Info:
vlim02 is done. failed=0 and the wizard shows Step 4 OK.
The run only took 17 seconds, and "Run Yum Update" took about a second. That means vlim02 already had everything installed from the earlier run, so this pass just confirmed it and tidied up. "Reboot VM if necessary" was skipped because no reboot was needed. The [WARN] lines are expected: they're just reminding you that this run covered only one server.
Next:
-
Step 11 on vlim02, to confirm no packages were removed. Also check the kernel:
ssh rbb-ref-a-vlim02 uname -rExpect
4.18.0-553.184.1.el8_10.x86_64. -
LVM check on all servers. This step is important: it stops the boot hang from happening on the rest.
cd /etc/ansible/tricycle_ansible_master ansible 'all:!rbb-ref-b-vadmin' -i inventories/ref_rbb/hosts_ref_rbb.yml --ask-vault-pass -u dbv6admin -b -m shell \ -a "rpm -q lvm2 device-mapper; lsinitrd | grep -c lvm"Every server should show both packages installed and a count above 0. Fix any that don't before going on. Use the same
dnf install lvm2steps you used on vlim02. -
Take snapshots of the remaining servers in vCenter, so you can roll back if a reboot goes wrong.
-
Step 4 in the wizard, typing
all:!rbb-ref-b-vadmin. Then Steps 5 to 13.
Comments
Post a Comment