fabric8-maven-plugin: application redeployment is getting failed for OpenShift v3.7.0
Description
If f8-m-p redeploy the existing application on OpenShift v3.7 then Deployment is not happening correctly. Its unable to pull the images and status appears ImgPullErr for a long time. After some time with 4-5 retries, it’s able to pull the image and deployment happen.
Info
This might be an issue with F8-M-P or OpenShift.
- f-m-p version : v3.5.34
- Maven version (
mvn -v) :
-
Kubernetes / OpenShift setup and version : OpenShift v3.7.0
-
If it’s a bug, how to reproduce :
- deploy the application using
mvn install or mvn fabric8:deploy - again invoke
mvn insall or mvn fabric8:deploy
- Sample project : [GitHub Clone URL] : https://github.com/fabric8io/fabric8-maven-plugin/tree/master/samples/spring-boot
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 34 (18 by maintainers)
Commits related to this issue
- Fixes #1130 Application redeployment is getting failed on OpenShift v3.7.0 + Added a workaround to deal with ImageTriggers. + Added flag fabric8.openshift.trimImageInContainerSpec which would trim ... — committed to rohanKanojia/fabric8-maven-plugin by rohanKanojia 6 years ago
- Fixes #1130 Application redeployment is getting failed on OpenShift v3.7.0 + Added a workaround to deal with ImageTriggers. + Added flag fabric8.openshift.trimImageInContainerSpec which would trim ... — committed to rohanKanojia/fabric8-maven-plugin by rohanKanojia 6 years ago
- Merge pull request #1176 from rohanKanojia/issue1130 Fixes #1130 Application redeployment is getting failed on OpenShift v3.7.0 — committed to fabric8io/fabric8-maven-plugin by deleted user 6 years ago
- Fixes #1130 Application redeployment is getting failed on OpenShift v3.7.0 + Added a workaround to deal with ImageTriggers. + Added flag fabric8.openshift.trimImageInContainerSpec which would trim ... — committed to valdar/fabric8-maven-plugin by rohanKanojia 6 years ago
- workaround for https://github.com/fabric8io/fabric8-maven-plugin/issues/1130 — committed to jamesfalkner/rhoar-getting-started by jamesfalkner 6 years ago
- workaround for https://github.com/fabric8io/fabric8-maven-plugin/issues/1130 — committed to jamesfalkner/rhoar-getting-started by jamesfalkner 6 years ago
@lordofthejars This is a OpenShift 3.7 issue for me. It’s actually a major blocker and preventing us from moving to OpenShift 3.7.
In OpenShift 3.6, it works fine.
Hey @valdar
FMP 3.5.35 has been released yesterday. It contains the workaround for redeployment on Openshift 3.7.x
You should hit for Openshift 3.7.x
mvn -Dfabric8.openshift.trimImageInContainerSpec=true fabric8:deployThanks
Okay, So I have found a temporary workaround for this. I saw discussion of @mojsha and Openshift guys here and I think until the Openshift guys solve this we can add that workaround solution. I’ve sent a pull request; after it gets merged, you won’t be facing this problem.
@hrishin @kameshsampath