Description of problem: The MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup, MiqAeServiceContainerImage, MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerNode and MiqAeServiceContainerService service models each have several broken associations, as follows: 1) MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup association 'metric_rollups' throws a NameError exception when accessed MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup association 'node_selector_parts' throws a NameError exception when accessed MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerGroup association 'vim_performance_states' throws a NameError exception when accessed 2) MiqAeServiceContainerImage association 'computer_system' throws a NameError exception when accessed MiqAeServiceContainerImage association 'openscap_result' throws a NameError exception when accessed MiqAeServiceContainerImage association 'openscap_rule_results' throws a NameError exception when accessed 3) MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerNode association 'computer_system' throws a NameError exception when accessed MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerNode association 'metric_rollups' throws a NameError exception when accessed MiqAeServiceManageIQ_Providers_Kubernetes_ContainerManager_ContainerNode association 'metrics' throws a NameError exception when accessed 4) MiqAeServiceContainerService association 'container_service_port_configs' throws a NameError exception when accessed MiqAeServiceContainerService association 'metric_rollups' throws a NameError exception when accessed MiqAeServiceContainerService association 'selector_parts' throws a NameError exception when accessed Version-Release number of selected component (if applicable): 5.8.2.3. How reproducible: Every time Steps to Reproduce: On an appliance with an OpenShift provider: 1. Access any of the 4 service models in the Rails console 2. list the associations of the model (<model>.associations) 3. try to access one of the associations listed as broken or On an appliance with an OpenShift provider: 1. Install object_walker from https://github.com/pemcg/object_walker (git-installable domain) 2. On the CFME appliance as root, install object_walker_reader using the command: rpm -ivh https://github.com/pemcg/object_walker/raw/master/object_walker_reader-1.8-1.noarch.rpm 3. Create and run the following automate method: $evm.root['container_service'] = $evm.vmdb(:ContainerService).first $evm.root['container_node'] = $evm.vmdb(:ContainerNode).first $evm.root['container_image'] = $evm.vmdb(:ContainerImage).first $evm.root['container_group'] = $evm.vmdb(:ContainerGroup).first $evm.instantiate('/Discovery/ObjectWalker/object_walker') 4. On the CFME appliance as root, run /root/object_walker_reader.rb | grep '!!!' Actual results: Broken associations are listed Expected results: There should be no broken associations Additional info:
Federico - Can you have some review this list of errors in the automate service model side. We typically do not expose every association from the service models, for example we do not expose any metric data. Unless there is a strong use case maybe some of these should be removed.
I used to be able to partly reproduce it on fine but not anymore, Can you please check if it is still happening on Fine? Maybe it was fixed before I understood how exactly to do it. On Master / Gaprindashvilli I haven't been able to see it and from Greg Mccullough I understood that is should be there.
I reproduced it on CFME 5.8.2.3 which is the current release.
PR: https://github.com/ManageIQ/manageiq/pull/16615
This issue is not relevant for master or G release, only for Fine. Loic, Do you want it to be fixed for 5.8.z ?
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-2018:0374