Bug 1326131

Summary:	calamari-ctl initialize requiring salt-minion to work
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Christina Meno <gmeno>
Component:	Calamari	Assignee:	Christina Meno <gmeno>
Calamari sub component:	Back-end	QA Contact:	Harish NV Rao <hnallurv>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	ceph-eng-bugs, hnallurv, kdreyer
Version:	2.0
Target Milestone:	rc
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	calamari-server-1.4.0-rc10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:35:48 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:
Embargoed:

Description Christina Meno 2016-04-11 22:29:12 UTC

Description of problem:
the spec file dropped package all requirements on salt, but initialize still uses the salt-call command which requires salt-minion and salt-common.

There are two fixes possible:
1. re depend on salt-minion and salt-common
2. re-write calamari-ctl to execute without salt

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


How reproducible:
100%

Steps to Reproduce:
1. install calamari without bootstrapping Storage Console
2. run calamari-ctl intialize
3. observe error

Actual results:
calamari-ctl errors

Expected results:
calamari-ctl does not error

Additional info:

Comment 2 Christina Meno 2016-04-27 15:39:24 UTC

*** Bug 1324494 has been marked as a duplicate of this bug. ***

Comment 4 Harish NV Rao 2016-06-09 11:57:09 UTC

The 'calamari-ctl initialize' is running successfully without any errors in recent builds. Moving this to verified.

[ubuntu@magna070 ~]$ sudo  calamari-ctl initialize 
[INFO] Loading configuration..
[INFO] Starting/enabling postgres...
[INFO] Updating database...
[ubuntu@magna070 ~]$

Comment 6 errata-xmlrpc 2016-08-23 19:35:48 UTC

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://rhn.redhat.com/errata/RHBA-2016-1755.html