Bug 1397010 - [RFE] Make interactive mode default when running openstack overcloud update stack
Summary: [RFE] Make interactive mode default when running openstack overcloud update s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 14.0 (Rocky)
Assignee: Julie Pichon
QA Contact: Arik Chernetsky
URL:
Whiteboard: NeedsAllocation
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 12:07 UTC by David Juran
Modified: 2018-01-26 11:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-26 11:01:16 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description David Juran 2016-11-21 12:07:06 UTC
Description of problem:
When applying updates to an OverCloud, by running "openstack overcloud update stack", as described in https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/upgrading-red-hat-openstack-platform/#sect-Updating_the_Overcloud one _must_ use the "-i" flag, otherwise the update will hang with no easy way of resuming. To avoid the risk of manual mistakes, I therefore suggest we make the interactive mode the default for this operation.


Additional info:
Is there nay situation where one would like to run the opnestack overcloud update stack without the -i flag?

Comment 1 Julie Pichon 2018-01-26 11:01:16 UTC
Minor updates were completely overhauled in OSP12 [1] [2], and it appears interactive mode is no longer an option.

$ openstack help overcloud update stack
usage: openstack overcloud update stack [-h] [--stack [STACK]]
                                        [--templates [TEMPLATES]]
                                        [--init-minor-update]
                                        [--container-registry-file CONTAINER_REGISTRY_FILE]
                                        [--ceph-ansible-playbook CEPH_ANSIBLE_PLAYBOOK]
                                        [--nodes NODES] [--playbook PLAYBOOK]
                                        [--static-inventory STATIC_INVENTORY]

Based on this I'm going to close the bug, as we usually don't change defaults for already released versions.

[1] https://bugs.launchpad.net/tripleo/+bug/1715557
[2] https://review.openstack.org/#/c/512991/


Note You need to log in before you can comment on or make changes to this bug.