Bug 1927080
Summary: | oc idle: Clusters upgrading with an idled workload do not have annotations on the workload's service | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> | |
Component: | Networking | Assignee: | Stephen Greene <sgreene> | |
Networking sub component: | router | QA Contact: | Arvind iyengar <aiyengar> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | high | |||
Priority: | urgent | CC: | aiyengar, amcdermo, aos-bugs, hongli, mjoseph, scuppett | |
Version: | 4.6 | Keywords: | Upgrades | |
Target Milestone: | --- | |||
Target Release: | 4.7.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause:
Upgrading a cluster from a prior version with an idled workload.
Consequence:
The idled workload will not wake on HTTP request once upgraded to OCP 4.6/4.7 with BZ#1900989 due to `oc idle` feature fixups and reworks.
Fix:
On ingress-opreator startup, mirror any idling changes from endpoints to services (since in latest 4.6/4.7, idling is based off of service idle annotations).
Result:
Unidling workloads after upgrades works as expected.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1927364 (view as bug list) | Environment: | ||
Last Closed: | 2021-03-16 08:42:46 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1925245 | |||
Bug Blocks: | 1927364 |
Description
OpenShift BugZilla Robot
2021-02-10 02:31:31 UTC
Bumping the priority to urgent as we want this to go into an early (as possible) 4.7.z release because it also need to go into 4.6 as early as possible after that. awaiting cherry pick Verified in "4.7.0-0.nightly-2021-03-04-004412" release version. Upgrading a v4.7 cluster to the said payload, the idled routes gets woken up and becomes accessible via curl without any manual interventions: ------------ $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.20 True False 20m Cluster version is 4.6.20 $ oc get all NAME READY STATUS RESTARTS AGE pod/web-server-rc-mltl9 1/1 Running 0 21s NAME DESIRED CURRENT READY AGE replicationcontroller/web-server-rc 1 1 1 21s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/service-secure ClusterIP 172.30.97.217 <none> 27443/TCP 22s service/service-unsecure ClusterIP 172.30.31.235 <none> 27017/TCP 22s NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD route.route.openshift.io/service-unsecure service-unsecure-test1a.apps.aiyengar-oc4620.qe.devcluster.openshift.com service-unsecure http None $ curl service-unsecure-test1a.apps.aiyengar-oc4620.qe.devcluster.openshift.com Hello-OpenShift web-server-rc-mltl9 http-8080 $ oc idle service-unsecure WARNING: idling when network policies are in place may cause connections to bypass network policy entirely The service "test1a/service-unsecure" has been marked as idled The service will unidle ReplicationController "test1a/web-server-rc" to 1 replicas once it receives traffic ReplicationController "test1a/web-server-rc" has been idled $ oc get all NAME DESIRED CURRENT READY AGE replicationcontroller/web-server-rc 0 0 0 87s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/service-secure ClusterIP 172.30.97.217 <none> 27443/TCP 87s service/service-unsecure ClusterIP 172.30.31.235 <none> 27017/TCP 87s NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD route.route.openshift.io/service-unsecure service-unsecure-test1a.apps.aiyengar-oc4620.qe.devcluster.openshift.com service-unsecure http None $ oc adm upgrade Cluster version is 4.6.20 Updates: VERSION IMAGE 4.7.0-0.nightly-2021-03-04-004412 registry.ci.openshift.org/ocp/release@sha256:7c742552fb326b32a6e4da1700ecbbbbe284ef4a69c0675167904fdcc2a6e2e5 $ oc adm upgrade --to=4.7.0-0.nightly-2021-03-04-004412 Updating to 4.7.0-0.nightly-2021-03-04-004412 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.20 True True 60m Working towards 4.7.0-0.nightly-2021-03-04-004412: 175 of 668 done (26% complete) .... $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2021-03-04-004412 True False 175m Cluster version is 4.7.0-0.nightly-2021-03-04-004412 $ curl service-unsecure-test1a.apps.aiyengar-oc4620.qe.devcluster.openshift.com Hello-OpenShift web-server-rc-lrgs4 http-8080 $ oc get all NAME READY STATUS RESTARTS AGE pod/web-server-rc-lrgs4 1/1 Running 0 24s NAME DESIRED CURRENT READY AGE replicationcontroller/web-server-rc 1 1 1 69m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/service-secure ClusterIP 172.30.97.217 <none> 27443/TCP 69m service/service-unsecure ClusterIP 172.30.31.235 <none> 27017/TCP 69m NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD route.route.openshift.io/service-unsecure service-unsecure-test1a.apps.aiyengar-oc4620.qe.devcluster.openshift.com service-unsecure http None ------------ Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.7.2 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:0749 |