Bug 2092572
| Summary: | acm-simple-kmod chart should create the namespace on the spoke cluster | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Constantin Vultur <cvultur> |
| Component: | Special Resource Operator | Assignee: | Pablo Acevedo <pacevedo> |
| Status: | CLOSED ERRATA | QA Contact: | Constantin Vultur <cvultur> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.11 | CC: | bthurber |
| Target Milestone: | --- | ||
| Target Release: | 4.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-10 11:15:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
With latest bundle this works fine. Marking as Verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069 |
Description of problem: The acm-simple-kmod does not create the namespace on spoke cluster. Version-Release number of selected component (if applicable): release-4.11 How reproducible: Steps to Reproduce: 1. Deploy acm-simple-kmod example on a hub/spoke 2. 3. Actual results: The policy status stays as NonCompliant "status": [ { "clustername": "sno1-0", "clusternamespace": "sno1-0", "compliant": "NonCompliant" }, { "clustername": "sno2-0", "clusternamespace": "sno2-0", "compliant": "NonCompliant" } ] While looking on the spoke cluster, there were no acm-simple-kmod namespace where to run the container. Then I created the namespace by hand on the sno1-0 spoke: # KUBECONFIG=/sno1-0/auth/kubeconfig oc new-project acm-simple-kmod Rechecked the policy and this time the sno1-0 is compliant: "status": [ { "clustername": "sno1-0", "clusternamespace": "sno1-0", "compliant": "Compliant" }, { "clustername": "sno2-0", "clusternamespace": "sno2-0", "compliant": "NonCompliant" } ] Then checked the pods in the acm-simple-kmod namespace: KUBECONFIG=/sno1-0/auth/kubeconfig oc get pods NAME READY STATUS RESTARTS AGE acm-simple-kmod-4-18-0-305-25-1-el8-4-x86-64-nv8rg 1/1 Running 0 7m25s Expected results: Example to create the namespace for the container Additional info: