Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revision gets active before replicas are ready #15343

Open
johnugeorge opened this issue Jun 23, 2024 · 1 comment
Open

Revision gets active before replicas are ready #15343

johnugeorge opened this issue Jun 23, 2024 · 1 comment
Labels
area/API API objects and controllers kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@johnugeorge
Copy link
Contributor

In what area(s)?

/area API

What version of Knative?

v1.13

Expected Behavior

Revision should be ready only when all replicas are up

Actual Behavior

Revision is ready before all replicas are up

Steps to Reproduce the Problem

The cluster has resources only for 8 replicas for the knative service.

  1. Create a knative service with replica=4
    Observation: Revision is ready with all 4 running replica
  2. Delete the service
    Observation: Service is deleted and pods are getting terminated
  3. Create the same service(same name) with replica=10 immediately during the pod termination time(Note: Cluster doesn't have enough resources for 10 replicas)
    Revision becomes ready immediately when 1 replica is running.
    Knative service also becomes ready
    Here is the transitions that I observed

Initially

kubectl get revision

NAME                                  CONFIG NAME                     K8S SERVICE NAME   GENERATION   READY   REASON   ACTUAL REPLICAS   DESIRED REPLICAS

example-predictor-00001         example-predictor                                             1          True             1                 10

After some time,

k get revision

NAME                                  CONFIG NAME                     K8S SERVICE NAME   GENERATION   READY   REASON   ACTUAL REPLICAS   DESIRED REPLICAS

example-predictor-00001          example-predictor                                          1          True             8                 10
```

Note: The state doesn't recover once the problem has occured. Ready is always true but active status is Unknown.  
  
4. If I redo the same step 3 after pods are terminated,  revision active status and ready status is Unknown. Knative service is also unknown. 

@johnugeorge johnugeorge added the kind/bug Categorizes issue or PR as related to a bug. label Jun 23, 2024
@knative-prow knative-prow bot added the area/API API objects and controllers label Jun 23, 2024
@johnugeorge johnugeorge changed the title Revision get active before replicas are ready Revision gets active before replicas are ready Jun 25, 2024
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/API API objects and controllers kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant