DescriptionFelix Dewaleyne
2019-06-19 16:10:08 UTC
Description of problem:
retiring two services at the same time leads to only the vms of the first service being retired - after completion of the retirement of the first service, the second service is retired without any automation running for it.
Version-Release number of selected component (if applicable):
5.10.5 and previous
How reproducible:
all the time
Steps to Reproduce:
1. create a catalog item or two that will be used to create vms against any provider (only infrastrucutre providers used to reproduce this)
2. create at least two services from the catalogs
3. go to services > my services
4. select 2 or more services
5. use lifecycle > retire services now
Actual results:
the retirement starts, runs as expeted for the first service, all services being retired are marked as being in the "retiring" state but only the vm attached to the first service is marked as "retiring". When the retirement completes, all services being retired are gone, but the vms of any service other than the first remain.
Expected results:
all services are retired and all automation runs
Additional info:
this is done using the default stock retirement automate.
doesn't happen when retiring multiple vms, only multiple services under services > my services.
if you display the details of the request created for the retirement, only the vm of the first service are listed under "affected vms"
I have not tested or seen the results of trying to remove more than 2 active services
Comment 3Niyaz Akhtar Ansari
2019-06-21 06:12:21 UTC
Hey Niyaz, could you check this again for me? I don't think it should be verified, I think it's broken in the same way that the 5'10 version of this ticket is.