Configuration "helloworld-go" is waiting for a Revision to become ready. #2598
Comments
knative-prow-robot
added
area/networking
kind/bug
|
Could you please run |
|
@ZhiminXiang I think we need update the document a bit by adding a troubleshooting section in case people have this issue again, I will try to follow up with a PR soon. |
|
Here's what I get: I have also attached the output from |
|
I do see a lot of errors in the autoscaler logs |
|
I thought the logs might be indicating that the autoscaler didn't have access to API resources, but I just confirmed that
So the RBAC all seems OK, and it must be something else preventing the API requests from the autoscaler from working properly. |
|
@lizrice can you please try reinstall Knative, but using |
|
@tcnghia I'm seeing Not sure what I'm missing here. Looks like the pod is showing. |
|
@andrewrynhard the readiness probe in this case has not failed after the first 3m, so it is correct that pod is ready. It is still a long time to pass readiness though. Can you please try out the steps to further diagnose the issue https://github.com/knative/serving/blob/master/docs/debugging/application-debugging-guide.md#check-clusteringressistio-routing |
|
I'm getting the exact same issue with the PHP example, any pointers? dev/k8s/k8sfiles master ✗ 2d ✖ ⚑ ◒
▶ kubectl describe ksvc/helloworld-php
Name: helloworld-php
Namespace: default
Labels: <none>
Annotations: kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"serving.knative.dev/v1alpha1","kind":"Service","metadata":{"annotations":{},"name":"helloworld-php","namespace":"default"},...
API Version: serving.knative.dev/v1alpha1
Kind: Service
Metadata:
Creation Timestamp: 2019-01-24T20:57:05Z
Generation: 1
Resource Version: 15397
Self Link: /apis/serving.knative.dev/v1alpha1/namespaces/default/services/helloworld-php
UID: 9aed31cc-201a-11e9-855e-52540046b08b
Spec:
Generation: 1
Run Latest:
Configuration:
Revision Template:
Spec:
Container:
Env:
Name: TARGET
Value: HELLO WORLD!
Image: gcr.io/knative-samples/helloworld-php
Timeout Seconds: 300
Status:
Conditions:
Last Transition Time: 2019-01-24T20:57:05Z
Severity: Error
Status: Unknown
Type: ConfigurationsReady
Last Transition Time: 2019-01-24T20:57:05Z
Message: Configuration "helloworld-php" is waiting for a Revision to become ready.
Reason: RevisionMissing
Severity: Error
Status: Unknown
Type: Ready
Last Transition Time: 2019-01-24T20:57:05Z
Message: Configuration "helloworld-php" is waiting for a Revision to become ready.
Reason: RevisionMissing
Severity: Error
Status: Unknown
Type: RoutesReady
Latest Created Revision Name: helloworld-php-00001
Observed Generation: 1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Created 11s service-controller Created Configuration "helloworld-php"
Normal Created 11s service-controller Created Route "helloworld-php" |
|
can you please share |
▶ kubectl describe revision helloworld-php-00001
Name: helloworld-php-00001
Namespace: default
Labels: serving.knative.dev/configuration=helloworld-php
serving.knative.dev/configurationGeneration=1
serving.knative.dev/configurationMetadataGeneration=1
serving.knative.dev/service=helloworld-php
Annotations: <none>
API Version: serving.knative.dev/v1alpha1
Kind: Revision
Metadata:
Creation Timestamp: 2019-01-24T20:57:05Z
Generation: 1
Owner References:
API Version: serving.knative.dev/v1alpha1
Block Owner Deletion: true
Controller: true
Kind: Configuration
Name: helloworld-php
UID: 9aefad90-201a-11e9-855e-52540046b08b
Resource Version: 16369
Self Link: /apis/serving.knative.dev/v1alpha1/namespaces/default/revisions/helloworld-php-00001
UID: 9af15913-201a-11e9-855e-52540046b08b
Spec:
Container:
Env:
Name: TARGET
Value: HELLO WORLD!
Image: gcr.io/knative-samples/helloworld-php
Name:
Resources:
Generation: 1
Timeout Seconds: 300
Status:
Conditions:
Last Transition Time: 2019-01-25T15:10:49Z
Severity: Error
Status: True
Type: BuildSucceeded
Last Transition Time: 2019-01-25T15:11:15Z
Message: Unable to fetch image "gcr.io/knative-samples/helloworld-php": Get https://gcr.io/v2/: x509: certificate has expired or is not yet valid
Reason: ContainerMissing
Severity: Error
Status: False
Type: ContainerHealthy
Last Transition Time: 2019-01-25T15:11:15Z
Message: Unable to fetch image "gcr.io/knative-samples/helloworld-php": Get https://gcr.io/v2/: x509: certificate has expired or is not yet valid
Reason: ContainerMissing
Severity: Error
Status: False
Type: Ready
Last Transition Time: 2019-01-25T15:10:49Z
Severity: Error
Status: Unknown
Type: ResourcesAvailable
Log URL: http://localhost:8001/api/v1/namespaces/knative-monitoring/services/kibana-logging/proxy/app/kibana#/discover?_a=(query:(match:(kubernetes.labels.knative-dev%2FrevisionUID:(query:'9af15913-201a-11e9-855e-52540046b08b',type:phrase))))
Events: <none>
Exact same as my other issue here #2991 |
|
I am getting the same issue with one Java example. Any pointers? |
|
Can you do describe the revision as well? It might have the reason.
…On Sunday, February 24, 2019, Himanshu Pandey ***@***.***> wrote:
I am getting the same issue with one Java example. Any pointers?
kubectl describe ksvc helloworld-new-java
Name: helloworld-new-java
Namespace: default
Labels: <none>
Annotations: kubectl.kubernetes.io/last-applied-configuration={ <http://kubectl.kubernetes.io/last-applied-configuration=%7B>"apiVersion":"serving.knative.dev/v1alpha1","kind":"Service","metadata":{"annotations":{},"name":"helloworld-new-java","namespace":"default"},"spec":{...
serving.knative.dev/creator=minikube-user
serving.knative.dev/lastModifier=minikube-user
API Version: serving.knative.dev/v1alpha1
Kind: Service
Metadata:
Creation Timestamp: 2019-02-24T10:05:36Z
Generation: 1
Resource Version: 3640
Self Link: /apis/serving.knative.dev/v1alpha1/namespaces/default/services/helloworld-new-java
UID: bb0dd911-381b-11e9-9016-ba4545af638e
Spec:
Run Latest:
Configuration:
Revision Template:
Metadata:
Creation Timestamp: <nil>
Spec:
Container:
Env:
Name: TARGET
Value: himanshu Sample v1
Image: docker.io/xxxxx/helloworld-new-java
Name:
Resources:
Timeout Seconds: 300
Status:
Conditions:
Last Transition Time: 2019-02-24T10:05:36Z
Status: Unknown
Type: ConfigurationsReady
Last Transition Time: 2019-02-24T10:05:36Z
Message: Configuration "helloworld-new-java" is waiting for a Revision to become ready.
Reason: RevisionMissing
Status: Unknown
Type: Ready
Last Transition Time: 2019-02-24T10:05:36Z
Message: Configuration "helloworld-new-java" is waiting for a Revision to become ready.
Reason: RevisionMissing
Status: Unknown
Type: RoutesReady
Latest Created Revision Name: helloworld-new-java-z2pkx
Observed Generation: 1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Created 15m service-controller Created Configuration "helloworld-new-java"
Normal Created 15m service-controller Created Route "helloworld-new-java"
Normal Updated 15m (x2 over 15m) service-controller Updated Service "helloworld-new-java"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2598 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAurXzTRQW109pi32cbrYhL2JU_WJ0tgks5vQmhwgaJpZM4Y8dsb>
.
|
|
@vagababov Here is the describe on revision: It's saying |
|
So what happens when you do |
|
For pods, it's saying running but for deployments, its not available: So I am trying to run this sample app https://github.com/knative/docs/tree/master/serving/samples/helloworld-java and for that I need the domain to execute the java app. But domain is not giving any value: |
|
Well for whatever reason you don't have all 3 of the pods. Perhaps not
enough resources?
…On Mon, Feb 25, 2019 at 10:45 AM Himanshu Pandey ***@***.***> wrote:
For pods, it's saying running but for deployments, its not available:
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
hello-world-mon-6tzz6-deployment 1 1 1 0 17m
kubectl get pods
NAME READY STATUS RESTARTS AGE
hello-world-mon-6tzz6-deployment-56747cf7fd-5ps6q 2/3 Running 0 18m
So I am trying to run this sample app
https://github.com/knative/docs/tree/master/serving/samples/helloworld-java
and for that I need the domain to execute the java app. But domain is not
giving any value:
kubectl get ksvc hello-world-mon
NAME DOMAIN LATESTCREATED LATESTREADY READY REASON
hello-world-mon hello-world-mon-6tzz6 Unknown RevisionMissing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2598 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAurXxmTAdKLRyY0zX-MaptVa3IcPGkwks5vRC9VgaJpZM4Y8dsb>
.
|
|
@hpandeycodeit Looks like you only have 2 containers ready in your pod. could you please run After you identify the unready container, could you please also check the log of that container, and see what causes failure of starting the container? |
|
Here is the output : Looks like queue-proxy is not ready. |
|
Could you please also run |
|
This is giving connection refused error: |
|
So it seems your container did not spring up. Let me try to run the example myself. |
|
I just deployed the sample on my cluster and it worked from the first try. |
|
I have just had this for helloworld-python - it righted itself after 10 minutes, so I am wondering if it's simply really really slow to spin up. |
|
I am still facing this issue: I used istio-lean.yaml for istio installation. |
|
So are you using minicube? |
|
No I have a 2 node cluster, I tried with IP address of both nodes |
|
Why would the IP be 127.0.0.1 then? |
|
Sorry for the misleading configuration. I put random IP for the post. I used IP address I got from this: And my request is like: |
|
This gave me |
|
Hello, Warning InternalError 46m revision-controller failed to update deployment "minserver-one-v1-deployment": Operation cannot be fulfilled on deploymen and the log: e$ oc logs -f minserver-one-v1-deployment-6b454f955b-xddcd -c queue-proxy |
|
I met the similar revision missing issue when go through the tutorial from: https://knative.dev/docs/getting-started/first-service/ The local env/cli in my local machine list as below: The root reason is not clear to me after some debugging info. Then, I reinstalled the local k8s cluster with The helloworld-go can be created/accessed successfully finally. |
Expected Behavior
200 response from helloworld-go service
Actual Behavior
404 response from the helloworld-go service
Service always shows Configuration "helloworld-go" is waiting for a Revision to become ready
Steps to Reproduce the Problem
Additional Info
Although the symptoms are like #1971 I don't think the cause is the same, as the cluster isn't behind a proxy, and the image is being successfully pulled so accessing the registry isn't the problem.
I've attached the output from kubectl describe for related resources, and also the controller log.
configuration.txt
deploy.txt
ksvc.txt
pod.txt
revision.txt
route.txt
rs.txt
controller.log
The text was updated successfully, but these errors were encountered: