RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1299958 - instack-virt-setup does not set explicit path, can't find binaries
Summary: instack-virt-setup does not set explicit path, can't find binaries
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: instack-undercloud
Version: Liberty
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 15:39 UTC by Lars Kellogg-Stedman
Modified: 2016-05-19 16:01 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 16:01:57 UTC
Embargoed:


Attachments (Terms of Use)

Description Lars Kellogg-Stedman 2016-01-19 15:39:56 UTC
Description of problem:

The instack-virt-setup script does not explicitly set `PATH`, and uses unqualified binary names.  This means that if it is run in an environment in which PATH does not include /usr/sbin, it will get stuck on this loop:

    instack never got an IP address from the libvirt default network.
    /usr/bin/instack-virt-setup: line 175: ip: command not found

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

    instack-undercloud-2.1.3-1.el7.noarch

The fix is to either (a) explicitly set PATH or (b) refer to binaries using explicit paths (e.g., /usr/sbin/ip).

A workaround if one encounters this condition is:

    ln -s /usr/sbin/ip /usr/bin/ip

This will allow the script to complete.

Comment 2 Chandan Kumar 2016-05-19 16:01:57 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


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