Bug 1551651
Summary: | Instance creation fails with "internal error: process exited while connecting to monitor" | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Joe H. Rahme <jhakimra> |
Component: | openstack-tripleo | Assignee: | James Slagle <jslagle> |
Status: | CLOSED DUPLICATE | QA Contact: | Arik Chernetsky <achernet> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 13.0 (Queens) | CC: | aschultz, kchamart, mburns, rhel-osp-director-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-03-09 14:25:15 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: |
Description
Joe H. Rahme
2018-03-05 15:57:57 UTC
At first sight, the error message reminds me of the duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=1543914. Second, chatting with Joe on IRC, he says it's not reproducible anymore with current builds, with the following versions: ----------------------------------------------------------------------------- [heat-admin@compute-0 ~]$ yum list installed | grep selinux ceph-selinux.x86_64 2:12.2.1-40.el7cp @rhelosp-ceph-3.0-mon container-selinux.noarch 2:2.48-1.el7 @rhelosp-rhel-7.5-extras libselinux.x86_64 2.5-12.el7 @anaconda/7.5 libselinux-python.x86_64 2.5-12.el7 @anaconda/7.5 libselinux-ruby.x86_64 2.5-12.el7 @rhos-13.0-rhel-7-signed libselinux-utils.x86_64 2.5-12.el7 @anaconda/7.5 openstack-selinux.noarch 0.8.14-0.20180221131810.4e6703e.el7ost selinux-policy.noarch 3.13.1-192.el7 @anaconda/7.5 selinux-policy-targeted.noarch 3.13.1-192.el7 @anaconda/7.5 ----------------------------------------------------------------------------- *** This bug has been marked as a duplicate of bug 1543914 *** |