Bug 1976894 - Unidling a StatefulSet does not work as expected
Summary: Unidling a StatefulSet does not work as expected
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Miheer Salunke
QA Contact: Arvind iyengar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-28 13:39 UTC by Simon Krenger
Modified: 2023-01-12 17:01 UTC (History)
7 users (show)

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.
Clone Of:
Environment:
Last Closed: 2022-03-10 16:04:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift oc pull 1026 0 None open Bug 1976894: Idling a StatefulSet seems to work however accessing the Services Route does not wake up the application ("... 2022-01-17 08:02:48 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:04:33 UTC

Comment 6 Miciah Dashiel Butler Masters 2022-01-25 17:29:58 UTC
Moving off of 4.10.0.  We'll fix this in a later release.

Comment 7 Miciah Dashiel Butler Masters 2022-01-29 00:57:25 UTC
The PR merged right before code freeze, so I am setting target release back to 4.10.0.

Comment 8 Miciah Dashiel Butler Masters 2022-01-29 01:01:35 UTC
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.

Comment 10 Arvind iyengar 2022-01-31 07:52:49 UTC
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
------

Comment 13 Brandi Munilla 2022-02-10 20:24:52 UTC
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!

Comment 15 errata-xmlrpc 2022-03-10 16:04:21 UTC
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


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