DescriptionRicardo Ramos Thomas
2024-08-05 12:07:45 UTC
Description of problem:
It is not possible to deploy any new computes under our upgraded osp17.1.3 cluster.
Because the ansible tasks that get executed are wrongly ordered.
As you can see in the attached rendered ansible playbook (coming from /home/stack/overcloud-deploy/xxxx/config-download/xxxx/stdv12sriov/host_prep_tasks.yaml), there are tasks that try and install packages (the currently problematic one systemd-container) before the Satellite registration is getting performed.
This results in an error like this:
FATAL | check systemd-container package installed or not | xxxxxcom090 | error={"changed": false, "failures":
["No package systemd-container available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []}
Which is logic as you can see in the attached ansible playbook, openstack tries to install this package at line 125, while the Satellite registration is only performed at line 590.
Version-Release number of selected component (if applicable):
RHOSP 17.1 (wallaby)
How reproducible:
trying to add new computes to env 17.1.3
Steps to Reproduce:
1.
2.
3.
Actual results:
Can't add new nodes.
Expected results:
Add new nodes to Environment successfully
Additional info:
- SOS report and analysis available on case.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (RHOSP 17.1.4 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2024:9974
Description of problem: It is not possible to deploy any new computes under our upgraded osp17.1.3 cluster. Because the ansible tasks that get executed are wrongly ordered. As you can see in the attached rendered ansible playbook (coming from /home/stack/overcloud-deploy/xxxx/config-download/xxxx/stdv12sriov/host_prep_tasks.yaml), there are tasks that try and install packages (the currently problematic one systemd-container) before the Satellite registration is getting performed. This results in an error like this: FATAL | check systemd-container package installed or not | xxxxxcom090 | error={"changed": false, "failures": ["No package systemd-container available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []} Which is logic as you can see in the attached ansible playbook, openstack tries to install this package at line 125, while the Satellite registration is only performed at line 590. Version-Release number of selected component (if applicable): RHOSP 17.1 (wallaby) How reproducible: trying to add new computes to env 17.1.3 Steps to Reproduce: 1. 2. 3. Actual results: Can't add new nodes. Expected results: Add new nodes to Environment successfully Additional info: - SOS report and analysis available on case.