Bug 1016956
Summary: | Some error messages are given out when executing "oo-diagnostics" on broker | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ma xiaoqiang <xiama> |
Component: | Node | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.0.0 | CC: | bleanhar, libra-onpremise-devel, lmeyer, mmasters, xtian |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-openshift-origin-common-1.17.2.4-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-04 16:57: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: | |
Embargoed: |
Description
Ma xiaoqiang
2013-10-09 03:33:04 UTC
test_broker_certificate should be improved now and not result in this error. check on rubygem-openshift-origin-common-1.17.2.4-1.el6op.noarch # oo-diagnostics <--snip--> WARN: test_broker_certificate Using a self-signed certificate for the broker WARN: test_yum_configuration oo-admin-yum-validator reported some possible problems with your package source configuration: -------------------------------------------------------------- No roles have been specified. Attempting to guess the roles for this system... If the roles listed below are incorrect or incomplete, please re-run this script with the appropriate --role arguments broker client Detected OpenShift Enterprise repository subscription managed by Red Hat Subscription Manager. Detected installed OpenShift Enterprise version 2.0 Checking if yum-plugin-priorities is installed Checking channel/repository priorities Resolving repository/channel/subscription priority conflicts To resolve conflicting repositories, update repo priority by running: # yum-config-manager --setopt=openshift_node.priority=40 openshift_node --save # yum-config-manager --setopt=openshift_infrastructure.priority=40 openshift_infrastructure --save Please re-run this tool after making any recommended repairs to this system -------------------------------------------------------------- Incorrect package source configuration could lead to failure to install the correct RPMs. Luke, did you mean to change the product version for this bug report from 1.2.0 to 2.0.0? I'm confused because it looks like you opened bug 1040647 to address the same bug in 2.0. I changed it because the report was against a 2.0 puddle. I don't recall seeing this under 1.2, not sure what we changed about the config for 2.0 to start running into this. The bug 1040647 *is* a duplicate, I just didn't notice I guess. Is there a need to look at this for 1.2 as well? The fix should be easy... Actually, I'm going to make a bug for 1.2 because I think it does happen there too. |