Bug 1299958 - instack-virt-setup does not set explicit path, can't find binaries
instack-virt-setup does not set explicit path, can't find binaries
Product: RDO
Classification: Community
Component: instack-undercloud (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: Kilo
Assigned To: James Slagle
Shai Revivo
Depends On:
  Show dependency treegraph
Reported: 2016-01-19 10:39 EST by Lars Kellogg-Stedman
Modified: 2016-05-19 12:01 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-05-19 12:01:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lars Kellogg-Stedman 2016-01-19 10:39:56 EST
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):


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 12:01:57 EDT
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.