Bug 1234117

Summary: openstack overcloud update stack assumes OVERCLOUD_PLAN_NAME exists
Product: Red Hat OpenStack Reporter: Ola Pavlenko <opavlenk>
Component: python-rdomanager-oscpluginAssignee: Jan Provaznik <jprovazn>
Status: CLOSED NOTABUG QA Contact: Ola Pavlenko <opavlenk>
Severity: high Docs Contact:
Priority: unspecified    
Version: DirectorCC: calfonso, dmatthew, jslagle, mburns, ohochman, rhel-osp-director-maint, rrosa
Target Milestone: ga   
Target Release: Director   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 13:45: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 Ola Pavlenko 2015-06-21 13:25:25 UTC
Description of problem:
trying to  run stack update using unified cli 'openstack overcloud stack update'  command.
In help of the command :
optional arguments:
   
  --plan PLAN        Name or ID of tuskar plan to scale (default=Env:
                     OVERCLOUD_PLAN_NAME)
which means that command assumes the env exists.

echoing the env returns nothing .
While trying to run the command without any args :
$ openstack overcloud update stack 
ERROR: openstack ERROR: 404 Not Found

The resource could not be found.


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

python-rdomanager-oscplugin-0.0.8-1.el7ost.noarch
rhos-release-0.62-1.noarch
How reproducible:
100%

Steps to Reproduce:
1.overcloud is deployed
2.update stack using 'openstack overcloud stack update' command
3.

Actual results:
ERROR

Expected results:
the stack was successfully updated

Additional info:

Comment 3 Dougal Matthews 2015-06-22 13:07:03 UTC
This sounds like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1232838

Comment 4 Dougal Matthews 2015-06-22 13:08:38 UTC
Ignore my previous comment, that was an error.

Comment 5 Jan Provaznik 2015-06-23 08:50:33 UTC
The behavior is following:
plan_name is used if "--plan plan_name" is passed as argument, if "--plan plan_name" is not passed then command will check if OVERCLOUD_PLAN_NAME env variable is set and if it is it will use plan_name set in this variable.

So setting OVERCLOUD_PLAN_NAME variable is optional if you don't want to use "--plan" argument.

This behavior was chosen after discussion with CLI/UI team so a change in this should be checkd with them - I suppose the rest of commands will use the same behavior.

Switching to ON_QA, if you think this behavior is confusing, feel free to switch back to ON_DEV and we can discuss this further.

Comment 7 Jan Provaznik 2015-07-22 13:45:57 UTC
Because this was not an actual bug, just misunderstanding about parameters, I'll close this as not a bug.