# Pastebin a4BJ7Rfu
                       - update content in file /etc/yum.repos.d/RDO-kilo.repo from none to dd5731
                       --- /etc/yum.repos.d/RDO-kilo.repo       2015-03-04 15:40:40.559599733 +0000
                       +++ /tmp/chef-rendered-template20150304-11653-1848nkc    2015-03-04 15:40:40.559599733 +0000
                       @@ -1 +1,11 @@
                       +# This file was generated by Chef
                       +# Do NOT modify this file by hand.
                       +
                       +[RDO-kilo]
                       +name=OpenStack RDO repo for kilo
                       +baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-kilo/epel-7
                       +enabled=1
                       +gpgcheck=1
                       +gpgkey=https://raw.githubusercontent.com/redhat-openstack/rdo-release/master/RPM-GPG-KEY-RDO-Kilo
                       +sslverify=true[2015-03-04T15:40:40+00:00] INFO: template[/etc/yum.repos.d/RDO-kilo.repo] mode changed to 644

                       - change mode from '' to '0644'
                       - restore selinux security context
                 [2015-03-04T15:40:40+00:00] INFO: template[/etc/yum.repos.d/RDO-kilo.repo] sending run action to execute[yum-makecache-RDO-kilo] (immediate)
                     * execute[yum-makecache-RDO-kilo] action run[2015-03-04T15:40:40+00:00] INFO: Processing execute[yum-makecache-RDO-kilo] action run (/var/chef/cache/cookbooks/yum/providers/repository.rb line 55)
                 http://repos.fedorapeople.org/repos/openstack/openstack-kilo/epel-7/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
                 Trying other mirror.


                  One of the configured repositories failed (OpenStack RDO repo for kilo),
                  and yum doesn't have enough cached data to continue. At this point the only
                  safe thing yum can do is fail. There are a few ways to work "fix" this:

                      1. Contact the upstream for the repository and get them to fix the problem.

                      2. Reconfigure the baseurl/etc. for the repository, to point to a working
                         upstream. This is most often useful if you are using a newer
                         distribution release than is supported by the repository (and the
                         packages for the previous distribution release still work).

                      3. Disable the repository, so yum won't use it by default. Yum will then
                         just ignore the repository until you permanently enable it again or use
                         --enablerepo for temporary usage:

                             yum-config-manager --disable RDO-kilo

                      4. Configure the failing repository to be skipped, if it is unavailable.
                         Note that yum will try to contact the repo. when it runs most commands,
                         so will have to try and fail each time (and thus. yum will be be much
                         slower). If it is a very temporary problem though, this is often a nice
                         compromise:

                             yum-config-manager --save --setopt=RDO-kilo.skip_if_unavailable=true

                 failure: repodata/repomd.xml from RDO-kilo: [Errno 256] No more mirrors to try.
                 http://repos.fedorapeople.org/repos/openstack/openstack-kilo/epel-7/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found