phantomjinx commented on pull request #2711: URL: https://github.com/apache/camel-k/pull/2711#issuecomment-1010181350
> @squakez thanks! > Thx for looking into this @christophd > I believe the workflow is doing something like this > > ``` > kamel install --cluster-setup > > > kamel install -n $YAKS_NAMESPACE > ``` > > Where the cluster setup is done for namespace `default` and the 2nd install is done in a test namespace. The 2nd install command should install the Camel K operator and the Integration Platform right? > The first command is not really doing anything for the `default` namespace since `--cluster-setup` is only responsible for installing cluster-level resources, ie. cluster-roles and CRDS. > So right after the install the test starts and creates the integration. Maybe this is a racing condition where the Integration Platform has not been fully created yet but the test is already referencing a Kamelet? > > We can add `-w` option to the 2nd install command to make sure we wait for the platform to be running. Will look further into this .... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
