You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This is a regression issue caused by this commit: 588db63
When using the OpenShift Quarkus extension to deploy our Quarkus app:
mvn package -Dquarkus.kubernetes.deploy=true
Then, the BuildConfig and the Build are triggered in OpenShift and when the Build instance finished, It's deleted (see the commit changes). Then, the DeploymentConfig does not trigger the application startup spite of the image stream is there. For some reason, the DeploymentConfig depends on the build instance to not be deleted.
After reverting the changes in 588db63, the Build instance is not deleted and hence everything works fine.
To Reproduce
For your Quarkus application:
mvn package -Dquarkus.kubernetes.deploy=true
The application will not be deployed into OpenShift. The same works for 1.12.0.Final and also by reverting the commit: 588db63
Environment (please complete the following information):
OpenShift: 4.6
Quarkus version or git rev: 1.12.1.Final, 999-SNAPSHOT
Additional context
(Add any other context about the problem here.)
The text was updated successfully, but these errors were encountered:
Describe the bug
This is a regression issue caused by this commit: 588db63
When using the OpenShift Quarkus extension to deploy our Quarkus app:
Then, the BuildConfig and the Build are triggered in OpenShift and when the Build instance finished, It's deleted (see the commit changes). Then, the DeploymentConfig does not trigger the application startup spite of the image stream is there. For some reason, the DeploymentConfig depends on the build instance to not be deleted.
After reverting the changes in 588db63, the Build instance is not deleted and hence everything works fine.
To Reproduce
For your Quarkus application:
The application will not be deployed into OpenShift. The same works for 1.12.0.Final and also by reverting the commit: 588db63
Environment (please complete the following information):
Additional context
(Add any other context about the problem here.)
The text was updated successfully, but these errors were encountered: