Bug 1137028 - Install Docs contain a link to EPEL that does not cover how to install EPEL7
Summary: Install Docs contain a link to EPEL that does not cover how to install EPEL7
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: documentation
Version: Master
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: 2.6.0
Assignee: Dennis Kliban
QA Contact: Irina Gulina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-03 21:32 UTC by Brian Bouterse
Modified: 2015-02-28 22:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-28 22:17:57 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 509 0 None None None Never

Description Brian Bouterse 2014-09-03 21:32:05 UTC
The install docs point at a page that easily has install instructions for the EPEL repo rpms, but only for EL6 and EL7. We should link to this page instead:

http://fedoraproject.org/wiki/EPEL/FAQ#howtouse

This should instead read something like "Go install EPEL: <link to https://fedoraproject.org/wiki/EPEL>"

Comment 1 Mike McCune 2014-09-03 21:41:06 UTC
As an admin/user I find it useful and convenient to be able to quickly copy-paste commands from the installation docs. Perhaps have different sections for the different RHEL versions pointing to EPEL for 6 and 7:

RHEL6: 

# rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

RHEL7:

# rpm -Uvh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-1.noarch.rpm 

Pointing at the upstream docs is easier but if you are trying to digest all the steps necessary to get Pulp running it can be easier if you can see all the necessary commands on one page.

Comment 3 Preethi Thomas 2015-01-26 20:09:26 UTC
This needs to be fixed again.

The link for rhel7 epel repo does not work.

What is in the doc is

https://pulp-user-guide.readthedocs.org/en/latest/installation.html#repositories


$ sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-2.noarch.rpm




[root@cloud-qe-4 ~]#  sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-2.noarch.rpm
Retrieving https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-2.noarch.rpm
curl: (22) The requested URL returned error: 404 Not Found
error: skipping https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-2.noarch.rpm - transfer failed
[root@cloud-qe-4 ~]#  sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
Retrieving https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
warning: /var/tmp/rpm-tmp.ddo0PU: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
Preparing...                          ################################# [100%]
Updating / installing...
   1:epel-release-7-5                 ################################# [100%]
[root@cloud-qe-4 ~]#

Comment 4 Dennis Kliban 2015-02-09 21:36:50 UTC
https://github.com/pulp/pulp/pull/1621

Comment 5 Chris Duryee 2015-02-10 22:32:57 UTC
2.6.0-0.7.beta

Comment 6 Irina Gulina 2015-02-17 17:11:38 UTC
The link on EPEL7 was fixed 

https://github.com/pulp/pulp/blob/master/docs/user-guide/installation.rst



    For RHEL and CentOS systems, the EPEL repositories are required. Following commands will add the appropriate repositories for RHEL6 and RHEL7 respectively:

    RHEL6:

    $ sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

    RHEL7:

    $ sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm

Note

The above EPEL URLs change with each release of the epel-release package. If you receive a 404 error when attempting to install the above RPM, point your browser at the directory it is in and look for the updated name of epel-release package.

Comment 7 Brian Bouterse 2015-02-28 22:17:57 UTC
Moved to https://pulp.plan.io/issues/509


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