Bug 1384290 - Misisng information on retirement behavior when provisioned out-of-band
Summary: Misisng information on retirement behavior when provisioned out-of-band
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Red Hat CloudForms Documentation
QA Contact: Red Hat CloudForms Documentation
URL:
Whiteboard: doc
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-13 02:43 UTC by Tsai Li Ming
Modified: 2018-10-08 23:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-08 23:39:09 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Tsai Li Ming 2016-10-13 02:43:19 UTC
https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/provisioning-virtual-machines-and-hosts/provisioning-virtual-machines-and-hosts#retiring_virtual_machines_and_instances

6.1.1. Retiring Virtual Machines and Instances

Describe the issue: 
https://github.com/ManageIQ/manageiq/pull/9233

1. I don't think this behavior is documented at all.
2. And the tagging required to do proper retirement

"ManageIQ domain retirement state machine default behavior was changed in PR #6290 to remove the restriction that the VM has to either be: 1. created by us, 2. tagged with lifecycle/retire_full. This PR reverts the prior change and puts those restrictions back in place."


Suggestions for improvement: 
Such changes should be documented and communicated.

Please coordinate with engineering management to ensure such things are documented properly next time.

Comment 2 Andrew Dahms 2018-10-08 23:39:09 UTC
Thank you for raising this bug.

We have evaluated this request, and while we recognize that it is a valid request for the documentation, we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. 

If you have any concerns about this, please feel free to contact Andrew Dahms.


Note You need to log in before you can comment on or make changes to this bug.