Skip to content

Conversation

@copejon
Copy link
Contributor

@copejon copejon commented Jan 14, 2026

If microshift config contains apiServer.featureGates.featureSet: DevPreviewNoUpgrade, microshift will refuse to start.

After the prohibited featureset is removed from the config, microshift will once again start.

@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 Jan 14, 2026
@openshift-ci-robot
Copy link

@copejon: This pull request references Jira Issue OCPBUGS-71208, which is invalid:

  • expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "4.21" instead

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:

If microshift config contains apiServer.featureGates.featureSet: DevPreviewNoUpgrade, microshift will refuse to start.

After the prohibited featureset is removed from the config, microshift will once again start.

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 requested review from agullon and vanhalenar January 14, 2026 20:20
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 14, 2026
@copejon
Copy link
Contributor Author

copejon commented Jan 14, 2026

Unrelated RF test failure from TLS drop-in config suite.

/retest-required

@agullon
Copy link
Contributor

agullon commented Jan 15, 2026

@copejon I think we should treat TechPreviewNoUpgrade same way as DevPreviewNoUpgrade because any FeatureGate in TechPreviewNoUpgrade and DevPreviewNoUpgrade Feature sets can break MicroShift.

So I suggest expanding the change in this ticket and PR to also TechPreviewNoUpgrade.

@copejon
Copy link
Contributor Author

copejon commented Jan 16, 2026

Pausing until we have a decision on MicroShift supporting specific tech-preview features

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 16, 2026
@copejon copejon changed the title OCPBUGS-71208: Prohibit DevPreviewNoUpgrade feature due to incompatible feature gate OCPBUGS-73946: Ignore (Dev|Tech)PreviewNoUpgrade FeatureSets Jan 16, 2026
@openshift-ci-robot openshift-ci-robot added the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Jan 16, 2026
@openshift-ci-robot
Copy link

@copejon: This pull request references Jira Issue OCPBUGS-73946, which is invalid:

  • expected the bug to target only the "4.22.0" version, but multiple target versions were 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:

If microshift config contains apiServer.featureGates.featureSet: DevPreviewNoUpgrade, microshift will refuse to start.

After the prohibited featureset is removed from the config, microshift will once again start.

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.

@copejon
Copy link
Contributor Author

copejon commented Jan 16, 2026

/jira refresh

@openshift-ci-robot
Copy link

@copejon: This pull request references Jira Issue OCPBUGS-73946, which is invalid:

  • expected the bug to target only the "4.22.0" version, but multiple target versions were 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.

Details

In response to this:

/jira refresh

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.

@copejon
Copy link
Contributor Author

copejon commented Jan 20, 2026

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 20, 2026
Co-authored-by: Alejandro Gullón <agullon@redhat.com>
@copejon
Copy link
Contributor Author

copejon commented Jan 23, 2026

/jira refresh

@openshift-ci-robot
Copy link

@copejon: This pull request references Jira Issue OCPBUGS-73946, which is invalid:

  • expected the bug to target only the "4.22.0" version, but multiple target versions were set
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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.

Details

In response to this:

/jira refresh

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.

@copejon
Copy link
Contributor Author

copejon commented Jan 23, 2026

/test e2e-aws-tests
/test e2e-aws-tests-bootc-arm

@copejon
Copy link
Contributor Author

copejon commented Jan 26, 2026

/test e2e-aws-tests-bootc-arm

@agullon
Copy link
Contributor

agullon commented Jan 27, 2026

it looks good to me

Copy link
Member

@pmtk pmtk left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, pmtk

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

@copejon
Copy link
Contributor Author

copejon commented Jan 27, 2026

/jira refresh

@openshift-ci-robot
Copy link

@copejon: This pull request references Jira Issue OCPBUGS-73946, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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.

Details

In response to this:

/jira refresh

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.

@copejon
Copy link
Contributor Author

copejon commented Jan 27, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 27, 2026
@openshift-ci-robot
Copy link

@copejon: This pull request references Jira Issue OCPBUGS-73946, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @agullon

Details

In response to this:

/jira refresh

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 requested a review from agullon January 27, 2026 17:33
@copejon
Copy link
Contributor Author

copejon commented Jan 27, 2026

/verified by jcope,ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 27, 2026
@openshift-ci-robot
Copy link

@copejon: This PR has been marked as verified by jcope,ci.

Details

In response to this:

/verified by jcope,ci

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
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@copejon: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit b3eb191 into openshift:main Jan 27, 2026
12 checks passed
@openshift-ci-robot
Copy link

@copejon: Jira Issue OCPBUGS-73946 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

Details

In response to this:

If microshift config contains apiServer.featureGates.featureSet: DevPreviewNoUpgrade, microshift will refuse to start.

After the prohibited featureset is removed from the config, microshift will once again start.

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.

@agullon
Copy link
Contributor

agullon commented Jan 28, 2026

/cherrypick release-4.21

@openshift-cherrypick-robot

@agullon: new pull request created: #6162

Details

In response to this:

/cherrypick release-4.21

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants