Hide Forgot
Looking at: https://atomic-e2e-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhelah-autobrew-7.3-treecompose/66/console I am confused with the docker versioning in http://pkgs.devel.redhat.com/cgit/rpms/docker/log/?h=extras-rhel-7.3 The version number seems to have gone backwards in Brew specifically: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=518021 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=520103 Which ordinarily may be OK except I think in this case one of the repos picked up an older build with a higher version.
I didn't think this would be an issue since the version that will be released next would be 1.10.3 and 1.12.1 is still ahead of it. Anyway, I can bump the Epoch if it's causing internal chaos.
Colin 7.3.0 is supposed to go out with 1.10.3 7.3.1 is going to go out with docker-1.12.*. The problem was that everything was frozen for 7.3.0 and we were working on 7.3.1, but then OpenShift found a problem which caused us to go up the docker-1.10 version for 7.3.0.
Ok, now we have a new issue in that when docker/docker-latest match, they conflict: https://atomic-e2e-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhelah-autobrew-7.3-treecompose/108/console 09:13:50 error: Error running transaction: file /usr/libexec/docker/docker-containerd conflicts between attemped installs of docker-latest-1.12.2-1.el7.x86_64 09:13:50 file /usr/libexec/docker/docker-containerd-shim conflicts between attemped installs of docker-latest-1.12.2-1.el7.x86_64 09:13:50 file /usr/libexec/docker/docker-ctr conflicts between attemped installs of docker-latest-1.12.2-1.el7.x86_64 09:13:50 file /usr/libexec/docker/docker-runc conflicts between attemped installs of docker-latest-1.12.2-1.el7.x86_64
https://atomic-e2e-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhelah-autobrew-7.3-treecompose/358/console
(In reply to Lokesh Mandvekar from comment #2) > I didn't think this would be an issue since the version that will be > released next would be 1.10.3 and 1.12.1 is still ahead of it. Anyway, I can > bump the Epoch if it's causing internal chaos. The damage is already done. I'm just letting you know that system administrators for years to come will look at this comment and say "This was the change. This is the starting point that started all our pain." It's too late now, but please, please, please do not use Epoch's so lightly.
(In reply to Troy Dawson from comment #8) > (In reply to Lokesh Mandvekar from comment #2) > > I didn't think this would be an issue since the version that will be > > released next would be 1.10.3 and 1.12.1 is still ahead of it. Anyway, I can > > bump the Epoch if it's causing internal chaos. > > The damage is already done. I'm just letting you know that system > administrators for years to come will look at this comment and say "This was > the change. This is the starting point that started all our pain." > > It's too late now, but please, please, please do not use Epoch's so lightly. Is there an option other than bumping Epoch when it comes to downgrading?