Bug 1998029: CustomNoUpgrade should not fire no-upgrade failures#26430
Conversation
CustomNoUpgrade should be treated just as TechPreviewNoUpgrade, and should not be a condition that triggers no-upgrade failures in tests. This is useful in cases where we want to test a specific set of feature gates in isolation from other tech preview feature gates. Specifically we are using CustomNoUpgrade to test external-cloud-provider CCM promotions in isolation in https://github.com/openshift/release/blob/992f297ef8a1ba749f3a0b9b40438696f18a1bc4/ci-operator/step-registry/ccm/conf/pre-create-feature-gate/ccm-conf-pre-create-feature-gate-commands.sh#L22 Co-Authored-By: Matthew Booth <mbooth@redhat.com>
|
/cc JoelSpeed |
|
Changes make sense to me, and shouldn't affect the existing tests, LGTM |
|
@pierreprinetti: This pull request references Bugzilla bug 1998029, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 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 kubernetes/test-infra repository. |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/assign @ecordell |
|
/retest |
|
@pierreprinetti: The following test failed, say
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/test-infra repository. I understand the commands that are listed here. |
|
/assign njhale |
|
/assign @kevinrizza |
|
/lgtm |
|
Apparently I was chasing the wrong team. Let's try again! /assign bparees |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, JoelSpeed, pierreprinetti 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 |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/uncc |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
6 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/skip |
|
@pierreprinetti: All pull requests linked via external trackers have merged: Bugzilla bug 1998029 has been moved to the MODIFIED state. 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/test-infra repository. |
CustomNoUpgrade should be treated just as TechPreviewNoUpgrade, and
should not be a condition that triggers no-upgrade failures in tests.
This is useful in cases where we want to test a specific set of feature
gates in isolation from other tech preview feature gates.
Specifically we are using CustomNoUpgrade to test
external-cloud-provider CCM promotions in isolation in
https://github.com/openshift/release/blob/992f297ef8a1ba749f3a0b9b40438696f18a1bc4/ci-operator/step-registry/ccm/conf/pre-create-feature-gate/ccm-conf-pre-create-feature-gate-commands.sh#L22
Co-Authored-By: Matthew Booth mbooth@redhat.com