Bug 1332345 - Calamari instalation message mentions Inktank Ceph Enterprise
Summary: Calamari instalation message mentions Inktank Ceph Enterprise
Keywords:
Status: CLOSED DUPLICATE of bug 1268590
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Calamari
Version: 1.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 2.0
Assignee: Christina Meno
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 00:42 UTC by Warren
Modified: 2022-02-21 18:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-03 18:01:55 UTC
Embargoed:


Attachments (Terms of Use)

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 ***


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