quayacm-review

[TomHutter]

If someone is wondering, why the lab grade quayacm-review passes, even there is still a yellow application object.

This due to the DO480-apps/quayacm-review/application.yaml file, which IMHO doesn't belong there. The budget-app application (resource) will be created in the hub cluster, when I create the application (in the dashboard). Due to the application.yaml file the application (created in the dashboard) will try to deploy the resource Application/budget-app in the managed cluster, which can't be accomplished as the CRDs for application are only installed in the hub cluster.

[gmac99]

My quayacm-review lab won't even start up. It fails on the Installing Quay step with error: 

• Playbook failed: quay_ install.yaml
• workstation: Create the Quay configuration secret with database auth: Failed to create object: b'{"kind": "Status", "apiVersion": "v1", "metadata": (},"s tatus": "Failure", "message": "secrets \\"init-config-bundle-secretl\" is forbidden: unable to create new content in namespace registry because it is being

t

erminated", "reason": "Forbidden", "details": {"name": "init-config-bundle-secret", "kind": "secrets", "causes": [{" reason": "NamespaceTerminating", "message": "names pace registry is being terminated", "field": "metadata.namespace"}]}, "code": 403}\n'
I have run lab finish quayacm-review and tried again, and also shutdown the servers and started them up again - both with no success and same error.

[Chetan_Tiwary_]

@gmac99 please delete the lab, recreate a fresh lab and then see if the lab start script works.

[gmac99]

That workaround does work, however, it usually takes 45 mins - 1h 15 mins before the environment is ready when building from scratch. It would be faster and more beneficial if it would work after starting the machines up after they are stopped each day.