Trove Integration

use HOST_USERNAME as default of HOST_SCP_USERNAME

Bug #1485409 reported by Masaki Matsushita
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trove Integration
In Progress
Undecided
Masaki Matsushita

Bug Description

In many case, HOST_USERNAME and HOST_SCP_USERNAME may be same value.
I think it's useful that scripts use HOST_USERNAME as default value of HOST_SCP_USERNAME.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove-integration (master)

Fix proposed to branch: master
Review: https://review.openstack.org/213580

Changed in trove-integration:
assignee: nobody → Masaki Matsushita (mmasaki)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on trove-integration (master)

Change abandoned by Masaki Matsushita (<email address hidden>) on branch: master
Review: https://review.openstack.org/213580
Reason: I abandon the change because it is needed to define HOST_SCP_USERNAME in several elements and I think the change won't be reasonable.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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