Bug 1218555
Summary: | rdo-release needs to enable RHEL optional extras and rh-common repositories | ||
---|---|---|---|
Product: | [Community] RDO | Reporter: | Ami Jeain <ajeain> |
Component: | distribution | Assignee: | Alan Pevec <apevec> |
Status: | CLOSED EOL | QA Contact: | Shai Revivo <srevivo> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | Kilo | CC: | aortega, apevec, derekh, gchamoul, jpena, markmc, srevivo |
Target Milestone: | GA | ||
Target Release: | Kilo | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-19 15:32:28 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
Ami Jeain
2015-05-05 09:14:21 UTC
Packstack detects if it is installing RDO by checking if a package called rdo-release-* is installed. For the testing day, the package was called rdo-testing-kilo, so it was not detected. I doubt if we should consider this as NOTABUG (it will only happen in these cases), or we should find a better way to detect RDO. Any ideas? With RDO >= Kilo EPEL will not be required, we'll carry CloudSIG EPEL rebuilds in RDO repo. Also in this case, EPEL will not help, this is an issue with segmented RHEL repos, python-cheetah is in rh-common. I'll try to handle RHEL specific repos in rdo-release|testing repos, so that Packstack doesn't need to have any special handling. Exact names of RHEL repos which need to be enabled are: rhel-7-server-optional-rpms rhel-7-server-extras-rpms rhel-7-server-rh-common-rpms subscription-manager repos --enable rhel-7-server-optional-rpms --enable rhel-7-server-extras-rpms --enable rhel-7-server-rh-common-rpms This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen. |