Description of problem: Under some circumstances (scale, probably), it appears tripleo_free may prevent a proper OC registration against a satellite instance. This is described in bug #2061393 Version-Release number of selected component (if applicable): Detected first on 16.2, but will also happen on 17.0 - hence this BZ How reproducible: Always, with a high number of nodes to register
Some more context: the redhat_subscription is called as a "host_prep_tasks", as well as "scale_tasks" and "upgrade_tasks"[1]. In order to switch the strategy, we'd need to edit the deploy-steps.j2 for host_prep_tasks[2] and upgrade_tasks[3] generation. Note that, apparently. scaling isn't specifying any strategy [1] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/rhsm/rhsm-baremetal-ansible.yaml [2] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/common/deploy-steps.j2#L671-L709 [3] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/common/deploy-steps.j2#L1122-L1142 [4] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/common/deploy-steps.j2#L1252-L1286
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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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/RHEA-2022:6543
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days