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

[online] The route is not accepting traffic yet because it has not been admitted by a router. #6086

Closed
syui opened this Issue Nov 2, 2017 · 11 comments

Comments

Projects
None yet
6 participants
@syui

syui commented Nov 2, 2017

I am using OpenShift Online Starter.

However, errors are generated when creating Routes.

$ oc expose svc/xxxxx

The route is not accepting traffic yet because it has not been admitted by a router.

https://docs.openshift.com/online/dev_guide/routes.html

@ahardin-rh

This comment has been minimized.

Show comment
Hide comment
@ahardin-rh

ahardin-rh Nov 2, 2017

Contributor

@tiwillia @Miciah Please advise

Contributor

ahardin-rh commented Nov 2, 2017

@tiwillia @Miciah Please advise

@ahardin-rh ahardin-rh self-assigned this Nov 2, 2017

@syui

This comment has been minimized.

Show comment
Hide comment
@syui

syui Nov 3, 2017

I solved the problem.

But this time a new problem has occurred.

An error occurred creating the route.

An error occurred creating the route. Reason: Route "xxxxx" is invalid: spec.host: Forbidden: you do not have permission to set the host field of the route

No Create Route

syui commented Nov 3, 2017

I solved the problem.

But this time a new problem has occurred.

An error occurred creating the route.

An error occurred creating the route. Reason: Route "xxxxx" is invalid: spec.host: Forbidden: you do not have permission to set the host field of the route

No Create Route

@syui

This comment has been minimized.

Show comment
Hide comment
@syui

syui Nov 3, 2017

In addition, if you do not reload many times Application is not available.

example : http://cachet-tapp.1d35.starter-us-east-1.openshiftapps.com/

syui commented Nov 3, 2017

In addition, if you do not reload many times Application is not available.

example : http://cachet-tapp.1d35.starter-us-east-1.openshiftapps.com/

@mrinx

This comment has been minimized.

Show comment
Hide comment
@mrinx

mrinx Nov 3, 2017

@syui, can you tell me how did you solve the problem?

I still have a problem with my route, no matter how long I wait.

... either the administrator has not installed a router or the router is not selecting this route.

I'm also on 1d35.starter-us-east-1.openshiftapps.com

mrinx commented Nov 3, 2017

@syui, can you tell me how did you solve the problem?

I still have a problem with my route, no matter how long I wait.

... either the administrator has not installed a router or the router is not selecting this route.

I'm also on 1d35.starter-us-east-1.openshiftapps.com

@syui

This comment has been minimized.

Show comment
Hide comment
@syui

syui Nov 3, 2017

@mrinx sorry, I put timed.

The error disappeared the day after I wrote the issue.

syui commented Nov 3, 2017

@mrinx sorry, I put timed.

The error disappeared the day after I wrote the issue.

@jkkj93

This comment has been minimized.

Show comment
Hide comment
@jkkj93

jkkj93 Nov 5, 2017

I met the same problem as syui.

jkkj93 commented Nov 5, 2017

I met the same problem as syui.

@MartinMelis21

This comment has been minimized.

Show comment
Hide comment
@MartinMelis21

MartinMelis21 Nov 5, 2017

Currently facing the same issue (using Starter plan). Having a Java application on Tomcat 7, built and deployed currectly (curl 0.0.0.0:8080 on the pod works fine), but unable to create the route.
Progress message: The route is not accepting traffic yet because it has not been admitted by a router.

After checking oc adm router --dry-run error is returned: Router "router" service does not exist.

After trying to create a router with oc adm router
error pops up: router could not be created; could not retrieve list of security constraints to verify service account "router": User "martinmelis" cannot list all securitycontextconstraints in the clu
ster

MartinMelis21 commented Nov 5, 2017

Currently facing the same issue (using Starter plan). Having a Java application on Tomcat 7, built and deployed currectly (curl 0.0.0.0:8080 on the pod works fine), but unable to create the route.
Progress message: The route is not accepting traffic yet because it has not been admitted by a router.

After checking oc adm router --dry-run error is returned: Router "router" service does not exist.

After trying to create a router with oc adm router
error pops up: router could not be created; could not retrieve list of security constraints to verify service account "router": User "martinmelis" cannot list all securitycontextconstraints in the clu
ster

@Miciah

This comment has been minimized.

Show comment
Hide comment
@Miciah

Miciah Nov 6, 2017

Contributor

@syui and @jkkj93, custom domains is only included as part of the Pro plan, not Starter. This is documented in the plan descriptions, but the restriction on custom domains was not consistently enforced on Starter, so confusion is understandable. Besides that, are you still seeing problems?

@mrinx and @MartinMelis21, can you provide the output of oc get routes -o json? Perhaps there will be more information in the route .spec or .status fields.

Note that the router can take a few minutes to admit a route during times of high contention.

Note also that oc adm commands are generally intended for the cluster administrator to use.

Contributor

Miciah commented Nov 6, 2017

@syui and @jkkj93, custom domains is only included as part of the Pro plan, not Starter. This is documented in the plan descriptions, but the restriction on custom domains was not consistently enforced on Starter, so confusion is understandable. Besides that, are you still seeing problems?

@mrinx and @MartinMelis21, can you provide the output of oc get routes -o json? Perhaps there will be more information in the route .spec or .status fields.

Note that the router can take a few minutes to admit a route during times of high contention.

Note also that oc adm commands are generally intended for the cluster administrator to use.

@mrinx

This comment has been minimized.

Show comment
Hide comment
@mrinx

mrinx Nov 6, 2017

@Miciah, I have a working route now, it started working for me again on Saturday, I didn't mess with it since then. In my case it took longer than minutes, it was in hours. And before that I was waiting a whole day or so - without any success.

Do I understand correctly, that the creationTimestamp is the time I asked for the route to be created, and the lastTransitionTime is the time when the route was accepted by the router?

    "apiVersion": "v1",
    "items": [
        {
            "apiVersion": "v1",
            "kind": "Route",
            "metadata": {
                "annotations": {
                    "openshift.io/host.generated": "true"
                },
                "creationTimestamp": "2017-11-03T17:34:09Z",
                ...
            },
            "spec": {
                "host": "x-y.1d35.starter-us-east-1.openshiftapps.com",
                "port": {
                    "targetPort": "8080-tcp"
                },
                "to": {
                    "kind": "Service",
                    "name": "x",
                    "weight": 100
                },
                "wildcardPolicy": "None"
            },
            "status": {
                "ingress": [
                    {
                        "conditions": [
                            {
                                "lastTransitionTime": "2017-11-04T05:41:27Z",
                                "status": "True",
                                "type": "Admitted"
                            }
                        ],
                        ...
                    }
                ]
            }
        }
    ],
    ...
}

mrinx commented Nov 6, 2017

@Miciah, I have a working route now, it started working for me again on Saturday, I didn't mess with it since then. In my case it took longer than minutes, it was in hours. And before that I was waiting a whole day or so - without any success.

Do I understand correctly, that the creationTimestamp is the time I asked for the route to be created, and the lastTransitionTime is the time when the route was accepted by the router?

    "apiVersion": "v1",
    "items": [
        {
            "apiVersion": "v1",
            "kind": "Route",
            "metadata": {
                "annotations": {
                    "openshift.io/host.generated": "true"
                },
                "creationTimestamp": "2017-11-03T17:34:09Z",
                ...
            },
            "spec": {
                "host": "x-y.1d35.starter-us-east-1.openshiftapps.com",
                "port": {
                    "targetPort": "8080-tcp"
                },
                "to": {
                    "kind": "Service",
                    "name": "x",
                    "weight": 100
                },
                "wildcardPolicy": "None"
            },
            "status": {
                "ingress": [
                    {
                        "conditions": [
                            {
                                "lastTransitionTime": "2017-11-04T05:41:27Z",
                                "status": "True",
                                "type": "Admitted"
                            }
                        ],
                        ...
                    }
                ]
            }
        }
    ],
    ...
}
@syui

This comment has been minimized.

Show comment
Hide comment
@syui

syui commented Nov 6, 2017

@Miciah No

@jkkj93

This comment has been minimized.

Show comment
Hide comment
@jkkj93

jkkj93 Nov 7, 2017

@Miciah Got it.Thank you for answering.

jkkj93 commented Nov 7, 2017

@Miciah Got it.Thank you for answering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment