trove-integration changes $HOME and there are problems if any devstack plugin wants $HOME

Bug #1552048 reported by Amrith Kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Confirmed
Medium
Unassigned

Bug Description

In redstack, there's a function set_home_dir()

function set_home_dir() {
    self="${0#./}"
    base="${self%/*}"
    current=`pwd`
    if [ "$base" = "$self" ] ; then
        HOME="$current/"
    elif [[ $base =~ ^/ ]]; then
        HOME="$base/"
    else
        HOME="$current/$base/"
    fi
}

Now, if some devstack plugin wants to look at $HOME, much hilarity ensues

I have no idea why we set $HOME but it seems like a bad thing to be doing ...

Amrith Kumar (amrith)
Changed in trove:
milestone: none → mitaka-rc1
importance: Undecided → Medium
status: New → Confirmed
Amrith Kumar (amrith)
Changed in trove:
milestone: mitaka-rc1 → mitaka-rc2
Amrith Kumar (amrith)
Changed in trove:
milestone: mitaka-rc2 → newton-1
Amrith Kumar (amrith)
Changed in trove:
milestone: newton-1 → ongoing
Amrith Kumar (amrith)
Changed in trove:
assignee: Amrith Kumar (amrith) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.