Skip to main content

447 Close

 INFO:


Status Update

  • I ran the follow-up Nessus scan of the rBB Ref environment on 19 Nov 2026 after patching both sides. It covered 23 addresses and found zero Critical vulnerabilities.
  • 20 servers were scanned with valid credentials, so the result reflects the packages actually installed. The other 3 addresses returned only basic host information.
  • The critical findings from the November scan are now cleared on both sides, including the kernel, unbound, vim, OpenSSH and the eMudhra ca-certificates update.
  • The pyOpenSSL finding no longer appears in the scan.
  • All patched servers are running kernel 4.18.0-553.185.1 and the login banner shows the new kernel.
  • The acceptance criteria for this ticket are met.
  • The OS patching script was used for both sides and a full side took about 20 minutes.

Next Steps

  • Close this ticket.
  • Continue with the P2B change control approval request with the customer to apply the same tested packages to Production.
  • The remaining High and Medium findings, such as bind, wget, rsyslog, apr-util and a newer kernel advisory, are outside the scope of this ticket. They will be picked up in the next quarterly patch round.
  • Application findings for MongoDB, nginx and Grafana are tracked separately with the application team.
  • pyOpenSSL: the scan no longer shows it, so I marked it as cleared and dropped it from Next Steps. But I will discuss with Adam.

Comments

Popular posts from this blog

Nov 17

 INFO: Only one package is missing, and it's my mistake. The command I gave you to check installed packages (in the short runbook) left out python3-unbound . So I wrongly told you no server had it. In fact every B server has python3-unbound , and it must be the same version as unbound-libs . The good news: that's the only problem. Kernel, vim, libtiff, rhc, LVM and GRUB all passed on every server. Fix: Download one more file from Red Hat (RHSA-2026:70754, RHEL 8 x86_64): python3-unbound-1.16.2-5.14.el8_10.4.x86_64.rpm Copy it to the B master: scp python3-unbound-1.16.2-5.14.el8_10.4.x86_64.rpm root@<rbb-ref-b-ansible>:/root/releases/2026.11/extra-rpms/ Step 2 again: answer y to "Use the existing folder" answer y to "Copy them into the repo?" answer y to the commands and to "Carry on" os-patch already points at rhel-8-10-nov2026 , so nothing changes there. Step 3 again. Every B server except vlim06 should show OK . v...

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...

New A Run

 INFO: You're in good shape at 5.8 GB free. The tar file can go straight from where it is. dbv6admin can already read /var/www/html/rbb-rhel8-repo-20261117.tar.gz , so it doesn't need copying to /tmp on B first. Only extra-rpms (160 MB) has to go through /tmp , because dbv6admin can't get into /root . On B, as root 1. Put extra-rpms where dbv6admin can reach it, and take the tar file's fingerprint cp -r /root/releases/2026.11/extra-rpms /tmp/ chown -R dbv6admin:dbv6admin /tmp/extra-rpms cp /root/os_patch_wizard_1.5.2.sh /tmp/ chown dbv6admin:dbv6admin /tmp/os_patch_wizard_1.5.2.sh sha256sum /var/www/html/rbb-rhel8-repo-20261117.tar.gz exit Write down the code sha256sum prints. You'll compare it on A. Skip the two wizard lines if A already has 1.5.2. To check, run grep SCRIPT_VERSION= /root/os_patch_wizard*.sh on A. On B, as dbv6admin 2. Send everything to A's /tmp scp /var/www/html/rbb-rhel8-repo-20261117.tar.gz dbv6admin@<A-master>:/tmp/ scp -r /tmp/...