attempting the tripleo container image prepare workflow without logging out after install results in an error

[Alex Schultz]

If you install an undercloud and start an overcloud deployment without logging out, you may hit an error when you run 'openstack tripleo container image prepare -e ~/containers-prepare-parameter.yaml --roles-file /usr/share/openstack-tripleo-heat-templates/roles_data.yaml --output-env-file ~/containers-default-parameters.yaml'

The error may just be:
Error while fetching server API version: ('Connection aborted.', error(13, 'Permission denied'))

This is because the user that installed the undercloud (typically 'stack') does not have the docker group added until you logout and log back in again.

http://paste.openstack.org/show/730382/

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/603914

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/603914
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=75c2c3c4447134842cefb56f29285e493c2f5966
Submitter: Zuul
Branch: master

commit 75c2c3c4447134842cefb56f29285e493c2f5966
Author: Steve Baker <email address hidden>
Date: Thu Sep 20 08:47:53 2018 +1200

    Make every reference to the prepare command use sudo

    Even though the installing user is added to the docker group, this
    only takes effect after they restart their shell session. So if they
    install the undercloud and run prepare in the same session, the
    prepare call will fail at the docker operations.

    Rather than explain this caveat, document calling prepare with sudo.
    This is already done on line #266, but this change ensures every
    reference to the command includes sudo.

    Change-Id: Ia14b0964dcaefbbf7265b3960315114219fd3c7b
    Closes-Bug: #1793375