New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=0b8f8d758237a37a9d29998dc48da5086410c1ea commit 0b8f8d758237a37a9d29998dc48da5086410c1ea Merge: e0f444e ef77751 Author: Greg McCullough <gmccullo> AuthorDate: Wed Feb 10 14:27:40 2016 -0500 Commit: Greg McCullough <gmccullo> CommitDate: Wed Feb 10 14:27:40 2016 -0500 Merge branch 'cherry_pick_retirement_tag_fix' into '5.5.z' Automate - Retirement - Remove miq_provision and tag code from the cloud/infra remove_from_provider methods. https://bugzilla.redhat.com/show_bug.cgi?id=1301149 Original: https://bugzilla.redhat.com/show_bug.cgi?id=1300559 https://github.com/ManageIQ/manageiq/pull/6290 Clean cherry-pick. See merge request !745 .../Methods.class/__methods__/remove_from_provider.rb | 10 +++------- .../Methods.class/__methods__/remove_from_provider.rb | 10 +++------- .../unit/method_validation/remove_from_provider_spec.rb | 1 - 3 files changed, 6 insertions(+), 15 deletions(-)
Tina, please help to reproduce this bug. I imported enclosed production automation_code.zip. Should I edit /ManageIQ/Infrastructure/VM/Retirement/StateMachines/Methods/RemoveFromProvider class?
Hi Dmitry, To reproduce the issue: 1. Add a provider that you have provisioned a VM on from a different server. 2. Select "Refresh Relationships and Power States". 3. Select "Retire Now" on the VM that can be deleted. 4. When retirement has completed. you'll notice the VM still exists(on the provider and VMDB) and is marked as 'retired'. To validate the fix: Repeat steps 1-3 above. You'll notice the VM has been deleted from the provider and the VMDB. Let me know if you have any problems or questions. If you're having issues, provide me the IP, credentials, and VM and I'll take a look. Regards, Tina
Thanks Tina. Tested and verified in 5.5.3.2.20160318152106_92d2d67.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:0616