Fix ambiguity around releases and workarounds
Note speaks of two workarounds, but only one is listed (unless upgrade is considered workaround). Also rocky is not released yet, so cannot be a recommended action operators can take in thd moment of time. This patch is just to fine tune the above, the rest looks good though. Change-Id: I931c5737d6e0a6ed5ae912693bad6b49438c80e1
This commit is contained in:
parent
064314998c
commit
57aeac354b
@ -17,14 +17,15 @@ set to thick so most installations are likely not affected. Operators
|
||||
can check their configuration in `cinder.conf` or check for zero padding
|
||||
with this command `scli --query_all`.
|
||||
|
||||
### Recommended Actions ###
|
||||
Update Cinder to Rocky or later.
|
||||
#### Recommended Actions ####
|
||||
|
||||
Alternatively operators can use one of two workarounds:
|
||||
Operators can use the following two workarounds, until the release of
|
||||
Rocky (planned 30th August 2018) which resolves the issue.
|
||||
|
||||
Swap to thin volumes
|
||||
1. Swap to thin volumes
|
||||
|
||||
2. Ensure ScaleIO storage pools use zero-padding with:
|
||||
|
||||
Ensure ScaleIO storage pools use zero-padding with:
|
||||
`scli --modify_zero_padding_policy
|
||||
(((--protection_domain_id <ID> |
|
||||
--protection_domain_name <NAME>)
|
||||
|
Loading…
Reference in New Issue
Block a user