Red Hat Bugzilla – Bug 1306042
Cannot set Retirement date and retirement warning date for Catalog Item only in Catalog Bundle
Last modified: 2017-10-04 13:43:17 EDT
Description of problem:
Not able to set the retirement date and retirement warning date for a Catalog Item, but can for a Catalog Bundle. This should be consistent across both.
Version-Release number of selected component (if applicable):
The retirement section on catalogs items is for the VM provision template. A generic and orchestration catalog items would not show a retirement option since they are not derived from the provisioning dialogs.
This creates an issue on the Service side since the VM can be retired out from under the service.
I think the best option here is to hide the retirement selection on the VM provision dialog screen when displaying as part of a catalog item and add support for it from the service dialogs so it applies to the entire service.
John - Does this approach sound reasonable?
I've heard from the field that customers provision and/or move VMs into an existing service in which case they'd have their own retirement dates. It's not unusual to want to retire only one VM from a service since customers some times use services only as a means to provision VMs and remove the service after provisioning.
We have a PR that enables users to set a retirement date for Catalog Items/Bundles and wonder if its possible that we should leave the retirement selection on the VM provision dialog.
This bug has been open for more than a year and is assigned to an older release of CloudForms.
If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.