Created attachment 1891950 [details] log Description of problem: Prior to OCP 4.7.48, the configure-ovs script picked the corrected bonded interface for br-ex. In OCP 4.7.48 we have that is consistently fail. It picks one of the slave interfaces (ens3f0). Version-Release number of selected component (if applicable): OCP Release > OCP 4.7.37 How reproducible: 100% Steps to Reproduce: 1. Deploy an OCP cluster with bonding 2. 3. Actual results: Expected results: configure-ovs should not fail and assign the correct interface to br-ex (bond1) Additional info: There appears to be a new default NM profile from 4.7.37 to 4.7.38 a that was not there before
Created attachment 1891952 [details] log
Note: The same bonding config has been used since OCP 4.6. The bond is being formed and the slaves are also appropriately attached. But there is this new wired-connection that is being created by NM that was not there in OCP 4.7.37 or earlier
When configure-ovs starts, before it does anything, ens3f0 is not enslaved to the bond. Instead, it has been activated on its own and has a default route. Thus configure-ovs picks up this interface to add to br-ex. Afterwards, configuration fails because of dhcp timeout and I guess this has something to do with dhcp server static mappings and the lease being already obtained for bond1. May 18 16:45:20 master-2 configure-ovs.sh[4464]: + ip route show May 18 16:45:20 master-2 configure-ovs.sh[4464]: default via 10.75.71.97 dev ens3f0 proto dhcp metric 102 May 18 16:45:20 master-2 configure-ovs.sh[4464]: default via 10.75.71.97 dev bond1 proto dhcp metric 300 May 18 16:45:20 master-2 configure-ovs.sh[4464]: 10.75.71.96/27 dev ens3f0 proto kernel scope link src 10.75.71.104 metric 102 May 18 16:45:20 master-2 configure-ovs.sh[4464]: 10.75.71.96/27 dev bond1 proto kernel scope link src 10.75.71.104 metric 300 May 18 16:45:20 master-2 configure-ovs.sh[4464]: 172.18.125.0/27 dev bond0.1305 proto kernel scope link src 172.18.125.18 metric 401 May 18 16:45:20 master-2 configure-ovs.sh[4464]: 198.19.0.0/19 dev bond1.1306 proto kernel scope link src 198.19.0.162 metric 400 May 18 16:45:20 master-2 configure-ovs.sh[4464]: + nmcli c show May 18 16:45:20 master-2 configure-ovs.sh[4464]: NAME UUID TYPE DEVICE May 18 16:45:20 master-2 configure-ovs.sh[4464]: Wired Connection 35577a25-d9a0-418e-b923-9f632e1050c4 ethernet ens3f0 May 18 16:45:20 master-2 configure-ovs.sh[4464]: bond0.1305 8c2f5a0a-09f8-31d8-9161-f88fd6d48994 vlan bond0.1305 May 18 16:45:20 master-2 configure-ovs.sh[4464]: bond1 0c977863-9a3f-3ad8-abee-145871486619 bond bond1 May 18 16:45:20 master-2 configure-ovs.sh[4464]: bond1.1306 a2de42bc-b496-3555-a3a3-7925d2d8eddb vlan bond1.1306 May 18 16:45:20 master-2 configure-ovs.sh[4464]: bond0 52eecf5a-df5e-30ae-9ca1-6297f0239027 bond bond0 May 18 16:45:20 master-2 configure-ovs.sh[4464]: eno1np0 e6fd4bca-c5dc-3704-bb4d-e55ef7f5e238 ethernet eno1np0 May 18 16:45:20 master-2 configure-ovs.sh[4464]: eno2np1 a667d95d-0f01-34fa-8c98-cce4b7b1fb86 ethernet eno2np1 May 18 16:45:20 master-2 configure-ovs.sh[4464]: ens3f1 b21ef99d-027b-37ed-bdcb-8b21127ae053 ethernet ens3f1 May 18 16:45:20 master-2 configure-ovs.sh[4464]: ens3f0 9871f703-73ca-33c2-ac5a-63990a852771 ethernet -- May 18 16:46:36 master-2 NetworkManager[2692]: <info> [1652892396.4105] dhcp4 (br-ex): activation: beginning transaction (timeout in 45 seconds) May 18 16:47:21 master-2 NetworkManager[2692]: <warn> [1652892441.3239] dhcp4 (br-ex): request timed out May 18 16:47:21 master-2 NetworkManager[2692]: <info> [1652892441.3239] dhcp4 (br-ex): state changed unknown -> timeout The problem though here happens before configure-ovs starts. ens3f0 is activated through the "Wired Connection 35577a25-d9a0-418e-b923-9f632e1050c4" profile instead of the intended "ens3f0 9871f703-73ca-33c2-ac5a-63990a852771" profile. The "Wired Connection 35577a25-d9a0-418e-b923-9f632e1050c4" has been most likely generated by nm-initrd-generator on boot, due to the presence of an "ip=" kernel argument. The profile is also activated during boot and when NM starts it recalls this activation state inhibiting the activation of the intended "ens3f0 9871f703-73ca-33c2-ac5a-63990a852771" profile. The is the same known issue as https://bugzilla.redhat.com/show_bug.cgi?id=2036677, so making this BZ depend on it. @bnemec is will assign it to you as well, but let me know if we should do something else. @thomas.haller Can you think of a reason why we don't see this behavior consistently for other devices? For example, The other devices (eno1np0, eno2np1, ens3f1) were activated through their intended profiles. Why it did not happen for them the same thing that happened for ens3f0? We sometimes don't see or have this problem at all, being the same known circumstance, and we wonder why? In the meantime, these are the possible workarounds: - deploy a systemd service to run before configure-ovs that will explicitly activate the bond & slaves - User the keep-configuration=no and allowed-connections NM settings as described in https://bugzilla.redhat.com/show_bug.cgi?id=1934122#c24 to override nm-initrd-generator for specific devices, although this looks like is only available form NM 1.32
I have a couple of ideas that might be worth a try as a workaround, in order of preference: 1. Use dhcp-client-id instead of static mac address mappings for dhcp leases. Set the dhcp-client-id in the bond profile only. If the slaves are not able to get a lease and they can't get activated through the default profile, they might activate through the slave profile. 2. Set autoconnect-slaves in the bond profile. That might force the slaves to be activated through the slave profile as well instead of the default profile.
Hello Jaime, (In reply to Jaime Caamaño Ruiz from comment #6) > I have a couple of ideas that might be worth a try as a workaround, in order > of preference: > > 1. Use dhcp-client-id instead of static mac address mappings for dhcp > leases. Set the dhcp-client-id in the bond profile only. If the slaves are > not able to get a lease and they can't get activated through the default > profile, they might activate through the slave profile. We are already using dhcp-client-id for the bonds, however the first boot will be on the default profile (in order to get the ignition). > > 2. Set autoconnect-slaves in the bond profile. That might force the slaves > to be activated through the slave profile as well instead of the default > profile. We are adding that too. This is how our Key file looks like: [connection] id=bond1 type=bond interface-name=bond1 autoconnect=true autoconnect-priority=98 connection.autoconnect-slaves=1 [ethernet] mtu=9000 [bond] mode=802.3ad miimon=100 [ipv4] method=auto dhcp-timeout=2147483647 [ipv6] method=auto And for the client-id: [root@master-2 ~]# cat /etc/NetworkManager/conf.d/98-client-id.conf [connection-bond0] match-device=interface-name:bond0 ipv4.dhcp-client-id=<mac> [connection-bond1] match-device=interface-name:bond1 ipv4.dhcp-client-id=<mac>
> > We are already using dhcp-client-id for the bonds, however the first boot > will be on the default profile (in order to get the ignition). > Through which interface? Isn't there a separate provisioning network for this? May 18 16:45:20 master-2 configure-ovs.sh[4464]: default via 10.75.71.97 dev ens3f0 proto dhcp metric 102 May 18 16:45:20 master-2 configure-ovs.sh[4464]: default via 10.75.71.97 dev bond1 proto dhcp metric 300 As you can see bond1 and ens3f0 have been leased the same ip address. Did ens3f0 with the default profile use the same dhcp-client-id as bond1? Anyway, the only other thing that occurs to me as far as possible workarounds go right now is to deploy a systemd service to run before configure-ovs that oneshots `nmcli c up ens3f1 && nmcli c up ens3f0` BTW we tracked that the default profile might have appeared on 4.7.42 release via an installer change (a year ago). Does it make sense? https://amd64.ocp.releases.ci.openshift.org/releasestream/4-stable/release/4.7.42 https://github.com/openshift/installer/pull/5013
(In reply to Jaime Caamaño Ruiz from comment #8) > > > > We are already using dhcp-client-id for the bonds, however the first boot > > will be on the default profile (in order to get the ignition). > > > > Through which interface? Isn't there a separate provisioning network for > this? This cluster is using virtual media, so there's no provisioning network. > > May 18 16:45:20 master-2 configure-ovs.sh[4464]: default via 10.75.71.97 dev > ens3f0 proto dhcp metric 102 > May 18 16:45:20 master-2 configure-ovs.sh[4464]: default via 10.75.71.97 dev > bond1 proto dhcp metric 300 > > As you can see bond1 and ens3f0 have been leased the same ip address. Did > ens3f0 with the default profile use the same dhcp-client-id as bond1? > > ens3f0 doesn't have a client-id configured, only the bonds. The interface ens3f0 is a member of the baremetal bond. IF I block ens3f0 from getting any IP, this would cause the deployment to fail right away as it wouldn't be able to provide an IP for inspection, deployment, ignition etc. > Anyway, the only other thing that occurs to me as far as possible > workarounds go right now is to deploy a systemd service to run before > configure-ovs that oneshots `nmcli c up ens3f1 && nmcli c up ens3f0` > I will try this and report back. > BTW we tracked that the default profile might have appeared on 4.7.42 > release via an installer change (a year ago). Does it make sense? > > https://amd64.ocp.releases.ci.openshift.org/releasestream/4-stable/release/4. > 7.42 > https://github.com/openshift/installer/pull/5013 This is a good finding, as 4.7.37 didn't have this behavior.
Just to clarify, even if there were a provisioning network it wouldn't be used to pull ignition. That always comes over the primary interface. Which mechanism is being used to deploy the bond config on the nodes? Is it machine-configs for something like the method described in https://access.redhat.com/solutions/5460671 ?
(In reply to Jaime Caamaño Ruiz from comment #3) > The problem though here happens before configure-ovs starts. ens3f0 is > activated through the "Wired Connection > 35577a25-d9a0-418e-b923-9f632e1050c4" profile instead of the intended > "ens3f0 9871f703-73ca-33c2-ac5a-63990a852771" profile. The "Wired Connection > 35577a25-d9a0-418e-b923-9f632e1050c4" has been most likely generated by > nm-initrd-generator on boot, due to the presence of an "ip=" kernel > argument. The profile is also activated during boot and when NM starts it > recalls this activation state inhibiting the activation of the intended > "ens3f0 9871f703-73ca-33c2-ac5a-63990a852771" profile. Hi, your analysis is correct; the `ip=dhcp` argument generates a `Wired Connection` wildcard profile. In the initrd, that profile is activated on all interfaces, but it only succeeds on `ens3f0` because there is no DHCP server on other interfaces. The NM state is carried over to the real root through a state file that indicates that `Wired Connection` should be active again on `ens3f0`. This is necessary because in general the network configuration should not change across the switch-root (to support scenarios where the root filesystem is on a network share). So, `ens3f0` gets activated with the generic profile instead of the one written by the configure-ovs script. Possible workarounds are: - don't use `ip=dhcp`, as it seems needed only in the first boot to fetch the ignition configuration; it doesn't seem required afterwards? - as pointed out above, use allowed-connections from https://bugzilla.redhat.com/show_bug.cgi?id=1934122#c24 However, that is available only since NM 1.32; - as suggested above, add a service/script that manually activates the right connection profiles; - have a service/script starting before NM that unconfigures `ens3f0` and removes the state file in /run/NetworkManager
(In reply to Beniamino Galvani from comment #11) Thanks for chiming in. > - don't use `ip=dhcp`, as it seems needed only in the first boot to > fetch the ignition configuration; it doesn't seem required > afterwards? I guess this is being used because the ip kernel arguments give some control over the ipv4 and ipv6 may-fail option in the generated profile that we would otherwise not have with the default profiles generated by NetworkManager. Having the possibility to configure overall defaults for them in NetworkManager configuration could potentially help as well. > - have a service/script starting before NM that > unconfigures `ens3f0` and removes the state file in /run/NetworkManager How can we recognize these state files? Are they in /run/NetworkManager/devices? Could we possibly have something that would remove all these state files before real root NM starts, so that NM has to reconsider the autoconnet-priority of all profiles when it does start? Thanks for the help.
(In reply to Jaime Caamaño Ruiz from comment #12) > (In reply to Beniamino Galvani from comment #11) > > Thanks for chiming in. > I guess this is being used because the ip kernel arguments give some control > over the ipv4 and ipv6 may-fail option in the generated profile that we > would otherwise not have with the default profiles generated by > NetworkManager. Having the possibility to configure overall defaults for > them in NetworkManager configuration could potentially help as well. Do you have more details on which are requirements about may-fail, and how does ip= help with that? > How can we recognize these state files? Are they in > /run/NetworkManager/devices? > Could we possibly have something that would remove all these state files > before real root NM starts, so that NM has to reconsider the > autoconnect-priority of all profiles when it does start? Right, the state file for each device is `/run/NetworkManager/devices/$ifindex` and contains a `device.connection-uuid` key. If that key is set, NM knows that the profile with that UUID must be activated on the interface because it was already active before a restart of the service. However, in order to let NM pick up the newly-created profiles it's not enough to delete the state file. When NM starts, `ens3f0` is already configured with an IP address and so NM will not touch it, generating a in-memory profile. You also need to flush the interface kernel configuration (e.g. via 'ip addr flush dev ens3f0`).
(In reply to Beniamino Galvani from comment #13) > (In reply to Jaime Caamaño Ruiz from comment #12) > > (In reply to Beniamino Galvani from comment #11) > > > > Thanks for chiming in. > > I guess this is being used because the ip kernel arguments give some control > > over the ipv4 and ipv6 may-fail option in the generated profile that we > > would otherwise not have with the default profiles generated by > > NetworkManager. Having the possibility to configure overall defaults for > > them in NetworkManager configuration could potentially help as well. > > Do you have more details on which are requirements about may-fail, and how > does ip= help with that? For IPv4 deployments, we are using ip=dhcp (probably unnecessarily after firsboot) /usr/libexec/nm-initrd-generator -s ip=dhcp ... [ipv4] dhcp-timeout=90 dns-search= may-fail=false method=auto ... [ipv6] addr-gen-mode=eui64 dhcp-timeout=90 dns-search= method=auto For dualstack or IPv6 deployments, we are using ip=dhcp6 /usr/libexec/nm-initrd-generator -s ip=dhcp6 ... [ipv4] dhcp-timeout=90 dns-search= method=disabled ... [ipv6] addr-gen-mode=eui64 dhcp-timeout=90 dns-search= may-fail=false method=auto For some reason, in those deployments we need to ensure IPv6 is resolved at network activation. > > > How can we recognize these state files? Are they in > > /run/NetworkManager/devices? > > Could we possibly have something that would remove all these state files > > before real root NM starts, so that NM has to reconsider the > > autoconnect-priority of all profiles when it does start? > > Right, the state file for each device is > `/run/NetworkManager/devices/$ifindex` and contains a > `device.connection-uuid` key. If that key is set, NM knows that the > profile with that UUID must be activated on the interface because it > was already active before a restart of the service. > > However, in order to let NM pick up the newly-created profiles it's not > enough to delete the state file. When NM starts, `ens3f0` is already > configured with an IP address and so NM will not touch it, generating > a in-memory profile. You also need to flush the interface kernel > configuration (e.g. via 'ip addr flush dev ens3f0`). Understood. If I also understood correctly, the NM 1.32 "keep-configuration" setting introduced in https://bugzilla.redhat.com/show_bug.cgi?id=1934122#c24 is not doing all this, right? It avoids the in-memory profile but it does nothing in regards to the state file. A pity, because it would be close to something that we could use on release where we have that version of NM available.
(In reply to Jaime Caamaño Ruiz from comment #14) > If I also understood correctly, the NM 1.32 "keep-configuration" setting > introduced in https://bugzilla.redhat.com/show_bug.cgi?id=1934122#c24 is not > doing all this, right? It avoids the in-memory profile but it does nothing > in regards to the state file. Right. But for the state file there is the other option in that comment: allowed-connections=except:origin:nm-initrd-generator that disallows initrd-generated profiles in real root. The two options together should achieve want you want. Anyway, when I said that deleting the state file is not enough, I was assuming that the kernel configuration of interfaces is preserved during switch-root. Now I have noticed in the log a script "coreos-teardown-initramfs" that presumably flushes addresses and routes before switch root. If that is really the case, then deleting the state file should be enough.
(In reply to Beniamino Galvani from comment #15) > (In reply to Jaime Caamaño Ruiz from comment #14) > > > If I also understood correctly, the NM 1.32 "keep-configuration" setting > > introduced in https://bugzilla.redhat.com/show_bug.cgi?id=1934122#c24 is not > > doing all this, right? It avoids the in-memory profile but it does nothing > > in regards to the state file. > > Right. But for the state file there is the other option in that comment: > > allowed-connections=except:origin:nm-initrd-generator > > that disallows initrd-generated profiles in real root. The two options > together should achieve want you want. I would say that's not exactly what we want. We want NM to consider initrd-generated profiles along with other profiles deployed by the user. We would just want NM to forget any associated state. If the user has deployed a higher priority profile for a device, then it will override any initrd-generated profile. If not, the initrd-generated profile will kick in. Or I might still be understanding something incorrectly. > > Anyway, when I said that deleting the state file is not enough, I was > assuming that the kernel configuration of interfaces is preserved during > switch-root. Now I have noticed in the log a script > "coreos-teardown-initramfs" that presumably flushes addresses and routes > before switch root. If that is really the case, then deleting the state file > should be enough. Good to know, thanks! We will have this in consideration.
(In reply to Beniamino Galvani from comment #13) > Do you have more details on which are requirements about may-fail, and how > does ip= help with that? The default behavior is to only wait for ipv4 (may-fail is set to no only on the v4 part of the connection). This doesn't work for ipv6/dual stack deployments where we need to have the ipv6 address before the network is actually up. If ipv6 may-fail is not set to no then we have run into situations where the network is considered "up" before it has an ipv6 address and everything after that breaks. It's true that we probably don't need ip=dhcp in the ipv4 case, but we prefer to limit the amount of ipv6-specific configuration that happens since ipv6 gets accidentally broken enough as it is because it works differently from ipv4. Even if we dropped ip=dhcp for the v4 case we'd still have this bug on ipv6.
(In reply to Ben Nemec from comment #17) > The default behavior is to only wait for ipv4 (may-fail is set to no only on > the v4 part of the connection). This doesn't work for ipv6/dual stack > deployments where we need to have the ipv6 address before the network is > actually up. If ipv6 may-fail is not set to no then we have run into > situations where the network is considered "up" before it has an ipv6 > address and everything after that breaks. This is for the initrd networking, not for the real root, right? From what I understood, the ip=dhcp or ip=dhcp6 arguments are needed only in initrd to fetch the ignition configuration. After that, ignition will create profiles for all the relevant interfaces and copy them to the real root. I suppose that those profiles could include ipv6.may-fail=no if IPv6 connectivity is needed in the real root. If so, then the ip= argument could be removed from the kernel command line in next boots, no? > It's true that we probably don't need ip=dhcp in the ipv4 case, but we > prefer to limit the amount of ipv6-specific configuration that happens since > ipv6 gets accidentally broken enough as it is because it works differently > from ipv4. Even if we dropped ip=dhcp for the v4 case we'd still have this > bug on ipv6. In RHEL 8.6, the initrd generator also supports ip=dhcp,dhcp6 which creates a profile with ipv4 and ipv6 both may-fail=yes, but where each address family is tried for at least 20 seconds before giving up. I think ip=dhcp,dhcp6 could be used on both IPv4 and IPv6/mixed deployments, provided that it's not a problem waiting those extra 20 seconds.
(In reply to Beniamino Galvani from comment #18) > This is for the initrd networking, not for the real root, right? From > what I understood, the ip=dhcp or ip=dhcp6 arguments are needed only > in initrd to fetch the ignition configuration. After that, ignition > will create profiles for all the relevant interfaces and copy them to > the real root. I suppose that those profiles could include > ipv6.may-fail=no if IPv6 connectivity is needed in the real root. If > so, then the ip= argument could be removed from the kernel command > line in next boots, no? I will let Ben correct me if needed but profiles would only be deployed through ignition in specific non default configurations (some of which we cannot predict at the time the image is built). In other cases, we do rely on the profiles from the kernel arguments and the capability we have to manipulate may-fail from them, even for the real root. > In RHEL 8.6, the initrd generator also supports ip=dhcp,dhcp6 which > creates a profile with ipv4 and ipv6 both may-fail=yes, but where each > address family is tried for at least 20 seconds before giving up. I think > ip=dhcp,dhcp6 could be used on both IPv4 and IPv6/mixed deployments, provided > that it's not a problem waiting those extra 20 seconds. If we had the capability to configure NM to behave like this generically (not per profile, but through NetworkManager.conf, which could then be override per profile), that would help also. --- So my understanding right now is that we might be able to handle this generically if we have something cleaning up the profile association in the device state files in /run/NetworkManager before NM starts. Could we remove the device state files altogether? Instead of just removing the `device.connection-uuid` key?
(In reply to Jaime Caamaño Ruiz from comment #19) > (In reply to Beniamino Galvani from comment #18) > > This is for the initrd networking, not for the real root, right? From > > what I understood, the ip=dhcp or ip=dhcp6 arguments are needed only > > in initrd to fetch the ignition configuration. After that, ignition > > will create profiles for all the relevant interfaces and copy them to > > the real root. I suppose that those profiles could include > > ipv6.may-fail=no if IPv6 connectivity is needed in the real root. If > > so, then the ip= argument could be removed from the kernel command > > line in next boots, no? > > I will let Ben correct me if needed but profiles would only be deployed > through ignition in specific non default configurations (some of which we > cannot predict at the time the image is built). In other cases, we do rely > on the profiles from the kernel arguments and the capability we have to > manipulate may-fail from them, even for the real root. In 4.10 when we added better-integrated network configuration we actually do drop the ip=dhcp lines if the user has specified a network config. In that case they're responsible for configuring all of the necessary interfaces. However, in 4.7 network configuration was done via mechanisms that the deployment layer did not have visibility into so it doesn't know whether the ip= lines need to be there.
(In reply to Jaime Caamaño Ruiz from comment #16) > I would say that's not exactly what we want. We want NM to consider > initrd-generated profiles along with other profiles deployed by the user. We > would just want NM to forget any associated state. If the user has deployed > a higher priority profile for a device, then it will override any > initrd-generated profile. If not, the initrd-generated profile will kick in. Got it, makes sense. I think we can implement a new feature to support this use case.
(In reply to Jaime Caamaño Ruiz from comment #19) > Could we remove the device state files altogether? Instead of just removing > the `device.connection-uuid` key? Yes, you can remove /run/NetworkManager/devices/ completely to forget the state from initrd. Then, the persistent profiles will be activated in real root because they have higher autoconnect priority.
*** Bug 2028159 has been marked as a duplicate of this bug. ***
Some success with ip=dhcp rd.debug rd.neednet=1 on 4.13.0-0.nightly-2022-11-28-233543, as long as we don't fail-over and reboot. Fail-over and reboot hits https://issues.redhat.com/browse/OCPBUGS-2817 F1129 19:57:42.669109 16597 ovnkube.go:133] error waiting for node readiness: failed to set the node masquerade route to OVN: unable to add OVN masquerade route to host, error: failed to add route for subnet fd69::1/128 via gateway <nil> with mtu 1400 and src: fd2e:6f44:5dd8::3f: invalid argument NetworkManager-clean-initrd-state logs -- Logs begin at Tue 2022-11-29 18:10:50 UTC, end at Wed 2022-11-30 02:56:42 UTC. -- Nov 29 18:16:37 master-0-0 systemd[1]: Starting Cleans NetworkManager state generated by dracut... Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + NM_DEVICES_DIR=/run/NetworkManager/devices Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + NM_RUN_CONN_DIR=/run/NetworkManager/system-connections Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + NM_ETC_CONN_DIR=/etc/NetworkManager/system-connections Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'Cleaning network activation state generated by dracut...' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'To disable, remove /var/lib/mco/nm-clean-initrd-state' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' '!' -e /run/NetworkManager/devices ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' '!' -e /run/NetworkManager/system-connections ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' '!' -e /etc/NetworkManager/system-connections ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' '!' -e /run/NetworkManager/devices/2 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1156]: ++ basename /run/NetworkManager/devices/2 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ifindex=2 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1163]: ++ ip -j link show Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1164]: ++ jq -r '.[] | select(.ifindex == 2) | .ifname // empty' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ifname=enp4s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -z enp4s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1180]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/2 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + active_profile_uuid= Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -z '' ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + continue Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' '!' -e /run/NetworkManager/devices/3 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1181]: ++ basename /run/NetworkManager/devices/3 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ifindex=3 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1184]: ++ ip -j link show Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1185]: ++ jq -r '.[] | select(.ifindex == 3) | .ifname // empty' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ifname=enp5s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -z enp5s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1194]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/3 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + active_profile_uuid=d97318fa-8067-4a3e-8418-8fb945041712 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -z d97318fa-8067-4a3e-8418-8fb945041712 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for profile in "${NM_RUN_CONN_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1195]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + generated_profile_uuid=d97318fa-8067-4a3e-8418-8fb945041712 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' d97318fa-8067-4a3e-8418-8fb945041712 = d97318fa-8067-4a3e-8418-8fb945041712 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + break Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' d97318fa-8067-4a3e-8418-8fb945041712 '!=' d97318fa-8067-4a3e-8418-8fb945041712 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1196]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + profile_ifname= Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -n '' ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1197]: ++ sed -nr '/^\[user\]/,/^\[/{/^org.freedesktop.NetworkManager.origin\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + origin=nm-initrd-generator Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -n nm-initrd-generator ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' nm-initrd-generator '!=' nm-initrd-generator ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1198]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/bond0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + profile_ifname=bond0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1199]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/bond0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + autoconnect= Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' bond0 = enp5s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1200]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/enp5s0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + profile_ifname=enp5s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1201]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/enp5s0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + autoconnect=true Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' enp5s0 = enp5s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' true '!=' false ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + break Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' enp5s0 '!=' enp5s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' true = false ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1202]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/enp5s0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + configured_profile_uuid= Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'enp5s0 activated with default generated profile d97318fa-8067-4a3e-8418-8fb945041712' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'enp5s0 has different configured specific profile ' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'enp5s0: removing state...' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'Flushing IP addresses from enp5s0' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ip addr flush enp5s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ip -6 addr flush enp5s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'Removing /run/NetworkManager/devices/3' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + rm -f -- /run/NetworkManager/devices/3 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' '!' -e /run/NetworkManager/devices/4 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1215]: ++ basename /run/NetworkManager/devices/4 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ifindex=4 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1218]: ++ ip -j link show Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1219]: ++ jq -r '.[] | select(.ifindex == 4) | .ifname // empty' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ifname=enp6s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -z enp6s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1226]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/4 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + active_profile_uuid=d97318fa-8067-4a3e-8418-8fb945041712 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -z d97318fa-8067-4a3e-8418-8fb945041712 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for profile in "${NM_RUN_CONN_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1227]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + generated_profile_uuid=d97318fa-8067-4a3e-8418-8fb945041712 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' d97318fa-8067-4a3e-8418-8fb945041712 = d97318fa-8067-4a3e-8418-8fb945041712 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + break Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' d97318fa-8067-4a3e-8418-8fb945041712 '!=' d97318fa-8067-4a3e-8418-8fb945041712 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1228]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + profile_ifname= Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -n '' ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1229]: ++ sed -nr '/^\[user\]/,/^\[/{/^org.freedesktop.NetworkManager.origin\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + origin=nm-initrd-generator Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' -n nm-initrd-generator ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' nm-initrd-generator '!=' nm-initrd-generator ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1230]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/bond0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + profile_ifname=bond0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1231]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/bond0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + autoconnect= Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' bond0 = enp6s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1232]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/enp5s0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + profile_ifname=enp5s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1233]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/enp5s0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + autoconnect=true Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' enp5s0 = enp6s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1234]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/enp6s0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + profile_ifname=enp6s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1235]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/enp6s0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + autoconnect=true Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' enp6s0 = enp6s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' true '!=' false ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + break Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' enp6s0 '!=' enp6s0 ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + '[' true = false ']' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1236]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/enp6s0 test .nmconnection' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + configured_profile_uuid= Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'enp6s0 activated with default generated profile d97318fa-8067-4a3e-8418-8fb945041712' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'enp6s0 has different configured specific profile ' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'enp6s0: removing state...' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'Flushing IP addresses from enp6s0' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ip addr flush enp6s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + ip -6 addr flush enp6s0 Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + logger -t nm-clean-initrd-state 'Removing /run/NetworkManager/devices/4' Nov 29 18:16:37 master-0-0 nm-clean-initrd-state.sh[1130]: + rm -f -- /run/NetworkManager/devices/4 Nov 29 18:16:37 master-0-0 systemd[1]: NetworkManager-clean-initrd-state.service: Succeeded. Nov 29 18:16:37 master-0-0 systemd[1]: Started Cleans NetworkManager state generated by dracut. Nov 29 18:16:37 master-0-0 systemd[1]: NetworkManager-clean-initrd-state.service: Consumed 150ms CPU time -- Reboot -- Nov 29 19:00:32 master-0-0 systemd[1]: Starting Cleans NetworkManager state generated by dracut... Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + NM_DEVICES_DIR=/run/NetworkManager/devices Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + NM_RUN_CONN_DIR=/run/NetworkManager/system-connections Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + NM_ETC_CONN_DIR=/etc/NetworkManager/system-connections Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'Cleaning network activation state generated by dracut...' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'To disable, remove /var/lib/mco/nm-clean-initrd-state' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '!' -e /run/NetworkManager/devices ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '!' -e /run/NetworkManager/system-connections ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '!' -e /etc/NetworkManager/system-connections ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '!' -e /run/NetworkManager/devices/2 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1134]: ++ basename /run/NetworkManager/devices/2 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + ifindex=2 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1138]: ++ ip -j link show Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1139]: ++ jq -r '.[] | select(.ifindex == 2) | .ifname // empty' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + ifname=enp4s0 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -z enp4s0 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1165]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/2 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + active_profile_uuid= Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -z '' ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + continue Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '!' -e /run/NetworkManager/devices/3 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1166]: ++ basename /run/NetworkManager/devices/3 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + ifindex=3 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1168]: ++ ip -j link show Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1169]: ++ jq -r '.[] | select(.ifindex == 3) | .ifname // empty' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + ifname=enp5s0 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -z enp5s0 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1177]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/3 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + active_profile_uuid=0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -z 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + for profile in "${NM_RUN_CONN_DIR}"/* Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1178]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + generated_profile_uuid=0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 = 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + break Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 '!=' 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1179]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + profile_ifname= Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -n '' ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1180]: ++ sed -nr '/^\[user\]/,/^\[/{/^org.freedesktop.NetworkManager.origin\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + origin=nm-initrd-generator Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -n nm-initrd-generator ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' nm-initrd-generator '!=' nm-initrd-generator ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1181]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + profile_ifname=enp5s0 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1182]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + autoconnect= Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' enp5s0 = enp5s0 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '' '!=' false ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + break Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' enp5s0 '!=' enp5s0 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '' = false ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1183]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + configured_profile_uuid=1cd39c01-a67e-40c4-8962-a7474b452abd Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'enp5s0 activated with default generated profile 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'enp5s0 has different configured specific profile 1cd39c01-a67e-40c4-8962-a7474b452abd' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'enp5s0: removing state...' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'Flushing IP addresses from enp5s0' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + ip addr flush enp5s0 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + ip -6 addr flush enp5s0 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'Removing /run/NetworkManager/devices/3' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + rm -f -- /run/NetworkManager/devices/3 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '!' -e /run/NetworkManager/devices/4 ']' Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1197]: ++ basename /run/NetworkManager/devices/4 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1120]: + ifindex=4 Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1199]: ++ ip -j link show Nov 29 19:00:32 master-0-0 nm-clean-initrd-state.sh[1200]: ++ jq -r '.[] | select(.ifindex == 4) | .ifname // empty' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + ifname=enp6s0 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -z enp6s0 ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1208]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/4 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + active_profile_uuid=0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -z 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + for profile in "${NM_RUN_CONN_DIR}"/* Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1211]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + generated_profile_uuid=0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 = 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + break Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 '!=' 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62 ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1216]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + profile_ifname= Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -n '' ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1218]: ++ sed -nr '/^\[user\]/,/^\[/{/^org.freedesktop.NetworkManager.origin\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + origin=nm-initrd-generator Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' -n nm-initrd-generator ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' nm-initrd-generator '!=' nm-initrd-generator ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1219]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + profile_ifname=enp5s0 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1220]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + autoconnect= Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' enp5s0 = enp6s0 ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1221]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + profile_ifname=enp6s0 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1223]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + autoconnect= Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' enp6s0 = enp6s0 ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '' '!=' false ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + break Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' enp6s0 '!=' enp6s0 ']' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + '[' '' = false ']' Nov 29 19:00:33 master-0-0 systemd[1]: NetworkManager-clean-initrd-state.service: Succeeded. Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1224]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 19:00:33 master-0-0 systemd[1]: Started Cleans NetworkManager state generated by dracut. Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + configured_profile_uuid=620621aa-3809-4dd7-992e-9f35de881716 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'enp6s0 activated with default generated profile 0f981b1f-d1d9-4539-a9d2-60d8a2a71e62' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'enp6s0 has different configured specific profile 620621aa-3809-4dd7-992e-9f35de881716' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'enp6s0: removing state...' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'Flushing IP addresses from enp6s0' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + ip addr flush enp6s0 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + ip -6 addr flush enp6s0 Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + logger -t nm-clean-initrd-state 'Removing /run/NetworkManager/devices/4' Nov 29 19:00:33 master-0-0 nm-clean-initrd-state.sh[1120]: + rm -f -- /run/NetworkManager/devices/4 Nov 29 19:00:33 master-0-0 systemd[1]: NetworkManager-clean-initrd-state.service: Consumed 154ms CPU time -- Reboot -- Nov 29 19:50:04 master-0-0 systemd[1]: Starting Cleans NetworkManager state generated by dracut... Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + NM_DEVICES_DIR=/run/NetworkManager/devices Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + NM_RUN_CONN_DIR=/run/NetworkManager/system-connections Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + NM_ETC_CONN_DIR=/etc/NetworkManager/system-connections Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + logger -t nm-clean-initrd-state 'Cleaning network activation state generated by dracut...' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + logger -t nm-clean-initrd-state 'To disable, remove /var/lib/mco/nm-clean-initrd-state' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' '!' -e /run/NetworkManager/devices ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' '!' -e /run/NetworkManager/system-connections ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' '!' -e /etc/NetworkManager/system-connections ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' '!' -e /run/NetworkManager/devices/2 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1135]: ++ basename /run/NetworkManager/devices/2 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + ifindex=2 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1140]: ++ jq -r '.[] | select(.ifindex == 2) | .ifname // empty' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1139]: ++ ip -j link show Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + ifname=enp4s0 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' -z enp4s0 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1169]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/2 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + active_profile_uuid= Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' -z '' ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + continue Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' '!' -e /run/NetworkManager/devices/3 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1170]: ++ basename /run/NetworkManager/devices/3 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + ifindex=3 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1172]: ++ ip -j link show Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1174]: ++ jq -r '.[] | select(.ifindex == 3) | .ifname // empty' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + ifname=enp5s0 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' -z enp5s0 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1177]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/3 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + active_profile_uuid= Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' -z '' ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + continue Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' '!' -e /run/NetworkManager/devices/4 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1178]: ++ basename /run/NetworkManager/devices/4 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + ifindex=4 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1180]: ++ ip -j link show Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1181]: ++ jq -r '.[] | select(.ifindex == 4) | .ifname // empty' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + ifname=enp6s0 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' -z enp6s0 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1186]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/4 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + active_profile_uuid=c3dc9da8-18d3-49a2-85d4-1a294392c105 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' -z c3dc9da8-18d3-49a2-85d4-1a294392c105 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + for profile in "${NM_RUN_CONN_DIR}"/* Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1187]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + generated_profile_uuid=c3dc9da8-18d3-49a2-85d4-1a294392c105 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' c3dc9da8-18d3-49a2-85d4-1a294392c105 = c3dc9da8-18d3-49a2-85d4-1a294392c105 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + break Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' c3dc9da8-18d3-49a2-85d4-1a294392c105 '!=' c3dc9da8-18d3-49a2-85d4-1a294392c105 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1188]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + profile_ifname= Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' -n '' ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1190]: ++ sed -nr '/^\[user\]/,/^\[/{/^org.freedesktop.NetworkManager.origin\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + origin=nm-initrd-generator Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' -n nm-initrd-generator ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' nm-initrd-generator '!=' nm-initrd-generator ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1191]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + profile_ifname=enp5s0 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1192]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + autoconnect= Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' enp5s0 = enp6s0 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1193]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + profile_ifname=enp6s0 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1194]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + autoconnect= Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' enp6s0 = enp6s0 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' '' '!=' false ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + break Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' enp6s0 '!=' enp6s0 ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + '[' '' = false ']' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1195]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 19:50:04 master-0-0 systemd[1]: NetworkManager-clean-initrd-state.service: Succeeded. Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + configured_profile_uuid=cb8f8af6-928b-4fe3-947f-b426704c88ad Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + logger -t nm-clean-initrd-state 'enp6s0 activated with default generated profile c3dc9da8-18d3-49a2-85d4-1a294392c105' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + logger -t nm-clean-initrd-state 'enp6s0 has different configured specific profile cb8f8af6-928b-4fe3-947f-b426704c88ad' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + logger -t nm-clean-initrd-state 'enp6s0: removing state...' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + logger -t nm-clean-initrd-state 'Flushing IP addresses from enp6s0' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + ip addr flush enp6s0 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + ip -6 addr flush enp6s0 Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + logger -t nm-clean-initrd-state 'Removing /run/NetworkManager/devices/4' Nov 29 19:50:04 master-0-0 nm-clean-initrd-state.sh[1115]: + rm -f -- /run/NetworkManager/devices/4 Nov 29 19:50:04 master-0-0 systemd[1]: Started Cleans NetworkManager state generated by dracut. Nov 29 19:50:04 master-0-0 systemd[1]: NetworkManager-clean-initrd-state.service: Consumed 127ms CPU time -- Reboot -- Nov 29 20:29:26 master-0-0 systemd[1]: Starting Cleans NetworkManager state generated by dracut... Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + NM_DEVICES_DIR=/run/NetworkManager/devices Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + NM_RUN_CONN_DIR=/run/NetworkManager/system-connections Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + NM_ETC_CONN_DIR=/etc/NetworkManager/system-connections Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'Cleaning network activation state generated by dracut...' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'To disable, remove /var/lib/mco/nm-clean-initrd-state' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '!' -e /run/NetworkManager/devices ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '!' -e /run/NetworkManager/system-connections ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '!' -e /etc/NetworkManager/system-connections ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '!' -e /run/NetworkManager/devices/2 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1161]: ++ basename /run/NetworkManager/devices/2 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ifindex=2 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1172]: ++ ip -j link show Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1173]: ++ jq -r '.[] | select(.ifindex == 2) | .ifname // empty' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ifname=enp4s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -z enp4s0 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1189]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/2 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + active_profile_uuid= Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -z '' ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + continue Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '!' -e /run/NetworkManager/devices/3 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1190]: ++ basename /run/NetworkManager/devices/3 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ifindex=3 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1192]: ++ ip -j link show Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1193]: ++ jq -r '.[] | select(.ifindex == 3) | .ifname // empty' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ifname=enp5s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -z enp5s0 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1200]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/3 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + active_profile_uuid=c2712725-804b-4f82-bc7a-b5af349edf0b Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -z c2712725-804b-4f82-bc7a-b5af349edf0b ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + for profile in "${NM_RUN_CONN_DIR}"/* Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1201]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + generated_profile_uuid=c2712725-804b-4f82-bc7a-b5af349edf0b Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' c2712725-804b-4f82-bc7a-b5af349edf0b = c2712725-804b-4f82-bc7a-b5af349edf0b ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + break Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' c2712725-804b-4f82-bc7a-b5af349edf0b '!=' c2712725-804b-4f82-bc7a-b5af349edf0b ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1202]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + profile_ifname= Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -n '' ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1203]: ++ sed -nr '/^\[user\]/,/^\[/{/^org.freedesktop.NetworkManager.origin\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + origin=nm-initrd-generator Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -n nm-initrd-generator ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' nm-initrd-generator '!=' nm-initrd-generator ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1204]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + profile_ifname=enp5s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1205]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + autoconnect= Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' enp5s0 = enp5s0 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '' '!=' false ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + break Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' enp5s0 '!=' enp5s0 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '' = false ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1206]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + configured_profile_uuid=645b6850-3780-4a02-9834-0b4e56c3fc8a Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'enp5s0 activated with default generated profile c2712725-804b-4f82-bc7a-b5af349edf0b' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'enp5s0 has different configured specific profile 645b6850-3780-4a02-9834-0b4e56c3fc8a' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'enp5s0: removing state...' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'Flushing IP addresses from enp5s0' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ip addr flush enp5s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ip -6 addr flush enp5s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'Removing /run/NetworkManager/devices/3' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + rm -f -- /run/NetworkManager/devices/3 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + for device in "${NM_DEVICES_DIR}"/* Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '!' -e /run/NetworkManager/devices/4 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1218]: ++ basename /run/NetworkManager/devices/4 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ifindex=4 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1220]: ++ ip -j link show Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1221]: ++ jq -r '.[] | select(.ifindex == 4) | .ifname // empty' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ifname=enp6s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -z enp6s0 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1222]: ++ sed -nr '/^\[device\]/,/^\[/{/^connection-uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/devices/4 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + active_profile_uuid=c2712725-804b-4f82-bc7a-b5af349edf0b Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -z c2712725-804b-4f82-bc7a-b5af349edf0b ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + for profile in "${NM_RUN_CONN_DIR}"/* Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1223]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + generated_profile_uuid=c2712725-804b-4f82-bc7a-b5af349edf0b Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' c2712725-804b-4f82-bc7a-b5af349edf0b = c2712725-804b-4f82-bc7a-b5af349edf0b ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + break Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' c2712725-804b-4f82-bc7a-b5af349edf0b '!=' c2712725-804b-4f82-bc7a-b5af349edf0b ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1224]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + profile_ifname= Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -n '' ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1225]: ++ sed -nr '/^\[user\]/,/^\[/{/^org.freedesktop.NetworkManager.origin\s*=/{s/[^=]+\s*=\s*//;P}}' /run/NetworkManager/system-connections/default_connection.nmconnection Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + origin=nm-initrd-generator Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' -n nm-initrd-generator ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' nm-initrd-generator '!=' nm-initrd-generator ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1226]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + profile_ifname=enp5s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1227]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp5s0-slave-ovs-clone.nmconnection' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + autoconnect= Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' enp5s0 = enp6s0 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + for profile in "${NM_ETC_CONN_DIR}"/* Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1228]: ++ sed -nr '/^\[connection\]/,/^\[/{/^interface-name\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + profile_ifname=enp6s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1230]: ++ sed -nr '/^\[connection\]/,/^\[/{/^autoconnect\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + autoconnect= Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' enp6s0 = enp6s0 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '' '!=' false ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + break Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' enp6s0 '!=' enp6s0 ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + '[' '' = false ']' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1231]: ++ sed -nr '/^\[connection\]/,/^\[/{/^uuid\s*=/{s/[^=]+\s*=\s*//;P}}' '/etc/NetworkManager/system-connections/Wired connection enp6s0-slave-ovs-clone.nmconnection' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + configured_profile_uuid=4d6afc73-f4b0-4ed0-a1bd-3bb2f3814c5a Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'enp6s0 activated with default generated profile c2712725-804b-4f82-bc7a-b5af349edf0b' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'enp6s0 has different configured specific profile 4d6afc73-f4b0-4ed0-a1bd-3bb2f3814c5a' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'enp6s0: removing state...' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'Flushing IP addresses from enp6s0' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ip addr flush enp6s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + ip -6 addr flush enp6s0 Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + logger -t nm-clean-initrd-state 'Removing /run/NetworkManager/devices/4' Nov 29 20:29:26 master-0-0 nm-clean-initrd-state.sh[1149]: + rm -f -- /run/NetworkManager/devices/4 Nov 29 20:29:26 master-0-0 systemd[1]: NetworkManager-clean-initrd-state.service: Succeeded. Nov 29 20:29:27 master-0-0 systemd[1]: Started Cleans NetworkManager state generated by dracut. Nov 29 20:29:27 master-0-0 systemd[1]: NetworkManager-clean-initrd-state.service: Consumed 146ms CPU time
Second install success on 4.13.0-0.nightly-2022-11-29-204715. Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.13.0 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:1326
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days