Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Boot up a VM on Azure. Sometimes the NetworkManager service is not started, which causes the eth0 to not be up.
Check journal log, it shows nis-domainname.service ordering cycle:
Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found ordering cycle on nis-domainname.service/start
Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found dependency on network-online.target/start
Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found dependency on cloud-init.service/start
Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found dependency on basic.target/start
Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found dependency on sysinit.target/start
Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Job nis-domainname.service/start deleted to break ordering cycle starting with sysinit.target/start
Version-Release number of selected components (if applicable):
hostname-3.20-7.el8.x86_64
* hostname-3.20-6.el8.x86_64 doesn't have this issue
RHEL Version:
RHEL-8.5.0-20210616.n.0
RHEL-8.5.0-20210528.n.0
How reproducible:
5%-10%
Steps to Reproduce:
1. start a RHEL-8.5 on Azure
2. Reboot system several times. After each reboot, check if the eth0 is up.
3. Check journal log
Actual results:
Sometimes the eth0 is not up because NetworkManager service is not started.
Expected results:
NetworkManager service is started every time.
Additional info:
Script to reboot VM from outside and check network:
# cat reboot_outside.sh
#!/bin/bash
HOST="20.185.148.35"
function _instanceWaitSSH() {
local HOST="$1"
for LOOP_COUNTER in {0..30}; do
if ssh-keyscan "$HOST" > /dev/null 2>&1; then
echo "SSH is up!"
break
fi
echo "Retrying in 5 seconds... $LOOP_COUNTER"
sleep 5
done
}
for i in {1..100}; do
echo "=================== round $i ===================="
ssh -oStrictHostKeyChecking=no root@$HOST reboot
sleep 20
_instanceWaitSSH $HOST
done
Description of problem: Boot up a VM on Azure. Sometimes the NetworkManager service is not started, which causes the eth0 to not be up. Check journal log, it shows nis-domainname.service ordering cycle: Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found ordering cycle on nis-domainname.service/start Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found dependency on network-online.target/start Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found dependency on cloud-init.service/start Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found dependency on basic.target/start Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Found dependency on sysinit.target/start Jun 18 15:39:16 wala85sriov06170313-vm4 systemd[1]: sysinit.target: Job nis-domainname.service/start deleted to break ordering cycle starting with sysinit.target/start Version-Release number of selected components (if applicable): hostname-3.20-7.el8.x86_64 * hostname-3.20-6.el8.x86_64 doesn't have this issue RHEL Version: RHEL-8.5.0-20210616.n.0 RHEL-8.5.0-20210528.n.0 How reproducible: 5%-10% Steps to Reproduce: 1. start a RHEL-8.5 on Azure 2. Reboot system several times. After each reboot, check if the eth0 is up. 3. Check journal log Actual results: Sometimes the eth0 is not up because NetworkManager service is not started. Expected results: NetworkManager service is started every time. Additional info: Script to reboot VM from outside and check network: # cat reboot_outside.sh #!/bin/bash HOST="20.185.148.35" function _instanceWaitSSH() { local HOST="$1" for LOOP_COUNTER in {0..30}; do if ssh-keyscan "$HOST" > /dev/null 2>&1; then echo "SSH is up!" break fi echo "Retrying in 5 seconds... $LOOP_COUNTER" sleep 5 done } for i in {1..100}; do echo "=================== round $i ====================" ssh -oStrictHostKeyChecking=no root@$HOST reboot sleep 20 _instanceWaitSSH $HOST done