hernan-abi opened a new issue, #5924: URL: https://github.com/apache/camel-k/issues/5924
### What happened? Using the open-api trait succeeds in v2.4.x and fails in 2.5.0 with the same configuration/integration. I'm using a very basic open-api spec and integration. Basically a hello-world api example for testing. While the integration is deploying there is a Knative revision error that is referenced in the integration conditions: ``` Condition "Ready" is "False" for Integration open-api-test: Configuration "open-api-test" is waiting for a Revision to become ready ``` This is probably nothing, but when I was taking a look at the knative-service for both my integrations (v2.4.0 and v2.5.0), the 2.5.0 ksvc has the open-api source referenced as the first source. I don't recall seeing this before but I'll continue looking into this unless anyone's got an idea of what's causing the regression. <img width="1220" alt="Screen Shot 2024-11-05 at 17 45 55" src="https://github.com/user-attachments/assets/2b91f121-fe58-4acf-9b98-9504e36c196e";> ### Steps to reproduce 1. Take any functioning example using the open-api trait in v2.4.x 2. Apply this same configuration to a cluster installed with v2.5.0 3. A Revision error is thrown during deployment ### Relevant log output ```shell Progress: integration "open-api-test" in phase Running Condition "KnativeServiceAvailable" is "True" for Integration open-api-test: Knative service name is open-api-test Condition "DeploymentAvailable" is "False" for Integration open-api-test: controller strategy: knative-service (combined from similar events): Condition "ServiceTraitInfo" is "True" for Integration open-api-test: explicitly disabled by the platform: knative-service trait has priority over this trait (combined from similar events): Condition "SecurityContextTraitInfo" is "True" for Integration open-api-test: explicitly disabled by the platform: pod security context is disabled for Knative Service. PodSecurityContext properties can affect non-user sidecar containers that come from Knative or your service mesh. Use container security context instead. (combined from similar events): Condition "TraitInfo" is "True" for Integration open-api-test: Applied traits: camel,environment,logging,deployer,gc,knative-service,container,mount,pull-secret,quarkus,jvm,owner (combined from similar events): Condition "Ready" is "False" for Integration open-api-test Integration "open-api-test" in phase "Running" (combined from similar events): Condition "Ready" is "False" for Integration open-api-test: The Route is still working to reflect the latest desired specification. (combined from similar events): Condition "Ready" is "False" for Integration open-api-test: Configuration "open-api-test" is waiting for a Revision to become ready. 2024-11-05T16:11:03-05:00 ERROR camel-k.scraper.pod error caught during log scraping {"name": "open-api-test-00001-deployment-75f4d6dd56-fl8gg", "error": "no state change after 30 seconds ``` ### Camel K version v2.4.0, v2.5.0 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
