openshift-ansible release fails if tag already exists

[adambkaplan]

openshift-ansible release fails if tag already exists

[adambkaplan]

@openshift/sig-developer-experience
@openshift/sig-continuous-delivery

[adambkaplan]

@openshift/sig-continuous-infrastructure

[adambkaplan]

odd...with a fresh Jenkins job the build succeeds: https://ci.openshift.redhat.com/jenkins/job/tmp_origin_tito_test/1/
However, existing jobs continue to fail.

[ingvagabund]

For some reason the tag already exists in the repo even before the github.com/openshift/openshift-ansible is pulled/synced.

Right after creating the AWS instance:

$ cd /data/src/github.com/openshift/openshift-ansible
$ git tag | grep 3.10.1-1
openshift-ansible-3.10.1-1
openshift-ansible-3.6.123.1001-1

So something is putting the tag into the repo during the "bake the base image" process.

[ingvagabund]

The job [1] already builds openshift-ansible-3.10.1 and adds the openshift-ansible-3.10.1-1 tag. @stevekuznetsov ? Do you know why?

[1] https://ci.openshift.redhat.com/jenkins/job/ami_build_origin_int_rhel_build/2885/consoleFull

[stevekuznetsov]

/assign @sdodson @smarterclayton

Is this the classic release branch mishap?

[stevekuznetsov]

In the jobs we build tag N+1 from the current branch, so this could also be a workspace caching problem:

• AMI was built from master after 3.9 and therefore created a workspace with 3.10
• master is updated to 3.10
• jobs using the AMI have a stale workspace and collide tags

We can release a new AMI this morning.

[stevekuznetsov]

Yeah, the working job is at image_stage: base and the broken job at image_stage: build. We need to publish a new build stage AMI, which should be happening on every commit to Origin. I will look into it.

/assign

[stevekuznetsov]

The job is building Origin and OpenShift Ansible but is asking for a pre-built AMI at the same time. The job should be reconfigured to use the base stage AMI instead.

/close