Bug 1528663 - After Openstack 10 triggers an "unknown" state on instances, when it recovers Cloudforms duplicates vms instead of recovering them
Summary: After Openstack 10 triggers an "unknown" state on instances, when it recovers...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: All
OS: All
urgent
urgent
Target Milestone: GA
: 5.10.0
Assignee: Sam Lucidi
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks: 1541042 1541072
TreeView+ depends on / blocked
 
Reported: 2017-12-22 17:18 UTC by Felix Dewaleyne
Modified: 2021-06-10 14:02 UTC (History)
23 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1541042 1541072 (view as bug list)
Environment:
Last Closed: 2019-02-11 14:05:05 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Felix Dewaleyne 2017-12-22 17:18:28 UTC
Description of problem:
After Openstack 10 triggers an "unknown" state on instances, when it recoveres Cloudforms duplicates vms instead of recovering them

Version-Release number of selected component (if applicable):
openstack 10 (virtualised controllers)
Cloudforms 4.5.2

How reproducible:
every day at customer site

Steps to Reproduce:
1. get openstack to change instances to an unknwon state then back to normal
2. 
3.

Actual results:
the instances affected get archived and then get re-discovered

Expected results:
cloudforms recovers and does either un-archive the instances or never archives them in the first place

Additional info:
this happens daily at the customer's.

Comment 17 Adam Grare 2018-01-02 13:53:05 UTC
Hey Marek, it looks like some servers were returned multiple times.

Can you make a change to the openstack refresh_parser to unique the vms returned?
Adding this to the vcr tests would be great, also to confirm that graph refresh isn't affected since this should already be handled internally by graph refresh.

Comment 49 Jad Haj Yahya 2018-12-03 09:52:43 UTC
Hi Marek,

I need a clarification regarding step 2 above:

2. somehow filter some of VMs from Nova APIU output

Thanks,
Jad

Comment 50 Sam Lucidi 2018-12-04 21:41:34 UTC
Hi Jad,

I think all you should have to do to test whether the duplication has been solved is to add the provider, let it collect inventory, and then remove the provider so that the instances remain but are disconnected. Then readd the provider with all the same details and refresh to see whether the disconnected instances are reenabled or duplicated.

Sam

Comment 51 Jad Haj Yahya 2018-12-05 14:53:32 UTC
Verified on 5.10.0.27


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