Bug 2024433 - 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.9.z
Assignee: Pierre Prinetti
QA Contact: Pierre Prinetti
URL:
Whiteboard:
Depends On: 1998029
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-18 05:17 UTC by OpenShift BugZilla Robot
Modified: 2021-12-07 17:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 17:52:17 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 26615 0 None open [release-4.9] Bug 2024433: CustomNoUpgrade should not fire no-upgrade failures 2021-11-18 05:18:08 UTC

Comment 1 W. Trevor King 2021-11-18 05:25:46 UTC
To help out CI-search and Sippy, this should fix 4.9 failures like [1]:

: [sig-arch][Early] Managed cluster should start all core operators [Skipped:Disconnected] [Suite:openshift/conformance/parallel]
Run #0: Failed	1s
  fail [github.com/onsi/ginkgo@v4.7.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Nov 18 03:53:11.275: Some cluster operators are not ready: kube-apiserver (Upgradeable=False FeatureGates_RestrictedFeatureGates_TechPreviewNoUpgrade: FeatureGatesUpgradeable: "TechPreviewNoUpgrade" does not allow updates)

[1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-e2e-aws-techpreview/1461167575890137088

Comment 3 Pierre Prinetti 2021-12-07 16:45:12 UTC
Tentatively setting to VERIFIED.

Comment 4 W. Trevor King 2021-12-07 17:52:17 UTC
Doesn't need to get linked to an errata, so I'm closing CURRENTRELEASE.  Evidence that this backport improved things:

  $ w3m -dump -cols 200 'https://search.ci.openshift.org/?maxAge=48h&type=junit&search=cluster+operators+are+not+ready:+kube-apiserver.*Upgradeable=False' | grep 'failures match' | sort
  ...no hits..

while taking a deeper history to reach back before the backport landed gives plenty of hits:

  $ w3m -dump -cols 200 'https://search.ci.openshift.org/?maxAge=336h&type=junit&search=cluster+operators+are+not+ready:+kube-apiserver.*Upgradeable=False' | grep 'failures match' | sort
  periodic-ci-openshift-release-master-ci-4.9-e2e-aws-techpreview (all) - 42 runs, 86% failed, 78% of failures match = 67% impact
  periodic-ci-openshift-release-master-ci-4.9-e2e-aws-techpreview-serial (all) - 42 runs, 93% failed, 77% of failures match = 71% impact
  ...


Note You need to log in before you can comment on or make changes to this bug.