Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenShift plugin not deploying the Quarkus App (Regression Issue) #289

Closed
snowdrop-bot opened this issue Mar 5, 2021 · 0 comments
Closed
Assignees
Labels
7 - Community development upstream/closed The issue has been closed in the upstream repository

Comments

@snowdrop-bot
Copy link
Collaborator

Describe the bug
This is a regression issue caused by this commit: quarkusio@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 quarkusio@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: quarkusio@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.)


quarkusio#15487


$upstream:15487$

@snowdrop-bot snowdrop-bot added 7 - Community development upstream/closed The issue has been closed in the upstream repository labels Mar 5, 2021
@iocanel iocanel closed this as completed Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
7 - Community development upstream/closed The issue has been closed in the upstream repository
Projects
None yet
Development

No branches or pull requests

2 participants