Comment 2 for bug 1948140

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

Reviewed: https://review.opendev.org/c/starlingx/ansible-playbooks/+/818136
Committed: https://opendev.org/starlingx/ansible-playbooks/commit/3d2eb4e267461614f9c0ae897e058689812d9208
Submitter: "Zuul (22348)"
Branch: master

commit 3d2eb4e267461614f9c0ae897e058689812d9208
Author: Rafael Camargos <email address hidden>
Date: Tue Nov 16 17:13:07 2021 -0300

    Apply apiserver parameters on restore and upgrade

    The issue is manifested by backing-up and restoring a system with
    kube-apiserver parameters applied, e.g.: oidc-auth params. The
    parameters are restored and can be displayed by running
    `service-parameter-list` but aren't getting reapplied back.

    The fix consists in running the `puppet-manifest-apply.sh` script during
    the 'restore-more-data' step of the restore, which is executed both
    during platform restore and upgrade. When applying the manifest the
    kube-apiserver service parameters are updated, similarly to running
    `service-parameter-apply`.

    Test Plan: In an AIO-SX, apply oidc-auth kube-apiserver parameters,
    perform a B&R and an upgrade operation and verify these are properly
    restored.

    PASS: Verify kube-apiserver service parameters are restored after a
    System Backup and Restore
    PASS: Verify kube-apiserver service parameters are restored after a
    System Upgrade

    Closes-Bug: 1948140
    Signed-off-by: Rafael Camargos <email address hidden>
    Change-Id: I9d4823deb0b928acd86c8372fe5306ac8a841518