Bug #17627
closedinconsistent package versions
0%
Description
Sorry for the poor title, but I'm not sure what's going on here.
I'm testing a teuthology PR that does tag->sha1 mapping before querying shaman, and I hit an unrelated issue. The job I'm looking at is:
http://qa-proxy.ceph.com/teuthology/zack-2016-10-19_15:22:27-upgrade:jewel-x-master-distro-basic-vps/486318/teuthology.log
First, teuthology queries shaman using this URL:
https://shaman.ceph.com/api/search/?status=ready&project=ceph&flavor=default&distros=ubuntu%2F14.04%2Fx86_64&ref=jewel
The first item in the result is:
{'archs': ['x86_64'],
'chacra_url': 'https://chacra.ceph.com/repos/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/ubuntu/trusty/flavors/default/',
'distro': 'ubuntu',
'distro_codename': 'trusty',
'distro_version': '14.04',
'extra': {'build_url': 'https://jenkins.ceph.com/job/ceph-build/ARCH=x86_64,AVAILABLE_ARCH=x86_64,AVAILABLE_DIST=trusty,DIST=trusty,MACHINE_SIZE=huge/188/',
'job_name': 'ceph-build/ARCH=x86_64,AVAILABLE_ARCH=x86_64,AVAILABLE_DIST=trusty,DIST=trusty,MACHINE_SIZE=huge',
'node_name': '158.69.75.252+xenial_trusty_pbuilder_huge__2cdfb58f-56a5-4001-9f68-93dc62bfe990',
'package_manager_version': '10.2.0-1trusty',
'root_build_cause': 'MANUALTRIGGER',
'version': '10.2.0'},
'flavor': 'default',
'modified': '2016-10-19 20:27:40.516792',
'project': 'ceph',
'ref': 'jewel',
'sha1': '3a9fba20ec743699b69bd0181dd6c54dc01c64b9',
'status': 'ready',
'url': 'https://chacra.ceph.com/r/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/ubuntu/trusty/flavors/default/'}
Note how it reports version: '10.2.0'
However, look at the packages themselves:
https://chacra.ceph.com/r/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/ubuntu/trusty/flavors/default/pool/main/c/ceph/
ceph-base_10.2.3-1trusty_amd64.deb 19-Oct-2016 18:50 52318782 ceph-base_10.2.3-1xenial_amd64.deb 19-Oct-2016 20:20 50114332 ceph-base_10.2.3-1xenial_arm64.deb 19-Oct-2016 20:21 44040482 ceph-base_10.2.3-1~bpo80+1_amd64.deb 19-Oct-2016 19:40 51342962 ceph-common-dbg_10.2.3-1trusty_amd64.deb 19-Oct-2016 20:13 227623294 ceph-common-dbg_10.2.3-1xenial_amd64.deb 19-Oct-2016 18:46 211041846 ceph-common-dbg_10.2.3-1xenial_arm64.deb 19-Oct-2016 19:00 208923884 ceph-common-dbg_10.2.3-1~bpo80+1_amd64.deb 19-Oct-2016 19:40 209801072 ceph-common_10.2.3-1trusty_amd64.deb 19-Oct-2016 18:55 13501002 ceph-common_10.2.3-1xenial_amd64.deb 19-Oct-2016 19:50 14157514 ceph-common_10.2.3-1xenial_arm64.deb 19-Oct-2016 20:20 12110014 ceph-common_10.2.3-1~bpo80+1_amd64.deb ...
Edit:
For reference: http://gitbuilder.ceph.com/ceph-deb-trusty-x86_64-basic/sha1/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/version -> 10.2.0-1trusty
Updated by Dan Mick over 7 years ago
Odd things about that first build returned from shaman:
- MANUALTRIGGER
- repo is on "chacra.ceph.com", not "n.chacra.."
whiskey tango...
Seems like that link https://chacra.ceph.com/r/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/ubuntu/trusty/flavors/default/ is just plain pointing to the wrong build
Updated by Andrew Schoen over 7 years ago
This repo you found is one I made trying to get older versions (in this case, 10.2.0) built and into chacra.ceph.com so that we can have repos for the upgrade tests.
I am confused why the repo does not contain the 10.2.0 binaries though, or perhaps they are but just named incorrectly. I was expected to see a combined repo though, because that's what chacra.ceph.com is configured to do for our upstream releases.
Another curious thing is that the binaries my build generated seem correct, it's just that they are not being included in the repo or otherwise renamed.
The build of 9.2.0 has the same issue. The binaries I got from the build all say 9.2.0, but the binaries in the repo are 9.2.1.
https://chacra.ceph.com/binaries/ceph/jewel/3a9fba20ec743699b69bd0181dd6c54dc01c64b9/ubuntu/xenial/
Updated by Andrew Schoen over 7 years ago
- Status changed from New to Resolved
- Assignee set to Andrew Schoen
Ok, I've got this resolved now. Long story short, chacra.ceph.com already had 10.2.3 binaries so when I rebuilt 10.2.0 and tried to make a repo reprepro ignored the older version of the binaries. The fix to that was to have chacra.ceph.com filter by sha1 when combining different debian versions into the same repo, this allows for ref/sha1 specific repos which is what we want.
This PR was that fix: https://github.com/ceph/chacra/pull/210
You can see in the repo that it now has the 10.2.0 binaries:
Let me know if having trusty and xenial in the same repo will be a problem, I don't imagine it will be though.