Skip to content

[WIP] OCPBUGS-42343: Remove master selector for olm installs on hcp?#16332

Draft
jkyros wants to merge 1 commit intoopenshift:mainfrom
jkyros:hypershift-olm-installs
Draft

[WIP] OCPBUGS-42343: Remove master selector for olm installs on hcp?#16332
jkyros wants to merge 1 commit intoopenshift:mainfrom
jkyros:hypershift-olm-installs

Conversation

@jkyros
Copy link
Copy Markdown
Member

@jkyros jkyros commented Apr 23, 2026

Please ignore this for now.

OLM installs on HCP selecting masters currently fail, I'm just testing to see if we can remove the master selector from the subscription and have it work.

Analysis / Root cause:

Solution description:

Screenshots / screen recording:

Test setup:

Test cases:

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

So right now if we're installing an OLM operator via the console, and
that operator's default nodeSelector happens to target masters, the
install will fail on a hosted control plane because there are no masters
available for scheduling, nor will there be.

This adjusts the OLM install for the console to check whether we're in a
hosted environment where we have no masters, and if so, remove that part
of the selector so the pods can float to the workers and run, which is a
better user experience than the install just breaking.

Signed-off-by: John Kyros <jkyros@redhat.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 23, 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 openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 23, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 23, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jkyros: This pull request references Jira Issue OCPBUGS-42343, which is invalid:

  • expected the bug to target the "5.0.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Please ignore this for now.

OLM installs on HCP selecting masters currently fail, I'm just testing to see if we can remove the master selector from the subscription and have it work.

Analysis / Root cause:

Solution description:

Screenshots / screen recording:

Test setup:

Test cases:

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the component/olm Related to OLM label Apr 23, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 23, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jkyros
Once this PR has been reviewed and has the lgtm label, please assign cajieh 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

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

Labels

component/olm Related to OLM do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants