Skip to content

Add debugging info to tls deployment docs #683

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 5, 2023
Merged

Add debugging info to tls deployment docs #683

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions doc/source/configuration/vault.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,6 +229,18 @@ Enable the required TLS variables in kayobe and kolla
kayobe overcloud service deploy
If VM provisioning fails with an error with this format:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did this happen after completion of the service deploy? It seems odd that it's using an HTTP endpoint.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you delete the admin endpoints before running service deploy? Should that be a separate step rather than a warning?

Did this happen after completion of the service deploy? It seems odd that it's using an HTTP endpoint.

I did delete the admin endpoints before the service deploy, and provisioning did not work after the service deploy. I thought it was very strange that it didn't pick up the changes and needed a manual restart.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had the nova_compute containers been restarted during the service deploy?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure, the docker logs don't really go back far enough


.. code-block::
Unable to establish connection to http://<kolla internal vip/fqdn>:9696/v2.0/ports/some-sort-of-uuid: Connection aborted
Restart the nova-compute container on all hypervisors:

.. code-block::
kayobe overcloud host command run --command "docker restart nova_compute" --become --show-output -l compute
Barbican integration
====================

Expand Down