Bug 1998029 - CustomNoUpgrade should not fire no-upgrade failures
Summary: CustomNoUpgrade should not fire no-upgrade failures
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Framework
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.10.0
Assignee: Pierre Prinetti
QA Contact: Pierre Prinetti
URL:
Whiteboard:
Depends On:
Blocks: 2024433
TreeView+ depends on / blocked
 
Reported: 2021-08-26 10:09 UTC by Pierre Prinetti
Modified: 2021-11-18 05:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 18:13:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 26430 0 None None None 2021-08-26 10:10:22 UTC
Github openshift origin pull 26449 0 None None None 2021-09-03 09:49:39 UTC

Description Pierre Prinetti 2021-08-26 10:09:29 UTC 
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[1].


[1]: 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
Comment 4 Brenton Leanhardt 2021-09-27 13:18:11 UTC 
Hi Pierre, has this bug been resolved?  If so, would you mind marking it as CLOSED CURRENTRELEASE? Thanks.
Comment 5 Pierre Prinetti 2021-09-28 10:22:19 UTC 
Thank you for the reminder; I will oblige once /retest[1] gives me an answer on the matter.
Comment 6 Pierre Prinetti 2021-09-28 10:22:47 UTC 
Thank you for the reminder; I will oblige once /retest[1] gives me an answer on the matter.

[1]: https://github.com/openshift/release/pull/21117#issuecomment-929054802
Note You need to log in before you can comment on or make changes to this bug.