[release-4.22] OCPBUGS-113718: Remove CustomNoUpgrade featureSet from disconnected UI - #3984
Conversation
…t API, so it no longer needs to be explicitly enabled via a feature gate. This also removes the CustomNoUpgrade featureSet which was only needed to allow setting that custom feature gate. manual cherry-pick from 03cbb90 (AGENT-1570)
|
@andfasano: This pull request references Jira Issue OCPBUGS-113718, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: andfasano 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 |
|
Welcome @andfasano! It looks like this is your first PR to openshift-assisted/assisted-installer-ui 🎉 |
|
Hi @andfasano. Thanks for your PR. I'm waiting for a openshift-assisted member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
/jira refresh |
|
@andfasano: This pull request references Jira Issue OCPBUGS-113718, which is invalid:
Comment DetailsIn response to this:
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. |
|
/jira refresh |
|
@andfasano: This pull request references Jira Issue OCPBUGS-113718, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
DetailsIn response to this:
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. |
|
/test ? |
|
@andfasano: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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. |
|
/retest |
|
/ok-to-test |
|
/test ? |
|
/test e2e-agent-compact-ipv4-iso-no-registry |
|
/lgtm |
|
@bfournie: changing LGTM is restricted to collaborators DetailsIn response to this:
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. |
|
/retest |
|
The current iso-no-registry failure is due the missing dependency bump in openshift/installer and openshift/mco. |
|
/hold |
|
/test e2e-agent-compact-ipv4-iso-no-registry |
2 similar comments
|
/test e2e-agent-compact-ipv4-iso-no-registry |
|
/test e2e-agent-compact-ipv4-iso-no-registry |
This is a manual cherry-pick of #3954, since the original backport to release-4.22 failed due some conflicts.
This patch is required to properly release the OVE ISO 4.22, otherwise it won't be possible to further upgrade the cluster once installed