Bug 981387 - openstack-packstack: remote cinder deployment doesn't work cinder service is not started at the end of installation [NEEDINFO]
openstack-packstack: remote cinder deployment doesn't work cinder service is ...
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack (Show other bugs)
x86_64 Linux
high Severity high
: rc
: 4.0
Assigned To: Martin Magr
: Triaged, Unconfirmed
Depends On:
  Show dependency treegraph
Reported: 2013-07-04 11:17 EDT by Haim
Modified: 2016-04-27 01:34 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-12-07 08:25:10 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
pmyers: needinfo? (hateya)

Attachments (Terms of Use)
installation log (3.86 KB, text/x-log)
2013-07-04 11:22 EDT, Haim
no flags Details

  None (edit)
Description Haim 2013-07-04 11:17:50 EDT
Description of problem:

remote cinder installation doesn't work as cinder services are not started during installation.

had to start the services manually. 

attached all logs + answer file. 


machine A - all regular services
machine B - cinder

start installation
Comment 1 Haim 2013-07-04 11:22:24 EDT
Created attachment 768855 [details]
installation log
Comment 2 Perry Myers 2013-12-05 13:51:19 EST
@haim, can you reproduce this with the RHOS 4.0 latest builds and provide packstack logs?
Comment 3 Martin Magr 2013-12-07 08:25:10 EST
Could not reproduce with current master branch. After installation cinder services on separate host are up and running:

[para@virtual-rhel ~]$ openstack-status 
== Cinder services ==
openstack-cinder-api:                   active
openstack-cinder-scheduler:             active
openstack-cinder-volume:                active
== Support services ==
messagebus:                             active
tgtd:                                   active
[para@virtual-rhel ~]$

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