Actions
Bug #50113
closedUpgrading to v16 breaks rgw_frontends setting
Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Community (user)
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
We are upgrading our cluster to v16 today with cephadm.
We have rgw daemons set up and the "rgw_frontends" config is left at its default (beast port=7480)
However, when upgrading, cephadm seems want to redeploy all rgw daemons. It set "rgw_frontends" config for new daemons to "beast port=80", which of course breaks our existing applications. Besides, We have other daemon listening on port 80. so we continuously get errors like:
mgr.gpu024.bapbcz (mgr.6544553) 113 : cephadm [INF] Deploying daemon rgw.smil.b7-1.gpu013.zshphp on gpu013 mgr.gpu024.bapbcz (mgr.6544553) 114 : cephadm [ERR] cephadm exited with an error code: 1, stderr:Deploy daemon rgw.smil.b7-1.gpu013.zshphp ... Verifying port 80 ... Cannot bind to IP 0.0.0.0 port 80: [Errno 98] Address already in use ERROR: TCP Port(s) '80' required for rgw already in use Traceback (most recent call last): File "/usr/share/ceph/mgr/cephadm/serve.py", line 1172, in _remote_connection yield (conn, connr) File "/usr/share/ceph/mgr/cephadm/serve.py", line 1087, in _run_cephadm code, '\n'.join(err))) orchestrator._interface.OrchestratorError: cephadm exited with an error code: 1, stderr:Deploy daemon rgw.smil.b7-1.gpu013.zshphp ... Verifying port 80 ... Cannot bind to IP 0.0.0.0 port 80: [Errno 98] Address already in use ERROR: TCP Port(s) '80' required for rgw already in use mgr.gpu024.bapbcz (mgr.6544553) 115 : cephadm [INF] Removing key for client.rgw.smil.b7-1.gpu013.zshphp
and the deployment of rgw cannot proceed.
We ended up stopping our daemon on 80 port to let it proceed, then fix the config and restart all rgw daemons manually.
Actions