As reported in https://issues.redhat.com/browse/OSPRH-7301 , the fips task incorrectly changes the reboot policy when the required fips status changes. We should follow whatever is defined by the deployer instead.
If nothing is defined, the policy is auto - which will result in a reboot.
In the case of a redeployed or adopted environment, we will end up simply logging that a reboot is supposed to happen. But we will then likely fail the subsquent fips status check - which is the desired behavior.
Needs approval from an approver in each of these files:
- ~~[OWNERS](https://github.com/openstack-k8s-operators/edpm-ansible/blob/main/OWNERS)~~ [rebtoor]
Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
As reported in https://issues.redhat.com/browse/OSPRH-7301 , the fips task incorrectly changes the reboot policy when the required fips status changes. We should follow whatever is defined by the deployer instead.
If nothing is defined, the policy is auto - which will result in a reboot.
In the case of a redeployed or adopted environment, we will end up simply logging that a reboot is supposed to happen. But we will then likely fail the subsquent fips status check - which is the desired behavior.
Resolves: https://issues.redhat.com/browse/OSPRH-7301