qa/cephadm: add default container image name base#66847
Conversation
Recent runs in the new lab for cephadm jobs are hitting
```
2026-01-06T00:47:00.247 ERROR:teuthology.run_tasks:Saw exception from tasks.
Traceback (most recent call last):
File "/home/teuthworker/src/git.ceph.com_teuthology_8707f5d0ca0e547efc56a3734c7aa4a4cf45b1f4/teuthology/run_tasks.py", line 112, in run_tasks
manager.__enter__()
File "/usr/lib/python3.12/contextlib.py", line 137, in __enter__
return next(self.gen)
^^^^^^^^^^^^^^
File "/home/teuthworker/src/github.com_ceph_ceph-c_73712ccf0d7b99648a0c0d2ebf766adc13587a45/qa/tasks/cephadm.py", line 1961, in task
raise Exception("Configuration error occurred. "
Exception: Configuration error occurred. The 'image' value is undefined for 'cephadm' task. Please provide...
```
but it appears the build is still pushing images to quay.ceph.io/ceph-ci/ceph:<sha1>
which is the image we would be looking for. The bit that raises an exception if
this isn't set is quite old, and I'm unsure if we still need it or it's safe
to just assume this naming scheme can be used if an explicit image is
passed, but this seems worth a try
Signed-off-by: Adam King <adking@redhat.com>
|
Reading the description of this PR makes me wonder if some configuration from the teuthology.yaml didn't get brought over with the lab move? For example in my "local teuthology" I have: which seems like I must have put in to satisfy this requirement. IOW maybe the code should be left alone and the config updated? |
|
@adk3798 can you add this ticket to your commit? https://tracker.ceph.com/issues/74477 |
This is what happened and /etc/teuthology.yaml on soko04 has been modified as of a few minutes ago. |
Recent runs in the new lab for cephadm jobs are hitting
but it appears the build is still pushing images to quay.ceph.io/ceph-ci/ceph: which is the image we would be looking for. The bit that raises an exception if this isn't set is quite old, and I'm unsure if we still need it or it's safe to just assume this naming scheme can be used if an explicit image is passed, but this seems worth a try
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins test classic perfJenkins Job | Jenkins Job Definitionjenkins test crimson perfJenkins Job | Jenkins Job Definitionjenkins test signedJenkins Job | Jenkins Job Definitionjenkins test make checkJenkins Job | Jenkins Job Definitionjenkins test make check arm64Jenkins Job | Jenkins Job Definitionjenkins test submodulesJenkins Job | Jenkins Job Definitionjenkins test dashboardJenkins Job | Jenkins Job Definitionjenkins test dashboard cephadmJenkins Job | Jenkins Job Definitionjenkins test apiJenkins Job | Jenkins Job Definitionjenkins test docsReadTheDocs | Github Workflow Definitionjenkins test ceph-volume allJenkins Jobs | Jenkins Jobs Definitionjenkins test windowsJenkins Job | Jenkins Job Definitionjenkins test rook e2eJenkins Job | Jenkins Job DefinitionYou must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.