registry "disabling cross-mount" message cited as an error

[gabemontero]

In investigating the extended test failure https://ci.openshift.redhat.com/jenkins/job/origin_extended_image_tests/284

Deployment of the mongodb container failed

Looking at the registry logs for the run, the failures highlighted in this gist related to the mongodb container seem to line up from a time frame perspective (accounting for different logs using different timezones)

It is on a POST though, so perhaps it is not relevant ??? ... I see a fair amount of them throughout

@liggitt (by request of @bparees ) and @miminar (by request of @mfojtik ) - FYI

[liggitt]

The "disabling cross-mount" message is not an error, it means the push has to do a full layer push. Do you have the logs from the build push from the same time?

[miminar]

Thanks for the report. The error looks serious but it's not in fact. We need to lower the log level or change the way we log.

The error means: a user isn't authorized to mount from source repository during cross-repo mount. It will just cause a full blob upload.

[mfojtik]

iow. we have to make the error look less serious :-)

[gabemontero]

I managed to download the logs before ci.openshift went belly up. Let me dig up how I can upload them to file.rdu .... will re-post when they are up there.

[gabemontero]

http://file.rdu.redhat.com/gmontero/artifacts.zip

(fyi - I've deleted this now that ci.openshift is back up)

[gabemontero]

Well ... ci.openshift is back up ... artifacats.zip if available there of course.

When looking at https://ci.openshift.redhat.com/jenkins/job/origin_extended_image_tests/284/consoleFull

The line
Jun 30 01:47:24.144: INFO: Running 'oc get --namespace=extended-test-nodejs-mongodb-repo-test-okbs4-zeemh --config=/tmp/openshift/extended-test-nodejs-mongodb-repo-test-okbs4-zeemh-user.kubeconfig pods -o json'

Is the start of the debug from the extended test, after we've stopped waiting for the mongodb deployment to complete.

The deployment was started with:

Jun 30 01:45:38.247: INFO: Running 'oc deploy --namespace=extended-test-nodejs-mongodb-repo-test-okbs4-zeemh --config=/tmp/openshift/extended-test-nodejs-mongodb-repo-test-okbs4-zeemh-user.kubeconfig mongodb --latest'

[bparees]

let's keep these as separate issues. let the registry team use this issue to fix their logging.

[gabemontero]

fyi - i created a test PR to try to reproduce the extended test failure, running only the specific test in question.

So far, I have not been able to reproduce with that PR. Nor have I been able to reproduce locally.

[gabemontero]

per @bparees 's suggestion from June 30th, I updated the issues description to focus fixing the "disabling cross-mount" message.

We are tracking the deploy situation with the nodejs-mongodb extended tests via other threads.

[openshift-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
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

[bparees]

/remove-lifecycle rotten
/lifecycle frozen