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) #15487

Closed
Sgitario opened this issue Mar 5, 2021 · 4 comments · Fixed by #15508
Closed

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

Sgitario opened this issue Mar 5, 2021 · 4 comments · Fixed by #15508
Assignees
Milestone

Comments

@Sgitario
Copy link
Contributor

Sgitario commented Mar 5, 2021

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.)

@Sgitario Sgitario added the kind/bug Something isn't working label Mar 5, 2021
@quarkus-bot
Copy link

quarkus-bot bot commented Mar 5, 2021

/cc @geoand

@Sgitario
Copy link
Contributor Author

Sgitario commented Mar 5, 2021

/cc @iocanel

@gsmet
Copy link
Member

gsmet commented Mar 5, 2021

@iocanel @geoand this one needs to be diagnosed quickly as this particular commit has been backported to 1.11.

@geoand
Copy link
Contributor

geoand commented Mar 5, 2021

I have assigned Ioannis to it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants