Skip to main content

Command 1

Info:


The base_orch repo is fixed: Apache returns 200 OK, and all 10 B servers say base_orch OK.

Next, re-run the MOTD update for the B servers only. Run it from the folder you're already in (/etc/ansible/tricycle_ansible_master):

ansible-playbook site.yml -i inventories/ref_rbb/hosts_ref_rbb.yml --ask-vault-pass -u dbv6admin --tags tcpwrappers --limit 'rbb-ref-b-*:!rbb-ref-b-vlim06'

Then check the result on one server:

ssh rbb-ref-b-vlim02 cat /etc/motd

If the run ends with failed=0 and the MOTD shows the new kernel (553.184.1), the MOTD step is done. If anything fails, send me the PLAY RECAP.




======================================================

The files are there, but one folder level too deep, so the servers still can't find them.

What happened: your update/ folder already had a base_orch_yum_repo-1.1.0 folder inside it. Moving it created this:

/var/www/html/base_orch_yum_repo-1.1.0/base_orch_yum_repo-1.1.0/   <- the RPMs are here

But the servers look for:

/var/www/html/base_orch_yum_repo-1.1.0/repodata/repomd.xml

It's the same extra-folder problem we had with the tar file.

Fix it on rbb-ref-b-ansible:

cd /var/www/html
mv base_orch_yum_repo-1.1.0 base_orch_tmp
mv base_orch_tmp/base_orch_yum_repo-1.1.0 base_orch_yum_repo-1.1.0
rmdir base_orch_tmp
ls base_orch_yum_repo-1.1.0/repodata/
  • The last command should list repomd.xml.
  • If it says "No such file or directory", the copy has no index. Build one with createrepo_c /var/www/html/base_orch_yum_repo-1.1.0.

Then fix permissions and labels, and test. Files moved from /tmp keep a label that blocks Apache, so run restorecon again after the move:

chmod -R a+rX /var/www/html/base_orch_yum_repo-1.1.0
restorecon -R /var/www/html/base_orch_yum_repo-1.1.0
curl -sI http://10.212.176.62/base_orch_yum_repo-1.1.0/repodata/repomd.xml | head -1

You should see HTTP/1.1 200 OK.

Then check the servers can read it:

cd /etc/ansible/tricycle_ansible_master
ansible 'rbb-ref-b-*:!rbb-ref-b-vlim06' -i inventories/ref_rbb/hosts_ref_rbb.yml --ask-vault-pass -u dbv6admin -b -o \
  -m shell -a "dnf -q makecache --repo base_orch >/dev/null && echo base_orch OK"

Every server should say base_orch OK. Once they do, you can re-run the MOTD update with --limit 'rbb-ref-b-*:!rbb-ref-b-vlim06'.

======================================================

 rbb-ref-b-*:!rbb-ref-b-vlim06:!rbb-ref-b-ansible

ansible 'rbb-ref-b-*:!rbb-ref-b-vlim06:!rbb-ref-b-ansible' -i inventories/ref_rbb/hosts_ref_rbb.yml --ask-vault-pass -u dbv6admin -o -m command -a "uname -r"



cd /etc/ansible/tricycle_ansible_master

ansible-playbook site.yml -i inventories/ref_rbb/hosts_ref_rbb.yml --ask-vault-pass -u dbv6admin \

  --tags tcpwrappers --limit 'rbb-ref-b-*:!rbb-ref-b-vlim06'

ssh rbb-ref-b-vlim02 cat /etc/motd

=====================================

This run did more than update the MOTD, and it has left one thing that needs fixing soon.

What happened:

  1. Along with the MOTD tasks, it ran the shared ansible-common setup. That rewrote the base_orch repo on every server to http://10.212.176.62/base_orch_yum_repo-1.1.0, switched on (enabled: 1). That's the "changed" lines at the top.
  2. The next task then tried to use that repo, and every server failed: "Cannot download repomd.xml". The B master (.62) isn't serving a base_orch_yum_repo-1.1.0 repo at that address.
  3. So the run stopped before the MOTD part.

Why it matters: each server now has a repo that is switched on but can't be reached. Until that's fixed, dnf commands on those servers will error, including installs, checks and next month's patching.

Step 1. Check the B master (rbb-ref-b-ansible):

ls -ld /var/www/html/base_orch_yum_repo*
curl -sI http://10.212.176.62/base_orch_yum_repo-1.1.0/repodata/repomd.xml | head -1

Step 2. Fix it based on what you see:

  • No base_orch_yum_repo-1.1.0 folder on the B master (most likely): the A master has one. Copy it across from the A master:
    scp -rp /var/www/html/base_orch_yum_repo-1.1.0 root@10.212.176.62:/var/www/html/
    
    Then on the B master:
    chmod -R a+rX /var/www/html/base_orch_yum_repo-1.1.0
    restorecon -R /var/www/html/base_orch_yum_repo-1.1.0
    
  • The folder exists but curl shows 403: run just the chmod and restorecon lines above.
  • There's a base_orch folder under a different version, for example -1.0.x: send me the ls output. The servers may be meant to use that version instead, which would mean the run picked up the wrong version number.

Step 3. Confirm the servers can read it again:

ansible 'rbb-ref-b-*:!rbb-ref-b-vlim06' -i inventories/ref_rbb/hosts_ref_rbb.yml --ask-vault-pass -u dbv6admin -b -o \
  -m shell -a "dnf -q makecache --repo base_orch >/dev/null && echo base_orch OK"

Every server should say base_orch OK. After that, you can re-run the MOTD update.

Also check: the run included rbb-ref-a-vadmin and both vlim06 servers, so the --limit wasn't applied. Please send me the exact command you ran. rbb-ref-a-vadmin also had its base_orch repo pointed at the B master (.62), so once the B repo is fixed, check whether that A server should point at .61 instead.

Comments

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

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