Bug 1976894
| Summary: | Unidling a StatefulSet does not work as expected | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Simon Krenger <skrenger> |
| Component: | Networking | Assignee: | Miheer Salunke <misalunk> |
| Networking sub component: | router | QA Contact: | Arvind iyengar <aiyengar> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | aiyengar, aos-bugs, bmcelvee, misalunk, mjoseph, mmasters, skrenger |
| Version: | 4.7 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Idling a StatefulSet seems to work however accessing the Services Route does not wake up the application ("Application is not available" error page is returned).
Consequence:
Fix: So, with this fix we will return an error saying that we don't support idling of stateful sets as the accessing the routes for the service which is idled does not work. For that a feature work will be required. But, for now we need to add a error whenever a customer tries to idle a stateful set service.
Result: We inform he customers that idling a statefulset is not supported when they run oc idle for a service which is mapped to a StatefulSet.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-10 16:04:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 6
Miciah Dashiel Butler Masters
2022-01-25 17:29:58 UTC
The PR merged right before code freeze, so I am setting target release back to 4.10.0. The change is in 4.10.0-0.nightly-2022-01-28-213019 build according to <https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/releasestream/4.10.0-0.nightly/release/4.10.0-0.nightly-2022-01-28-213019>, so I am moving the BZ to ON_QA. Verified in "4.10.0-0.nightly-2022-01-29-015515" release version. With this release, it is observed that the statefulset service does not get idled and the said warning gets produced during the process: ------ oc version Client Version: 4.10.0-0.nightly-2022-01-29-015515 Server Version: 4.10.0-0.nightly-2022-01-29-015515 Kubernetes Version: v1.23.3+b63be7f oc get all NAME READY STATUS RESTARTS AGE pod/web-server-rc-0 1/1 Running 0 2m12s pod/web-server-rc-1 1/1 Running 0 2m6s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/service-secure ClusterIP 172.30.8.237 <none> 27443/TCP 2m12s service/service-unsecure ClusterIP 172.30.156.245 <none> 27017/TCP 2m12s NAME READY AGE statefulset.apps/web-server-rc 2/2 2m14s NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD route.route.openshift.io/service-unsecure service-unsecure-test1.apps.aiyengar410bz.qe.devcluster.openshift.com service-unsecure http None oc idle service-unsecure WARNING: idling when network policies are in place may cause connections to bypass network policy entirely error: no valid scalable resources found to idle: unable to calculate scalable resources for service test1/service-unsecure: unable to load StatefulSet "web-server-rc": idling StatefulSet is not supported yet. oc get all NAME READY STATUS RESTARTS AGE pod/web-server-rc-0 1/1 Running 0 6m36s pod/web-server-rc-1 1/1 Running 0 6m33s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/service-secure ClusterIP 172.30.8.237 <none> 27443/TCP 57m service/service-unsecure ClusterIP 172.30.156.245 <none> 27017/TCP 57m ------ Hi, if there is anything that customers should know about this bug or if there are any important workarounds that should be outlined in the bug fixes section OpenShift Container Platform 4.10 release notes, please update the Doc Type and Doc Text fields. If not, can you please mark it as "no doc update"? Thanks! 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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056 |