Description of problem:
As container retirement is not (yet?) supported, the retirement button is still displayed in the UI (as well as in the Self Service UI), which ends with a fatal error method not implemented.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
run the container retirement or remove the life cycle buttons
Lucy - Check with Bill, we fixed a similar issue with Ansible objects and should apply the same logic here.
We need to keep the LifeCycle buttons as the user may also want to support retirement through custom automation. And we still want to support retiring the service (or service bundle) that may include this type of object.
New commit detected on ManageIQ/manageiq/master:
Author: Lucy Fu <email@example.com>
AuthorDate: Fri Apr 13 10:49:46 2018 -0400
Commit: Lucy Fu <firstname.lastname@example.org>
CommitDate: Fri Apr 13 10:49:46 2018 -0400
Add method retire_now to container OrchestrationStack.
So the container service may be retired.
app/models/manageiq/providers/container_manager/orchestration_stack.rb | 5 +
spec/factories/orchestration_stack.rb | 2 +
spec/models/manageiq/providers/container_manager/orchestration_stack_spec.rb | 10 +
3 files changed, 17 insertions(+)
Verified in 188.8.131.52.20181030184024_26956a0.
Creation of the Catalog Item fails due to https://bugzilla.redhat.com/show_bug.cgi?id=1645676 but this does not block the Retirement of the item