-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Strategic Product Work
-
3
-
False
-
None
-
False
-
OCPSTRAT-1162 - Rename “supported but not recommended” as known issues
-
-
-
OTA 250, OTA 251, OTA 252
oc adm upgrade {}include-not-recommended{-} today includes a Supported but not recommended updates: header when introducing those updates. It also renders the Recommended condition. OTA-1191 is about what to do with the -include-not-recommended flag. This ticket is about addressing the header and possibly about adjusting/contextualizing/something the Recommended condition type.
Here is a current output
$ oc adm upgrade --include-not-recommended Cluster version is 4.10.0-0.nightly-2021-12-23-153012 Upstream: https://raw.githubusercontent.com/wking/cincinnati-graph-data/cincinnati-graph-for-targeted-edge-blocking-demo/cincinnati-graph.json Channel: stable-4.10 Recommended updates: VERSION IMAGE 4.10.0-always-recommended quay.io/openshift-release-dev/ocp-release@sha256:0000000000000000000000000000000000000000000000000000000000000000 Supported but not recommended updates: Version: 4.10.0-conditionally-recommended Image: quay.io/openshift-release-dev/ocp-release@sha256:1111111111111111111111111111111111111111111111111111111111111111 Recommended: Unknown Reason: EvaluationFailed Message: Exposure to SomeChannelThing is unknown due to an evaluation failure: client-side throttling: only 16.3µs has elapsed since the last match call completed for this cluster condition backend; this cached cluster condition request has been queued for later execution On clusters with the channel set to 'buggy', this imaginary bug can happen. https://bug.example.com/b Version: 4.10.0-fc.2 Image: quay.io/openshift-release-dev/ocp- release@sha256:85c6ce1cffe205089c06efe363acb0d369f8df7ad48886f8c309f474007e4faf Recommended: False Reason: ModifiedAWSLoadBalancerServiceTags Message: On AWS clusters for Services in the openshift-ingress namespace… This will not cause issues updating between 4.10 releases. This conditional update is just a demonstration of the conditional update system. https://bugzilla.redhat.com/show_bug.cgi?id=2039339
Definition of done:
- Replace "Supported but not recommended updates" with "Updates with known issues" https://github.com/openshift/oc/blob/79dc671bdaeafa74b92f14ad9f6d84e344608034/pkg/cli/admin/upgrade/upgrade.go#L455
- Should we also remove the "Recommended: False" or "Recommended: Unknown" from the output?
After this change the output will look similar to below
$ oc adm upgrade --include-not-recommended Cluster version is 4.10.0-0.nightly-2021-12-23-153012 Upstream: https://raw.githubusercontent.com/wking/cincinnati-graph-data/cincinnati-graph-for-targeted-edge-blocking-demo/cincinnati-graph.json Channel: stable-4.10 Recommended updates: VERSION IMAGE 4.10.0-always-recommended quay.io/openshift-release-dev/ocp-release@sha256:0000000000000000000000000000000000000000000000000000000000000000 Updates with known issues: Version: 4.10.0-conditionally-recommended Image: quay.io/openshift-release-dev/ocp-release@sha256:1111111111111111111111111111111111111111111111111111111111111111 Recommended: Unknown Reason: EvaluationFailed Message: Exposure to SomeChannelThing is unknown due to an evaluation failure: client-side throttling: only 16.3µs has elapsed since the last match call completed for this cluster condition backend; this cached cluster condition request has been queued for later execution On clusters with the channel set to 'buggy', this imaginary bug can happen. https://bug.example.com/b Version: 4.10.0-fc.2 Image: quay.io/openshift-release-dev/ocp-release@sha256:85c6ce1cffe205089c06efe363acb0d369f8df7ad48886f8c309f474007e4faf Recommended: False Reason: ModifiedAWSLoadBalancerServiceTags Message: On AWS clusters for Services in the openshift-ingress namespace… This will not cause issues updating between 4.10 releases. This conditional update is just a demonstration of the conditional update system. https://bugzilla.redhat.com/show_bug.cgi?id=2039339
- is related to
-
-
- Closed
-
- links to