Comment 16 for bug 1950916
Revision history for this message
| Alfredo Moralejo (amoralej) wrote Re: master and wallaby check/gate/periodic tests are failing tempest - connectivity issues | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
After digging into this issue, i have some thoughts. Some facts:
- New version of qemu-kvm pushed to CentOS Stream 8 OS break oooq jobs because of the details showed in previous comments.
- If i understood correctly from conversation in #oooq, all reviews in tripleo repos are creating new containers from current-tripleo dlrn repo + current status of deps, OS and other dependencies.
- In this case, recreating containers on each review made all jobs to fail, not only promotion ones but also check and gate ones.
- As per conversations, this is a design decision, where rebuilding and serving containers (from provider job) was preferred over pulling and doing controlled update (only the packages being reviewed) because of problems with rate limiting in registry.
And now, just my opinion (as external non-ci team guy):
- Rebuilding the containers on check/gate jobs breaks the idea of promoting content, and limits it to only dlrn content.
- One of the advantages of including containers in the promotions was to extend the isolation of changes to not only the dlrn content but to the whole content of the containers. This still can have issues with packages installed in the hosts themselves, but provide a better protection against OS or deps changes.
I understand that this was evaluated when making the decision of rebuilding containers on each review, so this behaviour was expected, but it may be good to still think about alternatives (using a different registry?). There may be a viable one?