Bug 1104853 - need to set default cdn repo to rhelosp 5
Summary: need to set default cdn repo to rhelosp 5
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: Installer
Assignee: Marek Hulan
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-04 19:54 UTC by Mike Burns
Modified: 2014-08-21 18:04 UTC (History)
6 users (show)

Fixed In Version: foreman-installer-staypuft-0.0.15-1.el6ost.noarch.rpm
Doc Type: Bug Fix
Doc Text:
internal only, no doc text needed
Clone Of:
Environment:
Last Closed: 2014-08-21 18:04:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1090 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2014-08-22 15:28:08 UTC

Description Mike Burns 2014-06-04 19:54:16 UTC 
Description of problem:
When installing staypuft, the configuration provides:

rhel-6-server-openstack-4.0-rpms

as the default repos to enable.  It should provide:  rhel-7-server-openstack-5.0-rpms

Version-Release number of selected component (if applicable):
0.0.14-1

How reproducible:
always

Steps to Reproduce:
1.run staypuft-installer
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Marek Hulan 2014-06-05 07:11:14 UTC 
Fixed in 0.0.15
Comment 13 Ido Ovadia 2014-08-07 16:08:25 UTC 
Verified
========
foreman-installer-1.5.0-0.6.RC2.el6ost.noarch
Comment 15 errata-xmlrpc 2014-08-21 18:04:16 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1090.html
Note You need to log in before you can comment on or make changes to this bug.