Hide Forgot
Steps on Probe: Collect data from os-collect-config tool Collect the undercloud.conf file Validate undercloud.conf data (endpoints, ip-ranges etc) Collect partner overcloud images (probe undercloud glance) Inspect partner overcloud image for partner plugin config etc Collect/Inspect partner puppet integration with OSPD Check OSPD rpm packages (sosreport) Steps on Validation backend: Validate data from os-collect-config Validate undercloud.conf and related probe checks Validate overcloud image for partner plugin conf Validate puppet module for partner plugin OSPD integration (if any) Based on above probe and validation steps, we can confirm if partner has deployed using RHELOSP-D, please provide inputs if above steps are insufficient. https://projects.engineering.redhat.com/browse/RHELOSPCER-205
Based on internal discussions, only below steps were required to successfully verify director installation. Steps on Probe: Collect data from os-collect-config tool Collect the undercloud.conf file Steps on Validation backend: Validate data from os-collect-config Validate undercloud.conf and related probe checks
As per the above comments mentioned by Rohan , I have verified below mentioned steps in latest RCO build . redhat-certification-openstack-1.3.3-1.el7 Steps Tested: Collect data from os-collect-config tool Collect the undercloud.conf file Steps on Validation backend: Validate data from os-collect-config Validate undercloud.conf and related probe checks Test cases mentioned in : https://tcms.engineering.redhat.com/plan/19933/redhat-certification-openstack#reviewcases
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://rhn.redhat.com/errata/RHBA-2016-0538.html