Description of problem: Unable to retire the service via global region. Version-Release number of selected component (if applicable): 5.7.2.1 How reproducible: Always Steps to Reproduce: 1.Under the Global webui 2. Service provision via Service Catalog 3. Check newly provisioned Service via Service > My Service 4. Retire the Service: Service > My Service > select service > Lifecycle > Retire service Actual results: "The selected Service is not in the current region" error message Expected results: It should retire the service. Additional info: we are able to do service provisioning via global region but not service retirement.
Created attachment 1286418 [details] screenshot from case
Dear customer, The CloudForms team is reviewing the current CloudForms RFE(Request for Enhancement) backlog in order to improve our responsiveness to customers. We are closing any requests for versions no longer within full support(link below to the lifecycle) or that do not have a clear spot on the product roadmap. We are committing to better management of the backlog as we move forward. If you have an RFE that you still have a strong business case for, please open a new BZ against the currently supported version 4.6. Lifecycle page: https://access.redhat.com/support/policy/updates/cloudforms If you have any concerns about this, please let us know. Thanks and regards!”
Dear Josh, let me apologize but I do not agree with proposed aproach aiming to close this BZ as not useful. Although it is possible to order service at master region, there is missing functionality for "reverse action" > to let initiate service retirement from master region. I think this feature is must / requirement for CloudForms to allow full service life-cycle operations from master region. Kind regards, Vaclav