This will allow us to do most of the implementation of the
undercloud upgrade in instack-undercloud rather than in difficult-
to-update client code (it would be tricky at best to have the client
update itself).
bp undercloud-upgrade
Change-Id: Icb3fe2c1285f8f8574aad583d08c557936ffabe5
Depends-On: I8c614395e4e77f43b117c687cae3441b39f6c40b
This broke undercloud upgrades - tripleoclient imports
instack_undercloud.undercloud, then upgrades the package.
This means the upgrade call then runs against the old version
of the module, which is incompatible with some of the new
puppet stuff.
Closes-Bug: 1701362
This reverts commit b6e71724e091a8a23191114e3638e1760240dfd2.
Change-Id: Ie79dfff667437305ff4109da5a9c42ae358b1a3e
For about 2 years we've been indirectly calling the undercloud
install function through a bash script. Originally this was done
to allow for some backwards compatibility with mismatched packages,
but later it was kept because a direct call broke logging. This
is no longer a problem, probably due to some changes in how logging
in instack-undercloud works.
Change-Id: If07880e4bc25cffe485704772d64f62288a1a53d
Depends-On: Iff76f639bcacb5bcc1274fd837e47d34041afa15
Related bp undercloud-upgrade
In order to better handle upgrades, we need to be able to know when
we are performing an upgrade instead of an installation. This change
switches the undercloud upgrade process to use the
instack-upgrade-undercloud script which will expose the fact that we are
running an upgrade process to the underlying puppet scripts.
Change-Id: I493204117ca158e99f706770a02fbb7f6392673b
Depends-On: Ie3cb21e30334fe8ffc0a9d6e707b42269b64c9ec
Related-Bug: #1649341
Related-Blueprint: undercloud-upgrade
This new library provides the common logic used by openstack
clients. Replacing the imports from openstackclient and cliff.
Depends-On-External: https://review.rdoproject.org/r/#/c/2088/
Depends-On: I095209c241876c6ab48595962e07144fc5cc34a6
Closes-Bug: #1620964
Change-Id: I103a13ff6c0af94b82f5e48652380adfbf331d34
During upgrades testing and as discussed in bug 1558495 the
initial overcloud upgrade step (major-upgrade-pacemaker-init.yaml)
times out. The fix for now is to restart openstack-nova-api after
the undercloud upgrade.
Change-Id: Ifd9c2f4bdbca701d655c741ab21da2a571c1dcb5
Closes-Bug: 1558495
The undercloud upgrade process entails updating the installed packages,
then running the installer again. However, after updating packages, a
number of services may no longer be able to run, as upon restart the
new code is not compatible with older settings. Therefore, this makes
the upgrade more 'atomic' by bundling the package update and the
undercloud install into a single command. An error (non-zero RC) in the
package update will halt the process.
Change-Id: I269ba919f1648f0e4b30ab710c386dafdad2a68d
Running openstack command with python-tripleoclient under
root user is not supported and should not be allowed. Added
check for user and exit if it is root (EUID=0) to openstack
undercloud install command.
Each command can be disabled for root by adding
utils.ensure_run_as_normal_user() into it's body.
Change-Id: I685c639e02790483d1607c7eac038f8b9b8dc99e
Closes-Bug: rhbz#1239088
