Use fresh container images in openstack-meta-content-provider master#894
Use fresh container images in openstack-meta-content-provider master#894danpawlik wants to merge 2 commits into
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: danpawlik 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 |
danpawlik
force-pushed
the
use-local-registry
branch
from
c483eb9 to
7821818
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 49m 11s |
|
recheck |
danpawlik
force-pushed
the
use-local-registry
branch
from
7821818 to
a676cbf
Compare
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 4h 46m 14s |
danpawlik
force-pushed
the
use-local-registry
branch
from
a676cbf to
48af32e
Compare
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 1h 09m 02s |
|
recheck |
danpawlik
force-pushed
the
use-local-registry
branch
from
48af32e to
2667766
Compare
danpawlik
changed the title
|
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
danpawlik
force-pushed
the
use-local-registry
branch
from
2667766 to
694adee
Compare
danpawlik
force-pushed
the
use-local-registry
branch
from
694adee to
15cb513
Compare
danpawlik
changed the title
danpawlik
force-pushed
the
use-local-registry
branch
from
15cb513 to
5c20818
Compare
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 4h 04m 53s |
danpawlik
force-pushed
the
use-local-registry
branch
from
5c20818 to
52c66a3
Compare
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 3h 18m 51s |
|
recheck |
danpawlik
force-pushed
the
use-local-registry
branch
5 times, most recently
from
590f803 to
e7a5b61
Compare
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 2h 35m 01s |
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 3h 55m 32s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 3h 13m 09s |
danpawlik
force-pushed
the
use-local-registry
branch
from
b4be4f4 to
d1bdfe0
Compare
|
Build failed (check pipeline). Post ❌ telemetry-openstack-meta-content-provider-master FAILURE in 9m 14s |
|
recheck |
danpawlik
force-pushed
the
use-local-registry
branch
from
d1bdfe0 to
ccfcbb4
Compare
|
looks like it built barbican as expected on c10s im not really sure why cloud kitty failed but it did use the epceted images barbicanAPIImage: 38.102.83.144:5001/podified-master-centos10/openstack-barbican-api:telemetry_latest -- barbicanKeystoneListenerImage: 38.102.83.144:5001/podified-master-centos10/openstack-barbican-keystone-listener:telemetry_latest barbicanWorkerImage: 38.102.83.144:5001/podified-master-centos10/openstack-barbican-worker:telemetry_latest and it started fine so at least the barbican part seams to be ok |
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 3h 11m 44s |
|
Indeed. Thank you for that hint @SeanMooney |
|
I guess tempest is failing because it uses old image - https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/logs/6ed/rdoproject.org/6ed64a60c7124dc2a3191d5730a80271/controller/ci-framework-data/logs/openstack-must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-70ce4ab587da14dddf23f3816879343650007e91038f935686ab5355e6f2a7a2/namespaces/openstack/pods/tempest-tests-tempest/tempest-tests-tempest-describe |
danpawlik
force-pushed
the
use-local-registry
branch
from
ccfcbb4 to
8484a3f
Compare
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 3h 08m 26s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 3h 22m 53s |
danpawlik
force-pushed
the
use-local-registry
branch
from
c2012df to
f8bb02e
Compare
|
Testing last commit related to parents var. If that would work, will squash and push one more change. |
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 3h 53m 40s |
We would like to start using container images that are done with latest code available in the repository instead of relay on current-tested tag. Also improved zuul configuration file: What changed: - added comments that what job uses which component tag - changed python list style to yaml list - applied same CI job vars as it is done in watcher [1] - improved tempest vars [1] https://github.com/openstack-k8s-operators/watcher-operator/blob/main/.zuul.yaml Depends-On: https://review.opendev.org/c/openstack/barbican/+/990084 Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
danpawlik
force-pushed
the
use-local-registry
branch
from
f8bb02e to
ee3bb96
Compare
Some variables should belong to meta content job, not to the cloud kitty.
|
/test telemetry-operator-build-deploy-kuttl |
2 participants
We would like to start using container images that are done with
latest code available in the repository instead of relay on
current-tested tag.
Also improved zuul configuration file:
What changed:
[1] https://github.com/openstack-k8s-operators/watcher-operator/blob/main/.zuul.yaml
Depends-On: https://review.opendev.org/c/openstack/barbican/+/990084