-
Notifications
You must be signed in to change notification settings - Fork 223
OCPBUGS-73946: Ignore (Dev|Tech)PreviewNoUpgrade FeatureSets #6082
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
@copejon: This pull request references Jira Issue OCPBUGS-71208, 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: copejon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Unrelated RF test failure from TLS drop-in config suite. /retest-required |
|
@copejon I think we should treat So I suggest expanding the change in this ticket and PR to also |
|
Pausing until we have a decision on MicroShift supporting specific tech-preview features /hold |
|
@copejon: This pull request references Jira Issue OCPBUGS-73946, 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. |
|
/jira refresh |
|
@copejon: This pull request references Jira Issue OCPBUGS-73946, 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. |
ca9efca to
81654ae
Compare
|
@copejon: all tests passed! 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. |
|
/unhold |
| // Must set CustomNoUpgrade enabled or disabled lists when FeatureSet is CustomNoUpgrade | ||
| if fg.FeatureSet == FeatureSetCustomNoUpgrade && len(fg.CustomNoUpgrade.Enabled) == 0 && len(fg.CustomNoUpgrade.Disabled) == 0 { | ||
| return fmt.Errorf("CustomNoUpgrade enabled or disabled lists must be set when FeatureSet is CustomNoUpgrade") | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you remove this check? afaiu this is still relevant
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at OpenShift kubebuilder validation, empty lists are accepted for CustomNoUpgrade. This makes sense because OpenShift also doesn't restrict changes to the enable/disable FG lists.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
understood, thanks
| } | ||
| return nil | ||
| case FeatureSetCustomNoUpgrade: | ||
| // Valid - continue to validate enabled/disabled lists below |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what lists below do you refer to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"lists" just refers to additional validations further down (L195-L217)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
understood, thanks
| return c | ||
| }(), | ||
| expectErr: true, | ||
| }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| }, | |
| }, | |
| { | |
| name: "feature-gates-custom-no-upgrade-with-empty-enabled-and-disabled-lists", | |
| config: func() *Config { | |
| c := mkDefaultConfig() | |
| c.ApiServer.FeatureGates.FeatureSet = "CustomNoUpgrade" | |
| c.ApiServer.FeatureGates.CustomNoUpgrade.Enabled = []string{} | |
| c.ApiServer.FeatureGates.CustomNoUpgrade.Disabled = []string{} | |
| return c | |
| }(), | |
| expectErr: true, | |
| }, |
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.