Strenghten ready condition on set openstack containers#4017
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 39m 37s |
|
Build failed (check pipeline). Post ❌ openstack-k8s-operators-content-provider FAILURE in 11m 53s |
46306c0 to
87fc86b
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 28m 47s |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 20m 38s |
0b47467 to
a25ff47
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 22m 05s |
set_openstack_containers wait for the openstack-operator-init pod to be reinstalled, problem is that openstack-operator takes a minute to be restarted, which in some scenarios can cause problems, improving the wait logic to avoid that. Resolves: OSPRH-31605
set_openstack_containers wait for the openstack-operator-init
pod to be reinstalled, problem is that openstack-operator
takes a minute to be restarted, which in some scenarios can
cause problems, improving the wait logic to avoid that.
Resolves: OSPRH-31605