Bug 1478889

Summary:	[genealogy] CFME not detecting parent VM with Azure provider
Product:	Red Hat CloudForms Management Engine	Reporter:	Antonin Pagac <apagac>
Component:	Providers	Assignee:	Daniel Berger <dberger>
Status:	CLOSED ERRATA	QA Contact:	Antonin Pagac <apagac>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.8.0	CC:	apagac, bsorota, cpelland, dberger, gblomqui, jfrey, jhardy, obarenbo, simaishi, smallamp
Target Milestone:	GA
Target Release:	5.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.10.0.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-07 23:02:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Antonin Pagac 2017-08-07 12:51:43 UTC

Description of problem:
When editing an instance on Azure provider, in the Parent VM Selection there is always "no parent". I looked at multiple instances running on Azure, all of them have no parent. When deploying a testing instance the parent is also not detected.

I'm not sure if we can detect a parent VM on Azure provider.

Version-Release number of selected component (if applicable):
5.8.1.5

How reproducible:
Always

Steps to Reproduce:
1. Add an Azure provider to CFME
2. Deploy an instance
3. Select the instance, then Configuration -> Edit this Instance
4. Look at the Parent VM Selection
5. "no parent" is displayed

Actual results:
"no parent" detected on instances on Azure provider

Expected results:
A parent template/VM should be displayed. This would be the template from which we deployed this instance.

Additional info:
This is working fine for providers different than Azure

Comment 2 Bronagh Sorota 2017-08-08 20:03:27 UTC

Hi Dan,
Can you take a look at this, check if we track parents (image) of cloud provider instances. I checked an AWS VM and it didnt have the parent set, but maybe we need to provision from CloudForms, not sure.

Bronagh

Comment 3 Bronagh Sorota 2017-08-10 14:13:24 UTC

Hi Antonin,
Do I need to deploy a VM from CF to see this set in other providers? No parent was set for an AWS VM created from the AWS portal.
What is this setting used for? What is the impact of this?

thanks
Bronagh

Comment 5 Antonin Pagac 2017-08-11 08:54:42 UTC

Hi Bronagh,

QA is testing genealogy by creating a new VM via CF. For AWS EC2, this way the parent can be detected in CF without problems.

I looked at the instances currently deployed on AWS, went through them manually and every instance does have a parent in CF. I cannot tell however if these instances were deployed via CF or using AWS portal.

On usage/impact I will have to ask around.

Comment 6 Daniel Berger 2018-04-13 19:07:56 UTC

This seems to work on master. I provisioned from a Windows image, and when I go to edit the instance, it definitely shows the parent image.

I will check 5.8 and 5.9 and see if/when it was added and if it can be backported.

Comment 7 Daniel Berger 2018-04-13 20:10:45 UTC

It looks like current support on master was a positive side-effect of adding graph refresh. I'll see if it's possible to set this in classic refresh and then backport it.

Comment 8 Daniel Berger 2018-07-17 12:49:44 UTC

https://github.com/ManageIQ/manageiq-providers-azure/pull/267

Comment 9 Antonin Pagac 2018-08-09 09:40:46 UTC

Verified with 5.10.0.8.

Deployed an Instance, choose to edit it and the parent template is displayed there.

Comment 10 errata-xmlrpc 2019-02-07 23:02:39 UTC

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/RHSA-2019:0212