Bug 1332345

Summary: Calamari instalation message mentions Inktank Ceph Enterprise
Product: Red Hat Ceph Storage Reporter: Warren <wusui>
Component: CalamariAssignee: Christina Meno <gmeno>
Calamari sub component: Web UI QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: ceph-eng-bugs, vereddy
Version: 1.3.2   
Target Milestone: rc   
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-03 18:01:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Warren 2016-05-03 00:42:20 UTC 
Description of problem:

When installing calamari, after doing:
ceph-deploy calamari connect --master http://magna071.ceph.redhat.com/ magna034
the following text appeared:

New Calamari Installation

This appears to be the first time you have started Calamari and there are no clusters currently configured.

1 Ceph servers are connected to Calamari, but no Ceph cluster has been created yet. Please use ceph-deploy to create a cluster; please see the Inktank Ceph Enterprise documentation for more details.


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


How reproducible:
1 for 1

Steps to Reproduce:
1. Install calamari using CDN
2. do calamari-ctl initialize
3. try attaching a ceph cluster using the command above.  In this case the admin
   node was magna071, calamari-server was magna071, and the ceph cluster node was
   magna034.

Note that the problem is not necessarily that there is a error here (it is a probable user error).  The problem is the Inktank reference in the text of the message. 

Actual results:
See above

Expected results:
No references to Inktank should be made

Additional info:
Comment 2 Christina Meno 2016-05-03 18:01:55 UTC 

*** This bug has been marked as a duplicate of bug 1268590 ***