Skip to content

Update openstack2 NS containers in multi-NS VA#3819

Open
abays wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
abays:multi_ns_update_containers
Open

Update openstack2 NS containers in multi-NS VA#3819
abays wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
abays:multi_ns_update_containers

Conversation

@abays
Copy link
Copy Markdown
Contributor

@abays abays commented Mar 31, 2026

The second namespace in the multi-namespace VA needs to run the "update_containers" role. Only the "openstack" namespace is handled by default, so this adds a hook to the multi-namespace VA that calls the role for the "openstack2"
namespace.

The second namespace in the multi-namespace VA
needs to run the "update_containers" role.  Only
the "openstack" namespace is handled by default,
so this adds a hook to the multi-namespace VA
that calls the role for the "openstack2"
namespace.

Signed-off-by: Andrew Bays <abays@redhat.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 31, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 31, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign eshulman2 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@softwarefactory-project-zuul
Copy link
Copy Markdown

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/52d5efbf5cb54f8697028745d9814107

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 06m 01s
podified-multinode-edpm-deployment-crc FAILURE in 26m 32s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 23m 28s
✔️ cifmw-crc-podified-edpm-baremetal-minor-update SUCCESS in 1h 43m 36s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 52s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 59s

@abays
Copy link
Copy Markdown
Contributor Author

abays commented Mar 31, 2026

Build failed (check pipeline). Post recheck (without leading slash) to rerun all jobs. Make sure the failure cause has been resolved before you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/52d5efbf5cb54f8697028745d9814107

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 06m 01s ❌ podified-multinode-edpm-deployment-crc FAILURE in 26m 32s ✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 23m 28s ✔️ cifmw-crc-podified-edpm-baremetal-minor-update SUCCESS in 1h 43m 36s ✔️ noop SUCCESS in 0s ✔️ cifmw-pod-ansible-test SUCCESS in 8m 52s ✔️ cifmw-pod-pre-commit SUCCESS in 7m 59s

Unrelated to PR:

 urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.crc.testing', port=6443): Max retries exceeded with url: /api/v1/namespaces/openstack-operators (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa4cf4ce730>: Failed to establish a new connection: [Errno 111] Connection refused'))

@abays
Copy link
Copy Markdown
Contributor Author

abays commented Mar 31, 2026

recheck

@abays
Copy link
Copy Markdown
Contributor Author

abays commented Mar 31, 2026

This PR, combined with openstack-k8s-operators/architecture#732 and a <hidden internal PR> fixed the multi-namespace VA job in my testing.

@abays abays marked this pull request as ready for review March 31, 2026 19:32
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that perhaps this should go in hooks/playbooks instead, but arguably so should all the playbooks in the playbooks/multi-namespace directory. We could clean that up in a follow-up, as the goal of this PR and its companion PRs in openstack-k8s-operators and elsewhere are just to get the multi-namespace job working again. Moving these playbooks right now would further delay that process.

@amartyasinha
Copy link
Copy Markdown
Contributor

LGTM, but will delegate to cifmw members to approve
@danpawlik @evallesp

vakwetu added a commit to vakwetu/architecture that referenced this pull request Apr 1, 2026
… in openstack2 NS

Mirrors architecture PR openstack-k8s-operators#732 which adds this for the multi-namespace
scenario. Runs after the leaf control plane is deployed and ready,
before CA bundle and federation configuration hooks.

Reuses the shared playbooks/multi-namespace/ns2_update_containers.yaml
playbook from ci-framework rather than duplicating it.

Depends-On: openstack-k8s-operators/ci-framework#3819

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Ade Lee <alee@redhat.com>
Made-with: Cursor
Copy link
Copy Markdown
Contributor

@michburk michburk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants