Summary: | rhosp-director: Error: Evaluation Error: Illegal relationship operand, can not form a relationship with an Undef Value. A Catalog type is required. at /etc/puppet/modules/pacem aker/manifests/remote.pp:31:6 on node overcloud-networker-0.localdomain | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> |
Component: | puppet-pacemaker | Assignee: | Michele Baldessari <michele> |
Status: | CLOSED ERRATA | QA Contact: | pkomarov |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 12.0 (Pike) | CC: | aherr, dbecker, dprince, jjoyce, jschluet, mburns, michele, morazi, rhel-osp-director-maint, slinaber, tvignaud, ushkalim |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | puppet-pacemaker-0.6.1-0.20171015172907.44d3226.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-13 22:11:04 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: |
Description
Alexander Chuzhoy
2017-09-20 19:51:22 UTC
Ok so there are a couple of things here: 1) OS::TripleO::Services::PacemakerRemote probably does not make any sense in the Networker role anyway as I cannot see any services managed by pacemaker. *But* that is not the real problem here. 2) The real problem is that https://review.openstack.org/#/c/503077/ introduced ensure_resource() with a relationship and that will barf out like this: Error: Evaluation Error: Illegal relationship operand, can not form a relationship with an Undef Value. A Catalog type is required. at /etc/puppet/modules/pacemaker/manifests/remote.pp:31:6 on node nuc2.int.rhx Am not entirely sure as to why it was introduced because remote.pp and pacemaker::corosync are not meant to be included in the same node anyway? I'll take this one and work on a fix but I'd love to hear as to why we moved to ensure_resource() ? Change has merged upstream and there are no branches for this module Successfully deployed OC with composable roles after applying the attached patch to OC image. Martin explained to me why the assumption that remote and corosync were on the same node. It was mainly wrong thinking on a CI patch. So removing needinfo here. Verified. HA composable roles deployments are passing. https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/pidone/view/features/job/DFG-pidone-features-12_director-rhel-virthost-3cont_3data_3mess_1comp_1ceph-ipv4-vxlan-composable_roles/ 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/RHEA-2017:3462 |