StarlingX

  1. Bug #1887648
  2. Comment #12

Comment 12 for bug 1887648

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/753311
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=99616a7f72125c6fd5c86e5dd90af3d87ef3902c
Submitter: Zuul
Branch: master

commit 99616a7f72125c6fd5c86e5dd90af3d87ef3902c
Author: Dan Voiculeasa <email address hidden>
Date: Mon Sep 21 13:49:18 2020 +0300

    Introduce CLI commands for system restore control

    Introduce 3 new sysinv commands: restore-show, restore-start,
    restore-complete.

    When doing a restore, the system will be put automatically into a
    restore state by the restore playbook. After all the nodes are up
    and unlocked the user must do a `system restore-complete` to get
    out of the system restore state.

    Note: In the case of multi-nodes setups helm overrides may have been
    detected so apps will be auto-applied after exiting the restore
    state. The auto apply is started by a periodic audit thread.

    Depends-On: I44fc4aaa528e372a84115714f271b4f5e063f86e
    Partial-Bug: 1887648
    Change-Id: I7b7fab99d457056032dbbd612363cd5036736cda
    Signed-off-by: Dan Voiculeasa <email address hidden>