Skip to main content

New Command 5

 INFO:

Nothing here blocks patching. You can go ahead with Step 3. Here's what the output shows:

  • The duplicates are harmless. On vstat, vlip02, vlip03, vlim02 and vlip06, rbb-base is in two files: rbb_patches_07012025.repo (an old copy from July 2025) and rbb_rhel_patches.repo. Both copies are identical: same address, and both switched off (enabled = 0). dnf just warns about it.
  • vlim03's red FAILED is not a problem. grep returns code 1 when it finds nothing, so vlim03 simply has no rbb-base repo at all.
  • vlim04 and vlim05 point at the A-side master. Their rbb-base uses 10.212.176.61 (A), while the other B servers use .62 (B). It's switched off, so it doesn't affect this run, but it isn't consistent with the rest.

One quick check before Step 4. These rbb-base files point to /rhel-8-baseos/, not /os-patch/. On the A side, the patch run used a repo called os-base that the playbook creates, and that pointed at os-patch. That's why fixing os-patch worked there. To confirm the B side's Ansible code does the same, run this on rbb-ref-b-ansible:

cd /etc/ansible/tricycle_ansible_master
grep -rn --include='*.yml' -E 'os-patch|rhel-8-baseos|baseurl' . | grep -v '^./.git' | head -20

You should see os-patch in the task that creates the repo file ("Add … Repository file for RedHat 8.10 Patch"). If it shows rhel-8-baseos instead, stop and send me the output: the B servers would then patch from a different folder than the one you just fixed.

Then: run wizard Step 3 with rbb-ref-b-*:!rbb-ref-b-vlim06.

To tidy up later (worth adding to the Jira's next steps, but not part of today's fix):

  • Remove the old rbb_patches_07012025.repo from the 5 servers that have it.
  • Point rbb-base on vlim04 and vlim05 at the B master (.62), or remove it if it's no longer used.

Comments

Post a Comment

Popular posts from this blog

New Command 3

 INFO: These results are almost identical to the last run, which tells us the servers were still checking against an old copy of the repo list. Two things caused that. The B master is still running the old script. The message reads "dnf reports a conflict. Run: dnf update --assumeno", which is the 1.4 wording. Version 1.4.1 would also print dnf: lines underneath. The servers reused yesterday's repo list. When dnf reads a repo, it keeps a copy of the package list and reuses it for up to 48 hours. So the B servers checked against the list from before you added the 8 AppStream RPMs, and couldn't see them. That's why vlim03 still asks for perl and gcc. I've fixed the second one in the script: version 1.4.2 makes the dry run read the repo fresh every time. I've attached the script, the README (Word and PDF) and the pseudocode, all updated. Next steps: Copy os_patch_wizard.sh v1.4.2 to rbb-ref-b-ansible , replacing the old one. Check it with: grep...
Post a Comment
Read more

Single Step

  Starting a new weight loss journey today.  I will be working with Houston Methodist Hospital Medical Weight Management Center.  Met with the staff today and it seems to be a very positive environment. I am a bit worried about starting this process but glad I'm starting.   Details:  In this program, I will be placed on a Very Low Calorie Diet (VLCD), which involves consuming 800 calories in the form of meal replacements and no more than 50 grams of carbohydrates per day. My body should respond by going into ketosis, a metabolic state in which the body uses fat stores as its primary energy (ketone bodies).  And I have a lot of fat stored.   Start Date 3/14.   G
Post a Comment
Read more