diff options
| author | Michelle (Shelly) Mutu-Grigg <shellymutugrigg@gmail.com> | 2020-10-09 14:42:45 +1300 |
|---|---|---|
| committer | Michelle (Shelly) Mutu-Grigg <shellymutugrigg@gmail.com> | 2020-10-15 23:03:55 +1300 |
| commit | d5ca2ac7f0e2323400b22bc7b8cc2c33a3f1ef5a (patch) | |
| tree | 1a539060e51978c9e96fd35f15251493aae774ab /doc/source/admin/troubleshooting.rst | |
| parent | cde792a8c3b36afd9dd916b38bf60ed6af4f441a (diff) | |
| download | ironic-d5ca2ac7f0e2323400b22bc7b8cc2c33a3f1ef5a.tar.gz | |
Update .rst files
This commit removes `--os-baremetal-api-version` from CLI examples,
updates some `openstack baremetal` commands to be `baremetal` and
removes -uuid from <node-uuid>
Story: 2008194
Task: 40964
Change-Id: I4421e98afdee9ed97506cb7e5d69da966cffd963
Diffstat (limited to 'doc/source/admin/troubleshooting.rst')
| -rw-r--r-- | doc/source/admin/troubleshooting.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/source/admin/troubleshooting.rst b/doc/source/admin/troubleshooting.rst index 505e4d871..e774bbc3e 100644 --- a/doc/source/admin/troubleshooting.rst +++ b/doc/source/admin/troubleshooting.rst @@ -66,7 +66,7 @@ A few things should be checked in this case: #. Starting with the Pike release, check that all your nodes have the ``resource_class`` field set using the following command:: - openstack --os-baremetal-api-version 1.21 baremetal node list --fields uuid name resource_class + baremetal node list --fields uuid name resource_class Then check that the flavor(s) are configured to request these resource classes via their properties:: @@ -282,7 +282,7 @@ all the logs according to the ``deploy_logs_storage_backend`` configuration option. All log objects will be named with the following pattern:: - <node-uuid>[_<instance-uuid>]_<timestamp yyyy-mm-dd-hh:mm:ss>.tar.gz + <node>[_<instance-uuid>]_<timestamp yyyy-mm-dd-hh:mm:ss>.tar.gz .. note:: The *instance_uuid* field is not required for deploying a node when @@ -652,7 +652,7 @@ provisioning, rescuing, or even inspection, getting the node to the ``available`` state wil unblock your delete operation, that is unless there is a tenant VIF attahment. In that case, the vif will need to be removed from with-in the Bare Metal service using the -``openstack baremetal node vif detach`` command. +``baremetal node vif detach`` command. A port can also be checked to see if there is a VIF attachment by consulting the port's ``internal_info`` field. |