Red Hat Bugzilla – Bug 1478508
Not able to retire VM/instance via API unless "Set Retirement Date" feature is checked for role
Last modified: 2017-10-23 20:17:32 EDT
New commit detected on ManageIQ/manageiq/fine:
Author: Alberto Bellotti <email@example.com>
AuthorDate: Wed Jul 5 16:35:41 2017 -0400
Commit: Satoe Imaishi <firstname.lastname@example.org>
CommitDate: Fri Aug 4 13:34:35 2017 -0400
Merge pull request #15509 from jntullo/bz/wrong_retirement_product_feature
Use correct identifier for VM Retirement
(cherry picked from commit 30f51d5eec8695e68ad0205a477e636d2c86892a)
config/api.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Verified on 18.104.22.168 that it's possible to retire a VM using the REST API when "Set Retirement Date" is unchecked.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.