RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1336547 - openstack-icehouse repo rpm missing
Summary: openstack-icehouse repo rpm missing
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RDO
Classification: Community
Component: distribution
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: Kilo
Assignee: Lars Kellogg-Stedman
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-16 19:42 UTC by ddanielr
Modified: 2016-05-23 16:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-23 16:31:26 UTC
Embargoed:


Attachments (Terms of Use)
RPM with updated URL for the repository (12.00 KB, application/x-rpm)
2016-05-19 22:02 UTC, ddanielr
no flags Details

Description ddanielr 2016-05-16 19:42:44 UTC
Description of problem:
The rpm for the openstack-icehouse repo has been removed from hosting. 

It was previously located at: 

https://repos.fedorapeople.org/repos/openstack/EOL/openstack-icehouse/rdo-release-icehouse-4.noarch.rpm 

Was this an intentional change?
If so, are there plans to replace the rpm with open that points to the new openstack-icehouse URL for Centos 6:
https://repos.fedorapeople.org/openstack/EOL/openstack-icehouse/epel-6/ 

How reproducible:


Steps to Reproduce:
1. wget https://repos.fedorapeople.org/repos/openstack/EOL/openstack-icehouse/rdo-release-icehouse-4.noarch.rpm 
File does not exist, and was not moved somewhere else in the directory tree's children. It was simply removed.

Comment 1 ddanielr 2016-05-17 15:04:28 UTC
Given that there are now two new subdirectories (epel-6 and epel-7) that seem to contain most/all of the other files, it would seem like somebody is trying to add epel-7 support and perhaps is not quite done, or missed a step.

We would appreciate some way of getting in touch with whoever is implementing these changes so we can understand how best to preserve our ability to reprovision our new virtual machines (frozen at icehouse).

Comment 2 Alfredo Moralejo 2016-05-18 14:16:31 UTC
When a version reaches EOL repositories are moved to the EOL directory to indicate their status. Since the repository files installed by the rdo-release packages points to the old location, not only they are useless but they would give end-users the false idea that they still can deploy those versions by just installing those packages.

Use of EOL repositories is not recomended but if fully required, you could write
your own yum repository files pointing to the new location.

Comment 3 ddanielr 2016-05-19 22:02:55 UTC
Created attachment 1159724 [details]
RPM with updated URL for the repository

This is a rebuilt version of the rdo-release-icehouse-4.noarch.rpm file.

The URL path for the rdo-release.repo file has been updated to the new /EOL/ URL Path.

Comment 4 ddanielr 2016-05-19 22:06:15 UTC
We have rebuilt the old rpm (rdo-release-icehouse-4.noarch.rpm) with the new EOL URL path (rdo-release-icehouse-4-EOL.noarch.rpm). Can you please update the EOL repo and place this RPM at the following location: https://repos.fedorapeople.org/repos/openstack/EOL/openstack-icehouse/rdo-release-icehouse-4-EOL.noarch.rpm 

We understand that use of these packages is not recommended, however they are far from useless as there is still a need to access and install these packages for VMs that are being hosted on openstack-icehouse.

Comment 5 Alfredo Moralejo 2016-05-23 16:31:26 UTC
The use of EOL repositories can be reasonable in few exceptional cases. For those exceptions user can create their own .repo file or even create a rpm release repo and manage it in a user-managed yum repository. It has been decided in RDO project to not create release RPMs pointing to EOL locations for versions once they reach their end of life.

Comment 6 Alan Pevec 2016-05-23 16:37:40 UTC
EOL folder README has been updated to make it clear that its usage is not encouraged: https://repos.fedorapeople.org/repos/openstack/EOL/00README.txt
Providing release rpm would go against that message.


Note You need to log in before you can comment on or make changes to this bug.