similar to: kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok

This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: > Hi, > > kickstarting fails due to problems with host resolution, even though the > network seems to be properly configured through DHCP. eno1 and eno2 are

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

Dear Simon, every second IP-address is unwanted. We restarted? eno4: nmcli con down eno4; nmcli con up eno4 and the second address vanishes. Then after a few ours, the second ip address reappears. This is the config-file of eno2: # cat ifcfg-eno2 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes

On Thu, 16 Jan 2020 15:34:43 +0100, Stephen John Smoogen <smooge at gmail.com> wrote: > On Thu, 16 Jan 2020 at 07:58, Asle Ommundsen <aommundsen at gmail.com> > wrote: >> >> Hi, >> >> Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after a >> reboot of the first server the network was unavailable. In IPMI console >>

This does not look bad, pretty ok. But im do have a question here. > ipaddress: 10.103.1.6 X.X.103.1 This indicated that the primary interface is eno2 > 2: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > ??? inet 10.103.1.6/24 brd 10.103.1.255 scope global eno2 > 3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > ??? inet

> -----Original Message----- > From: Gordon Messmer > Sent: Monday, August 31, 2015 12:15 PM > > On 08/31/2015 03:51 AM, Jason Pyeron wrote: > > I feel like this is an issue of libvirt starting before networking, > > but I am a fish out of water with systemd. > > Are you using the "network" or "NetworkManager" service to > configure your

Dear CentOS-Community, we are facing the following issue: A secondary ip address seems to be automatically added to a nic which causes several issues in our setup. This server is equipped with four nics which are currently in use: # nmcli con show NAME????? UUID????????????????????????????????? TYPE????? DEVICE eno2????? cb6fcb54-be52-4ab6-8324-88091a0ea1a0? ethernet? eno2 eno4?????

Dear Simon, > And can you diff the config of eno1 and eno4. # pwd /etc/sysconfig/network-scripts # diff -u ifcfg-eno1 ifcfg-eno4 --- ifcfg-eno1??? 2020-09-21 17:23:25.576672703 +0200 +++ ifcfg-eno4??? 2020-09-22 07:18:43.160532532 +0200 @@ -3,15 +3,20 @@ ?BROWSER_ONLY=no ?BOOTPROTO=none ?DEFROUTE=no -IPV4_FAILURE_FATAL=yes -IPV6INIT=no -IPV6_AUTOCONF=no +IPV4_FAILURE_FATAL=no

This is my system info: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.60-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh

someone recommended that i should give br0 the same hardware address as eno2. I did that, and restarted the vm, and it still does not work. Here is my current host interface config: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft

Two onboard nics, Intel, eno1 and eno2 If either of them is set to onboot then network won't start. one error message says :bad vendor preset disabled Another error message (in red) says Failed to start LSB If I can find a USB key there is an updated kmod-wl src.rpm that *may* bring up my wifi, but I am not sure I have access to a USB key at the moment. The motherboard is supermicro and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, some months ago I ran into a hassle with following, quite simple config that works on CentOS 6 and CentOS 5 extremeley well, for years. However, I have problems getting it running on CentOS 7. ,-- bond0.100 -- brbond0.100 -> (VMs) eth0 (eno1 on C7) --. | |--- bond0 ----|--

Nux! wrote: > Hello, > > ksdevice specifies which NIC to be used during the network install. > > The new naming conventions indeed make this more complicated than it needs > to be. To go back to the old naming scheme (eth0, eth1 ...) just add this > to boot parameters (kernel cmdline): > biosdevname=0 net.ifnames=0 Yes! Actually, the other admin I work with and I were just

Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: > This problem still bites us. I've tried to play around with DHCP > settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. > > I'm happy about /any/ hint. 1) ip route seems ok, but what does your /etc/resolv.conf looks like? 2) could you try with 7.3.1611, 7.2.1511 is no longer supported. Tru >

This should be easy to answer (I hope).? We routinely kickstart boxes to use for managing our customers RADIUS/DHCP configurations (along with other things).? We've had a C7 kickstart in place since I built one in May and are finally starting to roll it out for new installations.? But, I'm curious as to what ksdevice= actually does. With the C6 we routinely used ksdevice=eth0 since we

Hello, I?m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \

Hi Felix > Dear Simon, > > every second IP-address is unwanted. We restarted? eno4: > > nmcli con down eno4; nmcli con up eno4 > > and the second address vanishes. Then after a few ours, the second ip > address reappears. That's really interesting. Doesn't NetworkManager also store other settings in a different location, not the ifcfg files? I think it does so and

On 18/04/2017 15:54, Frank Thommen wrote: > Hi, > > I am currently struggling with the right way to configure a bonding > device via kickstart (via PXE). > > I am installing servers which have "eno" network interfaces. Instead of > the expected bonding device with two active slaves (bonding mode is > balance-alb), I get a bonding device with only one active slave

On 05/09/2019 11:14, L.P.H. van Belle via samba wrote: > This does not look bad, pretty ok. > > But im do have a question here. > >> ipaddress: 10.103.1.6 X.X.103.1 > This indicated that the primary interface is eno2 > >> 2: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP >> ??? inet 10.103.1.6/24 brd 10.103.1.255 scope global eno2

On Fri, 3 Nov 2017, Mark Haney wrote: > On 11/01/2017 05:02 PM, James A. Peltier wrote: >> Leaving ksdevice= off the command line will prompt you for the location of >> the kickstart file and the device you want to use to kickstart >> > Well, things just got weird with this.? The first couple of times I included > the biosdevname etc, on the command line with