9f300cd9f8
In cases where we do a backup of a system that has non-default
sizes for drbd-backed partitions, the restore fails when first
unlocking controller-0.
The normal resize procedure requires all controller nodes to
be unlocked and available because the puppet manifest does
not support resizing at unlock.
To prevent the issue from occuring, as part of the restore
procedure, we should resize the partitions on controller-0
with the proper sizes found in sysinv. Controller-1 will
automatically create the partitions with the proper sizes
from the very start, so it will not need any resizes.
Change-Id: Ia73452ce721514d393b486a659730d0ca7c0d7e5
Closes-bug: 1854169
Depends-on: https://review.opendev.org/#/c/699990
Signed-off-by: Stefan Dinescu <stefan.dinescu@windriver.com>
(cherry picked from master commit 5cdd394cb1)
stx-ansible-playbooks
StarlingX Bootstrap and Deployment Playbooks
Execution environment
- Unix like OS (recent Linux based distributions, MacOS, Cygwin)
- Python 2.7
Additional Required Packages
The playbooks in this repo have been verified with the following versions of Ansible and StarlingX playbooks dependencies:
- sshpass 1.06
- python2-ptyprocess 0.5
- python2-pexpect 4.6
- python2-netaddr 0.7
ansible2.7.5
Supported StarlingX Releases
The playbooks in this repo are compatible with the following StarlingX releases:
- 19.12
Executing StarlingX Playbooks
Executing Bootstrap Playbook
Please refer to StarlingX Deployment Guides, section
Configuration controller-0 of the respective system
configuration for instructions on how to set up and execute the
bootstrap playbook from another host.