Bug 1659072
Summary: | osp8 overcloud deployment fails with : epmd reports: node 'rabbit' not running at all | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | pkomarov | |
Component: | resource-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> | |
Status: | CLOSED WONTFIX | QA Contact: | michal novacek <mnovacek> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 7.6 | CC: | agk, aherr, amarecek, apevec, bperkins, cfeist, cluster-maint, fdinitto, jeckersb, lhh, lmiccini, michele, mnovacek, oblaut | |
Target Milestone: | rc | Keywords: | Triaged, ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | resource-agents-4.1.1-16.el7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1692889 (view as bug list) | Environment: | ||
Last Closed: | 2021-03-15 07:32:30 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1647587, 1692889 |
Description
pkomarov
2018-12-13 14:07:51 UTC
This is because the rabbitmq-server version in OSP8 has different output format for eval calls than in newer OSP versions. On 8: [root@localhost ~]# rabbitmqctl eval 'testing.' testing ...done. [root@localhost ~]# On 9 through 14: [root@localhost ~]# rabbitmqctl eval 'testing.' testing [root@localhost ~]# On the 8 version, the "...done." output can be suppressed by passing the -q flag: [root@localhost ~]# rpm -q rabbitmq-server rabbitmq-server-3.3.5-34.el7ost.noarch [root@localhost ~]# rhos-release -L Installed repositories (rhel-7.6): 8 ceph-1.3 ceph-osd-1.3 rhel-7.6 [root@localhost ~]# rabbitmqctl eval -q 'testing.' testing [root@localhost ~]# So we must update the resource agent to always use -q for eval. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |