base_ami failing due to oc ex dockerbuild image name regex failures

[danmcp]

https://ci.openshift.redhat.com/jenkins/job/base_ami/1990/console

Stdout from the command:

Building base images...
/data/src/github.com/openshift/origin ~
++ Building go targets for linux/amd64: cmd/oc
++ Placing binaries
/data/src/github.com/openshift/origin/hack/build-go.sh took 124 seconds


Stderr from the command:

--> Image centos:centos7 was not found, pulling ...
error: API error (500): repository name component must match "[a-z0-9](?:-*[a-z0-9])*(?:[._][a-z0-9](?:-*[a-z0-9])*)*"
!!! Error in hack/build-base-images.sh:28
    '"${oc}" ex dockerbuild $2 $1' exited with status 1
Call stack:
    1: hack/build-base-images.sh:28 build(...)
    2: hack/build-base-images.sh:32 main(...)
Exiting with status 1
Build step 'Execute shell' marked build as failure

[smarterclayton]

Hrm, thought we solved this.

[danmcp]

https://ci.openshift.redhat.com/jenkins/job/base_ami/2023/console

[danmcp]

https://ci.openshift.redhat.com/jenkins/job/devenv_ami/4598/console

[danmcp]

@jwforres @stevekuznetsov This appears to be totally blocking pushing images.

[stevekuznetsov]

@smarterclayton do you have bandwidth to look at this today?

[smarterclayton]

Can you print out the arguments to oc ex dockerbuild and turn on loglevel=5?

[danmcp]

Just got this one this morning: https://ci.openshift.redhat.com/jenkins/job/devenv_ami/4660/console

[smarterclayton]

That's a different bug.

On Mon, Jul 25, 2016 at 10:23 AM, Dan McPherson notifications@github.com
wrote:

Just got this one this morning:
https://ci.openshift.redhat.com/jenkins/job/devenv_ami/4660/console

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#9269 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_pxUNxLAw6_EheeFF0t1HNQ_5ze3tks5qZMbQgaJpZM4Iy8q-
.

[danmcp]

@smarterclayton I can open a new issue then. Who should be the owner?

[smarterclayton]

Definitely not the scratch issue.

On Mon, Jul 25, 2016 at 10:36 AM, Clayton Coleman ccoleman@redhat.com
wrote:

That's a different bug.

On Mon, Jul 25, 2016 at 10:23 AM, Dan McPherson notifications@github.com
wrote:

Just got this one this morning:
https://ci.openshift.redhat.com/jenkins/job/devenv_ami/4660/console

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#9269 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_pxUNxLAw6_EheeFF0t1HNQ_5ze3tks5qZMbQgaJpZM4Iy8q-
.

[stevekuznetsov]

@smarterclayton I'm seeing this in the log:

Building base images...
/data/src/github.com/openshift/origin ~
--> Image centos:centos7 was not found, pulling ...
error: API error (500): repository name component must match "[a-z0-9](?:-*[a-z0-9])*(?:[._][a-z0-9](?:-*[a-z0-9])*)*"
[ERROR] PID 2624: hack/build-base-images.sh:27: `'/data/src/github.com/openshift/origin/_output/local/bin/linux/amd64/oc' ex dockerbuild /data/src/github.com/openshift/origin/images/base openshift/origin-base` exited with status 1.
[INFO]      Stack Trace: 
[INFO]        1: hack/build-base-images.sh:27: `'/data/src/github.com/openshift/origin/_output/local/bin/linux/amd64/oc' ex dockerbuild /data/src/github.com/openshift/origin/images/base openshift/origin-base`
[INFO]        2: hack/build-base-images.sh:31: build
[INFO]   Exiting with code 1.

Why is that a different issue than this one? The failure cause for this one picks it up.

[smarterclayton]

No it's fine - it's same symptom (so title is correct), just different
place it's failing

On Mon, Jul 25, 2016 at 10:42 AM, Dan McPherson notifications@github.com
wrote:

@smarterclayton https://github.com/smarterclayton I can open a new
issue then. Who should be the owner?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#9269 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_pyGXRiauywzdhT5yz2bWoiIPUY_gks5qZMtfgaJpZM4Iy8q-
.

[smarterclayton]

Docker 1.9 has different PullImage semantics in the API - it looks like a
call that works in Docker 1.10 fails in 1.9 and vice versa. Good to know...

On Mon, Jul 25, 2016 at 10:51 AM, Clayton Coleman ccoleman@redhat.com
wrote:

No it's fine - it's same symptom (so title is correct), just different
place it's failing

On Mon, Jul 25, 2016 at 10:42 AM, Dan McPherson notifications@github.com
wrote:

@smarterclayton https://github.com/smarterclayton I can open a new
issue then. Who should be the owner?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#9269 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_pyGXRiauywzdhT5yz2bWoiIPUY_gks5qZMtfgaJpZM4Iy8q-
.