These are issues reported by xjia in 871706 which got too muddy to follow. They are errors against https://openshift.redhat.com/community/wiki/deployment-guide-to-openshift-on-rhel-6 which is not yet part of the official docbooks, so no ECS action is indicated. 1.[High]Districts: https://openshift.redhat.com/community/wiki/deployment-guide-to-openshift-on-rhel-6#Districts (1)First, install rubygem-openshift-origin-msg-broker-mcollective, then modify "DISTRICTS_ENABLED=true" in the file /etc/openshift/plugins.d/openshift-origin-msg-broker-mcollective.conf. At last, restart openshift-broker service (2)In https://bugzilla.redhat.com/show_bug.cgi?id=849531#c5, these steps should be written in the doc 2.[High]Console:https://openshift.redhat.com/community/wiki/deployment-guide-to-openshift-on-rhel-6#Unsupported_Developer_Preview (1)The name of package is wrong. It should be "yum install openshift-console" (2)https://bugzilla.redhat.com/show_bug.cgi?id=871287#c3 and https://bugzilla.redhat.com/show_bug.cgi?id=871287#c4 , should add this document. 3.[Low]Lack the step how to configure the firewall or ldap server hostname in config file when use the ladp plugins. The item "AuthLDAPURL" should be paid attention in the file "/var/www/openshift/broker/httpd/conf.d/openshift-origin-auth-remote-user-ldap.conf.sample". Should specify how to configure the path and iptables. 4.[Low]Lack docs about how to make mcollective reconnect to activemq automatically after reboot like https://bugzilla.redhat.com/show_bug.cgi?id=869165#c4 . I think this should be written in Deployment, not BYO.
*** Bug 871706 has been marked as a duplicate of this bug. ***
1. is no longer relevant since DISTRICTS_ENABLED=true is the default. 2. has been fixed for some time. 3. I believe I have addressed this. Is there a specific change that needs to be made to selinux policy or iptables on the broker host in order to enable the outgoing connection? If so, please comment with details; I am not aware and it is not simple to test. 4. is baked into the configuration we provide.
Seems everything is ok. Verify it.
These are released AFAIK, apparently not in the errata release.