Bug 1920454 - oc idle functionality does not work with OpenShift 4.6
Summary: oc idle functionality does not work with OpenShift 4.6
Keywords:
Status: CLOSED DUPLICATE of bug 1900989
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: aos-network-edge-staff
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-26 11:01 UTC by Rejeeb
Modified: 2024-03-25 18:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-28 16:35:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rejeeb 2021-01-26 11:01:35 UTC
Description of problem:

`oc idle` functionality is not working with OpenShift 4.6. Once the pods are idled, it is not re-instated once the traffic flows in.

Version-Release number of selected component (if applicable):

OpenShift v4.6.12

How reproducible:

100%

Steps to Reproduce:
1. Create a new-app and idle the pods:

# oc new-app httpd
# oc expose svc httpd
# oc idle httpd

2. Try cURL to the URL:

[quicklab@upi-0 ~]$ curl -kvv server-test.apps.ocp468cluster.lab.upshift.rdu2.redhat.com
* About to connect() to server-test.apps.ocp468cluster.lab.upshift.rdu2.redhat.com port 80 (#0)
..
      <h1>Application is not available</h1>
      <p>The application is currently not serving requests at this endpoint. It may not have been started or is still starting.</p>

      <div class="alert alert-info">
        <p class="info">
          Possible reasons you are seeing this page:
        </p>
        <ul>
          <li>
            <strong>The host doesn't exist.</strong>
            Make sure the hostname was typed correctly and that a route matching this hostname exists.
          </li>
          <li>
            <strong>The host exists, but doesn't have a matching path.</strong>
            Check if the URL path was typed correctly and that the route was created using the desired path.
          </li>
          <li>
            <strong>Route and path matches, but all pods are down.</strong>
            Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.
          </li>
..


Actual results:

The pods are not getting invoked once the traffic flows in.

Expected results:

Pods should re-scale once the traffic flows in.

Additional info:

Had tested this issue with OpenShift 4.5 and it was working as expected, only OpenShift 4.6 is affected it seems.

Comment 2 zhaozhanqi 2021-01-26 13:07:32 UTC
I checked on 4.6.12, when idle service.  curl serviceip:$port can make the pod scale up. So guess this issue happen on routing side.

Comment 3 zhaozhanqi 2021-01-28 06:26:45 UTC
Move this bug to routing component,  and there is already bug https://bugzilla.redhat.com/show_bug.cgi?id=1900989 to trace this issue.

Comment 4 Andrew McDermott 2021-01-28 16:35:30 UTC

*** This bug has been marked as a duplicate of bug 1900989 ***

Comment 5 Red Hat Bugzilla 2023-09-15 01:32:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days


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