Comment 11 for bug 1956229

Reviewed: https://review.opendev.org/c/starlingx/openstack-armada-app/+/822357
Committed: https://opendev.org/starlingx/openstack-armada-app/commit/4e3157bf4c3271d2d01d72b1ea6bc5407dbc296a
Submitter: "Zuul (22348)"
Branch: master

commit 4e3157bf4c3271d2d01d72b1ea6bc5407dbc296a
Author: Lucas Cavalcante <email address hidden>
Date: Mon Dec 20 17:19:09 2021 -0300

    Fix nova-compute-ssh

    On stx-openstack, we run the nova-compute containers as user 0 (root) to
    get privileged access to some of the host resources. During the latest
    upversion of openstack-helm, we got in some commits that were
    incompatible with our usage of the root user since the keys for ssh
    access to a different compute were always placed under the 'nova' user's
    folder. This commit fixes that behavior while we don't merge a
    definitive fix on openstack-helm and go through a new upversion.

    Test Plan:

    PASS - nova-compute-ssh starting correctly after change
    the sshd->ssh parameter
    PASS - migrate/resize vm

    Closes-Bug: #1956229

    Signed-off-by: Lucas Cavalcante <email address hidden>
    Signed-off-by: Hugo Brito <email address hidden>
    Change-Id: Ic90e8e64670b8314b9a2f38b93a59361dcb7ecc9