Bug 1474811

Summary:	A MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup object derives from the wrong class
Product:	Red Hat CloudForms Management Engine	Reporter:	Peter McGowan <pmcgowan>
Component:	Automate	Assignee:	Greg McCullough <gmccullo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.8.0	CC:	cpelland, jhardy, mkanoor, obarenbo, simaishi, tfitzger, tpapaioa
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.8.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.8.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-24 16:51:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core	Target Upstream Version:
Embargoed:

Description Peter McGowan 2017-07-25 12:31:27 UTC

Description of problem:
A MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup object derives from MiqAeServiceProvider, whereas I suspect it should derive from MiqAeServiceContainerGroup (in the same way that the model ManageIQ::Providers::Kubernetes::ContainerManager::ContainerGroup derives from ::ContainerGroup)

This means that the associations of MiqAeServiceContainerGroup are not visible to a MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup object.

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

How reproducible:
Every time

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Greg McCullough 2017-07-25 13:12:43 UTC

This issue was reported as a comment in https://bugzilla.redhat.com/show_bug.cgi?id=1455563#c5 and fixed in PR https://github.com/ManageIQ/manageiq/pull/15235 on the Fine (CFME 5.8) branch.

I am moving the ticket to POST so it can be tested since the related BZ above does not clearly identify this issue as part of the title or description.

Also note that this is not an issue upstream (currently 5.9) where empty service models are auto-generated.

Comment 3 Tasos Papaioannou 2017-07-27 20:21:08 UTC

Verified on 5.8.1.5.

irb> MiqAeMethodService::MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup.superclass
=> MiqAeMethodService::MiqAeServiceContainerGroup

irb> MiqAeMethodService::MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup.all[0]
=> #<MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup:0x6324b54 @object=#<ManageIQ::Providers::Kubernetes::ContainerManager::ContainerGroup id: 7, ems_ref: "d9a426f0-4468-11e7-ac9d-001a4a3dca1f", name: "heapster-7iiqw", ems_created_on: "2017-05-29 12:17:57", resource_version: "5406397", <snip>>

irb> MiqAeMethodService::MiqAeServiceContainerGroup.all[0]
=> #<MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup:0x6317f58 @object=#<ManageIQ::Providers::Kubernetes::ContainerManager::ContainerGroup id: 7, ems_ref: "d9a426f0-4468-11e7-ac9d-001a4a3dca1f", name: "heapster-7iiqw", ems_created_on: "2017-05-29 12:17:57", resource_version: "5406397", <snip>>