mgr/cephadm: nfs migration: avoid port conflicts#44482
Conversation
The nfs upgrade renames the nfs spec from `nfs.ganesha-{service_id}`
to `nfs.{service_id}`. Previously we used the orphan-daemon check
to remove the old `nfs.ganesha-{service_id}` daemons. This does not work
as sometimes serve() tries to deploy the new daemons before cleaning up the
old daemons. This results in a port conflict breaking the upgrade.
Fixes: https://tracker.ceph.com/issues/53424
Signed-off-by: Sebastian Wagner <sewagner@redhat.com>
|
Teuthology Run Report: Unrelated Failures:
The dead jobs numbering 9 are unrelated as well. |
|
jenkins test this please |
|
jenkins test docs |
|
jenkins test api |
1 similar comment
|
jenkins test api |
|
@sebastian-philipp @adk3798 this is ready for merge. Failing tests |
|
jenkins test docs |
The nfs upgrade renames the nfs spec from
nfs.ganesha-{service_id}to
nfs.{service_id}. Previously we used the orphan-daemon checkto remove the old
nfs.ganesha-{service_id}daemons. This does not workas sometimes serve() tries to deploy the new daemons before cleaning up the
old daemons. This results in a port conflict breaking the upgrade.
Fixes: https://tracker.ceph.com/issues/53424
Signed-off-by: Sebastian Wagner sewagner@redhat.com
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume tox