-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.16.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
x86_64
-
Production
-
None
-
None
-
None
-
Ready to Pick
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
upi install, baremetal Hardware: Synergy 480 Gen10 private registry ClusterVersion : 4.16.44 1. Node (re)boots - no network - first noticed in upgrade 2. Power cycle the node and - edit grub into emergency mode to troubleshoot 3. Set password for core 4. Continue boot process 5. Possibly log in as core and do 'systemctl default', but it seems that sometimes the fact that you booted into emergency mode gives something (hardware??) enough time that you don't have to do systemctl default. Just going into emervecy boot may in fact be enough to fix the problem
How reproducible:
During upgrade to 4.16
Steps to Reproduce:
1. reboot system -no network 2. reboot into emergency mode 3. resume boot. everything works
Actual results:
Expected results:
should not have to reboot into emergency mode