qa/tasks: disable agent at end of iscsi test#66613
qa/tasks: disable agent at end of iscsi test#66613
Conversation
The cephadm agent is sometimes deployed during orch tests (determined by these yaml files: https://github.com/ceph/ceph/tree/main/qa/suites/orch/cephadm/smoke/agent). During the `test_iscsi_container` task, we execute several workunits to test iscsi. Throughout the test, if the agent was deployed, it sends metadata to a cephadm endpoint. At the end of the test, we disable cephadm and shut down the cluster. However, the agent is still deployed and trying to connect to cephadm, which it fails at since cephadm was disabled. The solution is to disable the agent during teardown via: ``` ceph config set mgr mgr/cephadm/use_agent false ``` Once set to false, the agent service will be stopped and the daemons will be removed automatically by cephadm. Fixes: https://tracker.ceph.com/issues/68586 Signed-off-by: Laura Flores <lflores@ibm.com>
|
jenkins test make check |
|
Thanks for the feedback. I'll run some tests on this once the lab migration is complete. I would rather to this than put it into one of Yuri's batches since I'm not 100% confident that this will function how I expect it to. |
|
jenkins test make check |
|
@ljflores did you manage to a have green/good run with this change? if that's the case we can go ahead and merge the PR. |
Oops, I need to return to this. I had scheduled some runs that failed from lab issues. Trying again. |
|
The test failed because teuthology deletes the https://pulpito.ceph.com/lflores-2026-02-06_22:21:29-rados:cephadm-main-distro-default-trial/38542 |
upssss I see, thanks @ljflores for re-testing it. |
The cephadm agent is sometimes deployed during orch tests (determined by these yaml files: https://github.com/ceph/ceph/tree/main/qa/suites/orch/cephadm/smoke/agent).
During the
test_iscsi_containertask, we execute several workunits to test iscsi. Throughout the test, if the agent was deployed, it sends metadata to a cephadm endpoint. At the end of the test, we disable cephadm and shut down the cluster. However, the agent is still deployed and trying to connect to cephadm, which it fails at since cephadm was disabled.The solution is to disable the agent during teardown via:
Once set to false, the agent service will be stopped and the daemons will be removed automatically by cephadm.
Fixes: https://tracker.ceph.com/issues/68586
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.