Conversation
Workaround for the namespace auto-detection bug in the shared operatorhub-subscribe-lvm-operator step (fix pending in openshift#85087): for OCP 5.x MINOR_VERSION=0, so the step incorrectly selects openshift-storage instead of openshift-lvm-storage, leaving the OLM subscription permanently unresolved. Explicitly set LVM_OPERATOR_SUB_INSTALL_NAMESPACE=openshift-lvm-storage on metal-ds-ipi-ovn-lvms-f14-compliance[-destructive] to bypass the broken auto-detection until the shared step is fixed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughTwo scheduled compliance jobs now set the LVM operator installation namespace to ChangesLVM operator namespace configuration
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to This change directly addresses the LVMS namespace detection issue without introducing an identified merge risk. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse |
|
@yuumasato: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse |
|
@yuumasato: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@yuumasato: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/pj-rehearse ack |
|
/pj-rehearse ack |
|
@yuumasato: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: taimurhafeez, yuumasato 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 |
|
/assign memodi |
What
Explicitly set
LVM_OPERATOR_SUB_INSTALL_NAMESPACE: openshift-lvm-storageon the two Compliance Operator 5.0 LVMS-backed jobs:metal-ds-ipi-ovn-lvms-f14-compliancemetal-ds-ipi-ovn-lvms-f14-compliance-destructiveWhy
Workaround for a bug in the shared
operatorhub-subscribe-lvm-operatorandstorage-create-lvm-clustersteps (fix pending in #85087): the namespace auto-detection uses only the minor version, so for OCP 5.x (MINOR_VERSION=0) it picksopenshift-storageinstead ofopenshift-lvm-storage. The OLM subscription is created in the wrong namespace,installedCSVnever populates, and LVMS installation times out.Setting the namespace explicitly bypasses the broken auto-detection entirely — the step takes the
elsebranch and uses the provided value directly.Tracked in CMP-4727.
Note
This workaround can be removed once #85087 merges and the shared step is fixed.
🤖 Generated with Claude Code
Summary by CodeRabbit
LVM_OPERATOR_SUB_INSTALL_NAMESPACE=openshift-lvm-storagefor the two Compliance Operator 5.0 LVMS-backed jobs.openshift-storage, which causes LVMS installation timeouts.metal-ds-ipi-ovn-lvms-f14-compliancemetal-ds-ipi-ovn-lvms-f14-compliance-destructive#85087merges.