Bug #46353
closedqa: Impossible to run rados/cephadm suite against master branch
0%
Description
It's a well-known fact that the named branches (master, octopus, etc.) do not exist in https://github.com/ceph/ceph-ci.git but, rather, in https://github.com/ceph/ceph.git
Still, these branches do get built by Jenkins/Chacra/Shaman and it is possible (and frequently done) to run teuthology suites against them by specifying e.g.:
teuthology-suite --ceph-repo https://github.com/ceph/ceph --ceph master --suite-repo https://github.com/ceph/ceph --suite-branch master
(usually the --newest option is also provided, since the very most recent tip of master might not yet have finished building).
This does not currently work well with the cephadm.py task, though, because it defaults to looking for the ceph container image on "quay.ceph.io/ceph/ceph-ci" when it should be looking on "quay.ceph.io/ceph/ceph", instead.
Sample failure: https://pulpito.ceph.com/smithfarm-2020-07-03_15:13:03-rados:cephadm:smoke-master-distro-basic-smithi/
Updated by Nathan Cutler almost 4 years ago
- Status changed from New to In Progress
Updated by Nathan Cutler almost 4 years ago
- Status changed from In Progress to New
- Assignee changed from Nathan Cutler to David Galloway
Updated by Nathan Cutler almost 4 years ago
- Project changed from Orchestrator to sepia
@David, is it feasible for pushes to "master" and "octopus" on ceph/ceph.git to trigger container builds?
Updated by David Galloway almost 4 years ago
Nathan Cutler wrote:
@David, is it feasible for pushes to "master" and "octopus" on ceph/ceph.git to trigger container builds?
See https://github.com/ceph/ceph/pull/35928#issuecomment-657557538. We are. AFAIK, this is how we were doing it when we were using quay.io as well. Both the ceph-dev (ceph.git) and ceph-dev-new (ceph-ci.git) Jenkins jobs pushed to the same quay.io ceph/ceph-ci container repo.
Is combining them an issue? In theory, they're all dev containers. The release containers go to dockerhub: https://hub.docker.com/r/ceph/ceph/tags
Updated by Nathan Cutler over 3 years ago
What one has to do is find the latest master SHA1 that has a container built. Do this by:
1. point browser at https://shaman.ceph.com/builds/ceph/master
2. find the latest master SHA1 that has all the OS builds you need (all must have green color)
3. point browser at https://quay.ceph.io/repository/ceph-ci/ceph?tag=latest&tab=tags
4. paste the SHA1 into the "filter tags" field (this should find a container image tagged with the SHA1)
5. paste the SHA1 into your teuthology-suite command: teuthology-suite --sha1 PASTE_IT_HERE