Skip to content

Fix workshop install troubleshooting: use installplans, not ip - #1343

Open
boazmichaely wants to merge 1 commit into
ComplianceAsCode:masterfrom
boazmichaely:fix-workshop-installplan-command
Open

boazmichaely wants to merge 1 commit into
ComplianceAsCode:masterfrom
boazmichaely:fix-workshop-installplan-command

Conversation

@boazmichaely

Copy link
Copy Markdown

Summary

  • Change oc get ip -nopenshift-compliance to oc get installplans -nopenshift-compliance in the install exercise troubleshooting section.

Why

The install exercise shows sample InstallPlan output (NAME, CSV, APPROVAL, APPROVED), but the command uses oc get ip.

On current OpenShift/kubectl, ip is a short name for IPAddress (networking.k8s.io/v1), not OLM InstallPlan. Running oc get ip lists cluster service IP allocations, for example:

NAME             PARENTREF
172.30.0.1       services/default/kubernetes
172.30.0.10      services/openshift-dns/dns-default
...

InstallPlan also has short name ip (operators.coreos.com/v1alpha1), but it is lower priority, so oc get ip resolves to IPAddress and may warn that ip could also match installplans.

For OLM install troubleshooting, the intended resource is InstallPlan in openshift-compliance. Using the full resource name avoids the ambiguity.

Test plan

  • Verified oc explain ip documents IPAddress (networking.k8s.io/v1)
  • Verified oc explain installplans documents OLM InstallPlan with the expected columns

Made with Cursor

Use `oc get installplans` instead of `oc get ip` when checking OLM
InstallPlan status during Compliance Operator installation.

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci

openshift-ci Bot commented Aug 16, 2026

Copy link
Copy Markdown

Hi @boazmichaely. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions 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.

@yuumasato yuumasato left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/lgtm
Just update with a signed the commit, please.

@openshift-ci

openshift-ci Bot commented Sep 9, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: boazmichaely, yuumasato

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved label Sep 9, 2026
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.

2 participants