diff options
| author | Ghanshyam Mann <gmann@ghanshyammann.com> | 2020-04-27 13:46:07 -0500 |
|---|---|---|
| committer | Ghanshyam Mann <gmann@ghanshyammann.com> | 2020-05-01 15:32:51 +0000 |
| commit | d4af91f349b9d3fe4f840878906032a62b589324 (patch) | |
| tree | 1ba3857116e2d09806d109311ef6a316aa2c2d58 /doc/source/install | |
| parent | 347d656c35fdf0c309039a7c1f352f82c6950868 (diff) | |
| download | nova-d4af91f349b9d3fe4f840878906032a62b589324.tar.gz | |
Add nova-status upgrade check and reno for policy new defaults
There are cases where policy file is re-generated freshly
and end up having the new defaults only but expectation is that
old deprecated rule keep working.
If a rule is present in policy file then, that has priority over
its defaults so either rules should not be present in policy file
or users need to update their token to match the overridden rule
permission.
This issue was always present when any policy defaults were changed
with old defaults being supported as deprecated. This is we have
changed all the policy for new defaults so it came up as broken case.
Adding nova-status upgrade check also to detect such policy file.
Related-Bug: #1875418
Change-Id: Id9cd65877e53577bff22e408ca07bbeec4407f6e
Diffstat (limited to 'doc/source/install')
| -rw-r--r-- | doc/source/install/verify.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/source/install/verify.rst b/doc/source/install/verify.rst index 7aaf0b5f86..9742595879 100644 --- a/doc/source/install/verify.rst +++ b/doc/source/install/verify.rst @@ -123,3 +123,7 @@ Verify operation of the Compute service. | Result: Success | | Details: None | +--------------------------------------------------------------------+ + | Check: Policy Scope-based Defaults | + | Result: Success | + | Details: None | + +--------------------------------------------------------------------+ |