8a18249fda
During an upgrade abort scenario where both controllers are already upgraded to release N+1, a potential issue arises. Release N+1 utilizes a new hieradata file named hostname-X.yaml, while release N uses the older ip.yaml. Controller-0 must be downgraded first, making controller-1 the active node. However, controller-1 attempts to update the hieradata file at /opt/platform/puppet/<Release N>/.../controller-0.yaml This file doesn't exist because release N uses ip.yaml Solution: The system needs to identify this downgrade scenario and update the correct hieradata file for release N: /opt/platform/puppet/<Release N>/hieradata/<ip>.yaml Tests Done: AIO-DX IPv6 fresh install AIO-DX IPv6 upgrade abort Story: 2010722 Task: 49692 Change-Id: I848543e7606ddc5bb24ddadb07a7a74d56126044 Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com> |
||
|---|---|---|
| .. | ||
| cert-alarm | ||
| cert-mon | ||
| cgts-client | ||
| ipsec-auth | ||
| sysinv | ||
| sysinv-agent | ||