From 001824ae96f8ba44a453a65e4bfe4c97bc04dcff Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Andr=C3=A9?= Date: Wed, 2 Dec 2015 14:33:40 +0900 Subject: [PATCH] Fix broken links to ironic-inspector upstream docs Ironic-inspector documentation is now published on docs.openstack.org. Depends-On: Ic14cb73668544be27c6b96b384f93b239e49acfd Change-Id: Ic83534054a696474da2d89aebfef0d3cf1f8f7c6 --- doc/source/troubleshooting/troubleshooting-nodes.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/troubleshooting/troubleshooting-nodes.rst b/doc/source/troubleshooting/troubleshooting-nodes.rst index 3af41695..f15ba722 100644 --- a/doc/source/troubleshooting/troubleshooting-nodes.rst +++ b/doc/source/troubleshooting/troubleshooting-nodes.rst @@ -66,8 +66,8 @@ of bugs in our scripts), a node can be in the "AVAILABLE" state, which is meant for deployment, not for introspection. You should advance node to the "MANAGEABLE" state before introspection and move it back before deployment. Please refer to `upstream node states documentation -`_ for information -on how to fix it. +`_ +for information on how to fix it. How can introspection be stopped? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -89,4 +89,4 @@ then remove ironic-inspector cache and restart it:: sudo systemctl restart openstack-ironic-inspector -.. _ironic-inspector troubleshooting documentation: https://github.com/openstack/ironic-inspector#troubleshooting +.. _ironic-inspector troubleshooting documentation: http://docs.openstack.org/developer/ironic-inspector/troubleshooting.html