Merge "[codespell] Fix spelling issues in IPA"
This commit is contained in:
29 changed files with 63 additions and 63 deletions
@@ -147,7 +147,7 @@ to be used.
.. NOTE::
The Ironic Developers chose to limit the items available for service steps
such that the risk of data distruction is generally minimized.
such that the risk of data destruction is generally minimized.
That being said, it could be reasonable to reconfigure RAID devices through
local hardware managers *or* to write the base OS image as part of a
service operation. As such, caution should be taken, and if additional data
@@ -160,7 +160,7 @@ Cleaning safeguards
-------------------
The stock hardware manager contains a number of safeguards to prevent
unsafe conditions from occuring.
unsafe conditions from occurring.
Devices Skip List
~~~~~~~~~~~~~~~~~
@@ -245,7 +245,7 @@ We also support determining the checksum by length.
The field can be utilized to designate:
* A URL to retreive a checksum from.
* A URL to retrieve a checksum from.
* MD5 (Disabled by default, see ``[DEFAULT]md5_enabled`` in the agent
configuration file.)
* SHA-2 based SHA256
@@ -189,7 +189,8 @@ Cleaning halted with ProtectedDeviceError
The IPA service has halted cleaning as one of the block devices within or
attached to the bare metal node contains a class of filesystem which **MAY**
cause irreparable harm to a potentially running cluster if accidently removed.
cause irreparable harm to a potentially running cluster if accidentally
removed.
These filesystems *may* be used for only local storage and as a result be
safe to erase. However if a shared block device is in use, such as a device
@@ -39,7 +39,7 @@ Upon success, it returns following data in response::
If successful, this synchronous command will:
1. Write the salted and crypted ``rescue_password`` to
1. Write the salted and encrypted ``rescue_password`` to
``/etc/ipa-rescue-config/ipa-rescue-password`` in the chroot or filesystem
that ironic-python-agent is running in.
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.