Are images on Docker hub out of date in respect to OS packages?

If I created a derived image containing:
FROM openshift/python-27-centos7

USER 0

RUN yum install -y --setopt=tsflags=nodocs httpd httpd-devel && \
    yum clean all -y

USER 1001

The Docker build will fail with errors like:
Dependencies Resolved

================================================================================
 Package                Arch       Version                    Repository   Size
================================================================================
Installing:
 httpd                  x86_64     2.4.6-40.el7.centos        base        2.7 M
 httpd-devel            x86_64     2.4.6-40.el7.centos        base        187 k
Installing for dependencies:
 acl                    x86_64     2.2.51-12.el7              base         81 k
 apr                    x86_64     1.4.8-3.el7                base        103 k
 apr-devel              x86_64     1.4.8-3.el7                base        188 k
 apr-util               x86_64     1.5.2-6.el7                base         92 k
 apr-util-devel         x86_64     1.5.2-6.el7                base         76 k
 centos-logos           noarch     70.0.6-3.el7.centos        base         21 M
 cryptsetup-libs        x86_64     1.6.7-1.el7                base        182 k
 cyrus-sasl             x86_64     2.1.26-19.2.el7            base         88 k
 cyrus-sasl-devel       x86_64     2.1.26-19.2.el7            base        309 k
 dbus                   x86_64     1:1.6.12-13.el7            base        306 k
 device-mapper          x86_64     7:1.02.107-5.el7           base        251 k
 device-mapper-libs     x86_64     7:1.02.107-5.el7           base        304 k
 dracut                 x86_64     033-360.el7_2              updates     311 k
 expat-devel            x86_64     2.1.0-8.el7                base         56 k
 httpd-tools            x86_64     2.4.6-40.el7.centos        base         82 k
 initscripts            x86_64     9.49.30-1.el7              base        429 k
 kmod                   x86_64     20-5.el7                   base        114 k
 kmod-libs              x86_64     20-5.el7                   base         47 k
 kpartx                 x86_64     0.4.9-85.el7               base         59 k
 libdb-devel            x86_64     5.3.21-19.el7              base         38 k
 mailcap                noarch     2.1.41-2.el7               base         31 k
 openldap-devel         x86_64     2.4.40-8.el7               base        799 k
 qrencode-libs          x86_64     3.4.1-3.el7                base         50 k
 systemd                x86_64     219-19.el7                 base        5.1 M
 systemd-libs           x86_64     219-19.el7                 base        356 k
 sysvinit-tools         x86_64     2.88-14.dsf.el7            base         63 k
Updating for dependencies:
 cyrus-sasl-lib         x86_64     2.1.26-19.2.el7            base        155 k
 dbus-libs              x86_64     1:1.6.12-13.el7            base        151 k
 libdb                  x86_64     5.3.21-19.el7              base        718 k
 libdb-utils            x86_64     5.3.21-19.el7              base        102 k
 openldap               x86_64     2.4.40-8.el7               base        348 k

Transaction Summary
================================================================================
Install  2 Packages (+26 Dependent packages)
Upgrade             (  5 Dependent packages)

Total download size: 35 M
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
--------------------------------------------------------------------------------
Total                                              876 kB/s |  35 MB  00:41
Running transaction check
Running transaction test

Transaction check error:
  file /usr/lib64/libsystemd-daemon.so.0 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package systemd-container-libs-208.20-6.el7.centos.x86_64
  file /usr/lib64/libsystemd-id128.so.0 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package systemd-container-libs-208.20-6.el7.centos.x86_64
  file /usr/lib64/libsystemd-journal.so.0 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package systemd-container-libs-208.20-6.el7.centos.x86_64
  file /usr/lib64/libsystemd-login.so.0 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package systemd-container-libs-208.20-6.el7.centos.x86_64
.....

If I build the openshift/python-27-centos7 image myself on local Docker, (but not using Makefile and so not squashed, but otherwise the same), and change FROM to use freshly built image, then the installation of httpd and httpd-devel in a derived image works fine.

Confirmed that blows up if build is done on OpenShift instance itself. That is, the following fails:
$ oc new-build https://github.com/GrahamDumpleton/openshift-s2i-python-experiments.git --context-dir=py27-1 --name httpd-python-27-centos7

To fake it out and get it to work I can build openshift/python-27-centos7 locally on OpenShift using:
oc new-build https://github.com/GrahamDumpleton/openshift-s2i-python.git --context-dir=2.7 --name=xpython-27-centos7

This creates image stream for the S2I Python builder called xpython-27-centos7.
I can then edit the bc for httpd-python-27-centos7 and change to:
                "strategy": {
                    "type": "Docker",
                    "dockerStrategy": {
                        "from": {
                            "kind": "ImageStreamTag",
                            "name": "xpython-27-centos7:latest"
                        }
                    }
                },

That is, pick up the image stream for my local built version of python-27-centos7 and then my build for my derived image works fine.
Thus there is definitely an issue with the Docker image on Docker Hub being out of date in respect of operating system package versions. It will have to be rebuilt to allow any images derived from it to build.
This could be an ongoing issue if changes to operating system packages for systemd are going to make the image periodically unusable as a base image until rebuilt.
The root cause needs to be properly understood.

openshift/python-27-centos7 is a dead image.  The right image is centos/python-27-centos7
i tested your dockerfile w/ that image and things work.

If openshift/python-27-centos7 (and other openshift/python-* packages) are regarded as dead and shouldn't be used, then there should be a warning in the descriptions on Docker Hub Registry pointing at what images should be used instead.
Better still, the images should be replaced with one which is effectively:
FROM centos/python-27-centos7

ONBUILD RUN echo "WARNING: The 'openshift/python-27-centos7' image is deprecated, use 'centos/python-27-centos7' instead"

and which is still updated each time the base image is updated.
This way users who were using the image under the old name will still get updates, plus get a warning when building a derived image that they are using an image name which is deprecated.
This avoids problems with Docker Hub Registry just becoming a graveyard for obsolete and unmaintained images where people are none the wiser that they are using old images.

@GrahamDumpleton I like that idea, @bparees ?

to be clear, openshift/python-33-centos7 is not dead.  We own 33 so it's in the openshift namepsace.  SCL owns 27 and 34 so those are in the centos namespace, per their request.
I'm happy to update the dockerhub text, i'm less inclined to update the images themselves as that could break people who are trying to use them as is.  I'm less worried about someone new trying to use that image and having it not work, than about breaking someone who still has a reference to it.
And because of the way s2i handles images that have onbuild instructions, adding that is going to make s2i builds extra slow (we will perform a docker build in order to ensure the onbuild instruction gets run).