Bug 1281307 - openstack-status command does not exist on compute node
Summary: openstack-status command does not exist on compute node
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Martin Magr
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-12 09:40 UTC by Eran Kuris
Modified: 2016-04-18 06:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-03 08:52:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
answer file (10.29 KB, text/plain)
2015-11-12 09:40 UTC, Eran Kuris
no flags Details

Description Eran Kuris 2015-11-12 09:40:39 UTC
Created attachment 1093095 [details]
answer file

Description of problem:
Install OSP-8 with packstack 2 nodes environment, IN compute node the command openstack-status  does not exist. When I checked I found that openstack-utils-2014.2-1.el7ost.noarch package didn't installed on compute node.
the output in compute node : 
rpm -qf `which openstack-status`
/usr/bin/which: no openstack-status in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)

output in controller:
 rpm -qf `which openstack-status`
openstack-utils-2014.2-1.el7ost.noarch

Version-Release number of selected component (if applicable):
openstack-utils-2014.2-1.el7ost.noarch
# rpm -qa |grep packstack
openstack-packstack-puppet-7.0.0-0.7.dev1661.gaf13b7e.el7ost.noarch
openstack-packstack-7.0.0-0.7.dev1661.gaf13b7e.el7ost.noarch


Steps to Reproduce:
1.install 2 nodes OSP env with packstack
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ivan Chavero 2015-12-03 08:52:00 UTC
the package openstack-utils is not a dependency of openstack-nova that's why you don't have it on the compute node.


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