-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Deployment of new version of application with OpenShift extension fails with LabelSelectorRequirement(nil)}: field is immutable
#39180
Comments
This might be related to a recent change that removes some selectors that are not needed. Meanwhile, I'll try to have a look and see if there is something else we can / need to do. |
Right. But just to be clear, I'd need to do this on every deployment, because the problem occurs again on the next deployment. It's not just some old, stale resource definition causing trouble.
Thanks. |
I managed to reproduce the issue by changing the version of the application which ends up being used in the LabelSelector of Deployments. This behavior is controlled by: Apparently, DeploymentConfig treated selectors a bit differently (AFAIR, it used its own Selector implementation) and that's why you haven't encountered the issue before. One option is to improve the error message, the other is to detect such conflicts and delete. I am a bit skeptic about the potential side effects of the later. |
Thanks, I'll try setting Another option would be to have |
See quarkusio/quarkus#39180 for more details.
Describe the bug
Hey @iocanel I noticed something odd lately when deploying with the OpenShift extension... Opening as a bug since I'm not quite sure, but feel free to requalify.
It seems that the deployment fails because a selector includes the app version (the git SHA in this case), and selectors are immutable:
I don't think I personally changed anything in this area in my app, so... could it be related to the switch from DeploymentConfig to Deployment?
More importantly, should this be addressed/documented in the extension, since it's apparently the default behavior, and it used to work fine?
See https://github.com/quarkusio/quarkus-github-lottery/actions/runs/8142539385/job/22252314385
Expected behavior
Deployment should erase the previous version of the application -- at least it used to.
Actual behavior
Deployment fails:
How to Reproduce?
Deploy a new version of an application without removing the previous version one.
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
3.8.1
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: