Red Hat Bugzilla – Bug 1228842
ceph-deploy rgw create should echo the port number (e.g., 7480)
Last modified: 2017-12-12 19:29:37 EST
Description of problem: The ceph-deploy rgw create utility does an excellent job of getting a Ceph Object Gateway. However, it starts the gateway on default port 7480, which most people wouldn't guess. Version-Release number of selected component (if applicable): How reproducible: Every time. Steps to Reproduce: 1. ceph-deploy install --rgw <node-name> 2. ceph-deploy rgw create <node-name> Actual results: It works, but http://<node-name> says connection refused. Expected results: Anonymous request payload. Most users will be expecting something on port 80, or port 8080. Port 7480 probably isn't anyone's nth guess, so informing them what port it's using would help. So an acceptable result is: "Ceph Object Gateway is running under port N" where N is the port number. Additional info: It would be ultra slick to provide an instruction given the name of the node. E.g., "To change the port, add [client.rgw.<node-name>] rgw_frontends = "civetweb port=n" To your Ceph configuration file, where 'n' is the port number. Then, restart the Ceph Object Gateway. sudo systemctl restart ceph-radosgw.service
*** Bug 1228846 has been marked as a duplicate of this bug. ***
Change merged upstream with: https://github.com/ceph/ceph-deploy/commit/2878c9183fa01bf2fe27580852a165300e3ea061
For Ubuntu, this bug is fixed in ceph-deploy-1.5.27.1.
ceph-deploy rgw create command succeeds with the following message: [ceph_deploy.rgw][INFO ] The Ceph Object Gateway (RGW) is now running on host magnaxxx and default port 7480
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:2512
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:2066