[1LP][RFR] Continue swapping EC2 with OpenStack and fix HTTP 503 issues.#10061
[1LP][RFR] Continue swapping EC2 with OpenStack and fix HTTP 503 issues.#10061mshriver merged 6 commits intoManageIQ:masterfrom jarovo:swap-the-ec2-with-other-cloud
Conversation
More methods are using EC2, which is disabled on the release runs.
We were getting HTTP 503 sometimes due to API not yet started though WebUI available. This adds simple check using the requests library.
john-dupuy
left a comment
There was a problem hiding this comment.
LGTM, thanks for this PR 👍
| try: | ||
| # There are 2 hard problems in computer science: cache | ||
| # invalidation, naming things, and off-by-1 errors. | ||
| # -- Leon Bambrick |
There was a problem hiding this comment.
Hilarious, and great implementation of the wait/check pattern here @JaryN !
|
I detected some fixture changes in commit f493032 The local fixture
The local fixture
The local fixture
The local fixture
The local fixture
Please, consider creating a PRT run to make sure your fixture changes do not break existing usage 😃 |
|
I expect to see Leon Bambrick on all of our cache invalidation calls from now on :) |
Another piece to saga about stabilization of the db restore tests.
I believe this PR, greatly reduces the problem by blocking until the API responds with some OK result. The API client object cached in the appliance had to be invalidated.
The errors currently on the PRT are not related. Related issue is an exception saying HTTP 503.