OpenShift unable to complete deployment

[galderz]

Hi,

I'm using OpenShift 3.7.1 and Fabric 8 maven plugin version 3.5.33.

Sometimes when I call mvn fabric8:deploy OpenShift cannot complete deployment, I see these messages appearing in the event log in a loop:

3:19:08 PM | app-5-x5np6 | Pod | Normal | Back-off | Back-off pulling image "app:latest"6 times in the last 2 minutes
-- | -- | -- | -- | -- | --
3:19:08 PM | app-5-x5np6 | Pod | Warning | Failed | Error: ImagePullBackOff6 times in the last 2 minutes
3:18:37 PM | app-5-x5np6 | Pod | Warning | Failed | Error: ErrImagePull4 times in the last 2 minutes
3:18:37 PM | app-5-x5np6 | Pod | Warning | Failed | Failed to pull image "app:latest": rpc error: code = 2 desc = Error response from daemon: {"message":"repository app not found: does not exist or no pull access"}4 times in the last 2 minutes
3:18:35 PM | app-5-x5np6 | Pod | Normal | Pulling | pulling image "app:latest"

Any idea what could be causing it? I'm using oc cluster up and a Mac with Docker 1.13.1.

Cheers,
Galder

[galderz]

I've been doing some testing with 3.6.1 and seems to work fine so far...

[galderz]

I've created an issue in the Fabric8 Maven Plugin, but they're hinting this is actually a problem with OpenShift itself. Anyone care to comment?

[csrwng]

@galderz after you run mvn fabric8:deploy can you inspect the following in OpenShift and include the results in a gist?

oc get is -o yaml
oc get builds -o yaml
oc get dc -o yaml

I don't think this is Mac specific. It looks like the image that the deployment config expects is not getting tagged in the image stream.

[galderz]

This appears to be a known issue now:
#18406 (comment) (via fabric8io/fabric8-maven-plugin#1130 (comment))

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close