Bug 1316105 - /setup/agent/ points to "localhost" as the master in the minion config
/setup/agent/ points to "localhost" as the master in the minion config
Product: Red Hat Storage Console
Classification: Red Hat
Component: ceph-installer (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 2
Assigned To: Alfredo Deza
Depends On:
  Show dependency treegraph
Reported: 2016-03-09 07:30 EST by Alfredo Deza
Modified: 2016-08-23 15:48 EDT (History)
11 users (show)

See Also:
Fixed In Version: ceph-installer-1.0.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-08-23 15:48:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alfredo Deza 2016-03-09 07:30:23 EST
Description of problem: When trying to bootstrap the agent with the /setup/agent/ endpoint, it creates a /etc/salt/minion.d/ceph_agent.conf  file pointing to "localhost" as the master, which is wrong.

Version-Release number of selected component (if applicable):

How reproducible: 100%

Steps to Reproduce:
1. curl http://<ceph-installer-host>:8181/setup/agent/ | sudo bash
2. wait for the installation process to complete

Actual results:

Expected results: /etc/salt/minion.d/ceph_agent.conf  should have the address/hostname of the host for the ceph-installer, not "localhost"

Additional info:
Comment 2 Alfredo Deza 2016-03-09 15:07:25 EST
Pull Request opened https://github.com/ceph/ceph-installer/pull/115
Comment 5 Mike McCune 2016-03-28 18:11:59 EDT
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
Comment 13 Martin Kudlej 2016-06-21 05:43:31 EDT
Checked with ceph-installer-1.0.11-1.el7scon.noarch and it works. -> Verified
Comment 15 errata-xmlrpc 2016-08-23 15:48:07 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.