Bug 1299958

Summary: instack-virt-setup does not set explicit path, can't find binaries
Product: [Community] RDO Reporter: Lars Kellogg-Stedman <lars>
Component: instack-undercloudAssignee: James Slagle <jslagle>
Status: CLOSED EOL QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: Liberty   
Target Milestone: ---   
Target Release: Kilo   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 16:01:57 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 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.