Bug 1323139 - Direct call of non-controller upgrade script
Summary: Direct call of non-controller upgrade script
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 10.0 (Newton)
Assignee: Brad P. Crochet
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-01 11:14 UTC by Jaromir Coufal
Modified: 2016-10-04 18:21 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-04 18:18:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 300618 0 None None None 2016-04-01 20:54:48 UTC

Description Jaromir Coufal 2016-04-01 11:14:33 UTC 
Description of problem:
In order to do the non-controller upgrade, user has to call directly a script.

All other upgrade commands are hidden behind CLI, it would be significant improvement for customer perception to have single experience for upgrade procedure and not to call scripts directly. This is usability issue.


How reproducible:
any upgrade procedure of non-controller nodes (compute, swift, ceph)


Steps to Reproduce:
1. deploy OSP 7
2. try to upgrade to OSP 8


Actual results:
upgrade-non-controller.sh --upgrade <nova_id_node> 


Expected results:
openstack overcloud upgrade start --non-controller <nova_id_node>
Comment 1 Hugh Brock 2016-04-01 11:17:00 UTC 
Assigning this to Brad. This is pretty low-risk -- if we can get it in today, we should.
Comment 2 Jaromir Coufal 2016-04-04 10:53:52 UTC 
Dropping the upgrade CLI command from OSP8, fallback to "deploy" command, unblocking
Comment 3 Mike Burns 2016-04-07 21:36:02 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Note You need to log in before you can comment on or make changes to this bug.