Details
-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Undefined
Description
Hi,
In the operator/templates team in our deployment tests of 3scale we are detecting that sometimes our tests fail due to some System/Zync managed routes not being created sometimes.
The issue doesn't always happen (some kind of race condition?).
You can see an example CircleCI execution where 3scale failed to deploy due to routes not being created. In this example case 3scale was deployed with templates:
https://app.circleci.com/pipelines/github/3scale/3scale-operator/2896/workflows/0cc23eae-130f-4f8c-95f5-156741d6d37c/jobs/20916
Notice how System's master route is not created (nor other expected routes)
In one of this CircleCI executions (not the above linked) I was able to get some more insights. In that execution case the routes I saw were:
circleci@default-d5fdc44e-b577-4fee-bbf0-b49e8542d8c2:~$ oc get routes NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD backend backend-3scale.lvh.me backend-listener http edge/Allow None zync-3scale-api-ckgms api-3scale-apicast-staging.lvh.me apicast-staging gateway edge/Redirect None zync-3scale-api-mrzvf api-3scale-apicast-production.lvh.me apicast-production gateway edge/Redirect None circleci@default-d5fdc44e-b577-4fee-bbf0-b49e8542d8c2:~$
As you can see, it seems some of the expected routes were not created for some reason (no master route, tenant route, ...).
I also attach zync and znc-que pod logs as they might be useful.
Note: This happens for all both provider routes and proxy routes.
Attachments
Issue Links
- relates to
-
THREESCALE-6835 Zync requires zync-que redeploy for routes to be created
- Closed
-
THREESCALE-6897 Zync-que stops creating routes after a while
- Closed