-
Sub-task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
1
-
False
-
-
False
-
-
-
Sprint 6 Quasar & Pulsar
-
1
We hit an issue with swift adoption, turns out that swift CR was missing the storagemgmt network attachement(https://issues.redhat.com/browse/OSPRH-15520?focusedId=28118986&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comme[…]118986).
I added it here in adoption repo (https://github.com/openstack-k8s-operators/data-plane-adoption/pull/1063/files) but it seems the NAD itself is not created as architecture repo doesn't have proper Kustomization for it.
We do define it in https://gitlab.cee.redhat.com/ci-framework/ci-framework-jobs/-/blob/main/scenarios/uni/uni05epsilon/01-net-def.yaml?ref_type=heads#L80 but it doesn't really set it up.
We are being told the standard approach was to always use storagemgmt in pre 18 release so it makes more sense to add it rather than dropping it everywhere .
We need to update the swift CR based on storagemgmt setup