I was going crazy about the same issue. The reason why yum couldn't find python-pip was that it is not called python-pip anymore. Starting with EPEL Version 7 it is renamed to identify the python version. On my centOS machine i can find now the following python*-pip packages.

[root@asdasdasdasdsa ~]# yum info python*-pip
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: ftp.rz.uni-frankfurt.de
 * epel: mirrors.mit.edu
 * extras: mirror.23media.de
 * updates: ftp.plusline.de
Available Packages
Name        : python2-pip
Arch        : noarch
Version     : 8.1.2
Release     : 5.el7
Size        : 1.7 M
Repo        : epel/x86_64
Summary     : A tool for installing and managing Python 2 packages
URL         : http://www.pip-installer.org
License     : MIT
Description : Pip is a replacement for `easy_install
            : <http://peak.telecommunity.com/DevCenter/EasyInstall>`_.  It uses mostly the
            : same techniques for finding packages, so packages that were made
            : easy_installable should be pip-installable as well.

Name        : python34-pip
Arch        : noarch
Version     : 8.1.2
Release     : 5.el7
Size        : 1.7 M
Repo        : epel/x86_64
Summary     : A tool for installing and managing Python3 packages
URL         : http://www.pip-installer.org
License     : MIT
Description : Pip is a replacement for `easy_install
            : <http://peak.telecommunity.com/DevCenter/EasyInstall>`_.  It uses mostly the
            : same techniques for finding packages, so packages that were made
            : easy_installable should be pip-installable as well.

You can always review a Yum mirror via your web browser to determine if it is a Yum problem, or if the package is missing from the mirror. In this case, it looks like the package is missing. Nothing is wrong with Yum. Your other systems may have cached repository data, or might be connecting to a different mirror with an outdated package list.

The next step would be to check the mailing lists and BugZilla to see if there has been any discussion.

I am actually not sure which mailing list would be correct here;

• epel-devel
• epel-announce
• epel-package-announce

I was able to find a conversation on BugZilla that might be related: pip install is broken (path/permissions) Maybe the package was pulled due to this. It doesn't seem like a serious issue..

If you cannot wait for this to be resolved, you might be able to find an older, unaffected version in Koji, the build system. (Check what version is installed and working on other systems.)

Lastly, it seems the SRPM is still available. You could grab it and rebuild it yourself to see if it will meet your needs. Though, if it was pulled, maybe there is good reason.