Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

application redeployment is getting failed for OpenShift v3.7.0

See original GitHub issue

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

Issue Analytics

State:
Created 6 years ago
Comments:34 (14 by maintainers)

Top GitHub Comments

2reactions

mojshacommented, Jan 19, 2018

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

1reaction

piyush-gargcommented, Feb 16, 2018

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:deploy

Thanks

Top Results From Across the Web

application redeployment is getting failed for OpenShift v3.7

In redeploying scenario on OpenShift v3.7/minishift v1.7.0 may be Deployment/DeploymentConfig is not happening correctly.

Chapter 7. Troubleshooting OpenShift Container Platform 4.10

If worker node post-installation configuration fails, check Machine Config Operator (MCO) and DNS functionality. You can also verify system clock ...

Troubleshooting installations | OpenShift Container Platform 4.7

Investigating worker node installation issues · If the endpoint is unresponsive, verify load balancer configuration. · Verify that the MCO endpoint's DNS record ......

Troubleshooting Guide for OpenShift Container Platform

Pod related issues. Router/Registry Not deploying to correct node · Issues with Nodes. Nodes being reported as ready, but builds failing · Registry...

How to redeploy a Tomcat 7 application on Openshift

Once its sub-module project changes (the Tomcat application remains the same), the git push origin master doesn't work at all ( Everything up-to-date...