prod [root@adplbs001prpntg ~]# puppet agent -t --no-noop
Info: Using configured environment 'main'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
        Info: Caching catalog for adplbs001prpntg.lin.pr.adform.zone.b5721dd7554cef47c60786d917efc59c
Info: Applying configuration version '785ffc4 - Auto Bot, Wed Oct 25 14:23:43 2017 +0200 : Merge branch 'csaslb_cm' into 'main''
Notice: /Stage[main]/Profiles::Nginx/Yumrepo[Adform-nginx]/ensure: created
Info: changing mode of /etc/yum.repos.d/Adform-nginx.repo from 600 to 644
Notice: [nginx] *** DEPRECATION WARNING***: HI! I notice that you're declaring some attributes in Class[nginx]. It is highly recommended to set these values via Hiera going forward. This will become mandatory in the near future. Please check out https://github.com/jfryman/puppet-nginx/blob/master/docs/hiera.md for more information.
Notice: /Stage[main]/Nginx::Notice::Config/Notify[[nginx] *** DEPRECATION WARNING***: HI! I notice that you're declaring some attributes in Class[nginx]. It is highly recommended to set these values via Hiera going forward. This will become mandatory in the near future. Please check out https://github.com/jfryman/puppet-nginx/blob/master/docs/hiera.md for more information.]/message: defined 'message' as '[nginx] *** DEPRECATION WARNING***: HI! I notice that you're declaring some attributes in Class[nginx]. It is highly recommended to set these values via Hiera going forward. This will become mandatory in the near future. Please check out https://github.com/jfryman/puppet-nginx/blob/master/docs/hiera.md for more information.'
Notice: /Stage[main]/Nginx::Package::Redhat/Yumrepo[nginx-release]/ensure: created
Info: changing mode of /etc/yum.repos.d/nginx-release.repo from 600 to 644
Warning: Puppet::Type::Package::ProviderYum: Could not check for updates, '/usr/bin/yum check-update' exited with 1
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install yum-plugin-versionlock' returned 1: One of the configured repositories failed (Unknown),
 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. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, 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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. 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=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: Adform-nginx
Error: /Stage[main]/Yum::Plugin::Versionlock/Yum::Plugin[versionlock]/Package[yum-plugin-versionlock]/ensure: change from purged to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install yum-plugin-versionlock' returned 1: One of the configured repositories failed (Unknown),
 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. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, 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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. 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=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: Adform-nginx
Notice: /Stage[main]/Profiles::Auditd/Auditd::Audisp::Plugin[syslog]/File[/etc/audisp/plugins.d/syslog.conf]: Dependency Package[yum-plugin-versionlock] has failures: true
Warning: /Stage[main]/Profiles::Auditd/Auditd::Audisp::Plugin[syslog]/File[/etc/audisp/plugins.d/syslog.conf]: Skipping because of failed dependencies
Notice: /Stage[main]/Profiles::Auditd/Auditd::Audisp::Plugin[af_unix]/File[/etc/audisp/plugins.d/af_unix.conf]: Dependency Package[yum-plugin-versionlock] has failures: true
Warning: /Stage[main]/Profiles::Auditd/Auditd::Audisp::Plugin[af_unix]/File[/etc/audisp/plugins.d/af_unix.conf]: Skipping because of failed dependencies
Notice: /Stage[main]/Profiles::Auditd/Auditd::Audisp::Plugin[au-remote]/File[/etc/audisp/plugins.d/au-remote.conf]: Dependency Package[yum-plugin-versionlock] has failures: true
Warning: /Stage[main]/Profiles::Auditd/Auditd::Audisp::Plugin[au-remote]/File[/etc/audisp/plugins.d/au-remote.conf]: Skipping because of failed dependencies
Notice: /Stage[main]/Profiles::Auditd/Auditd::Audisp::Plugin[audispd-zos-remote]/File[/etc/audisp/plugins.d/audispd-zos-remote.conf]: Dependency Package[yum-plugin-versionlock] has failures: true
Warning: /Stage[main]/Profiles::Auditd/Auditd::Audisp::Plugin[audispd-zos-remote]/File[/etc/audisp/plugins.d/audispd-zos-remote.conf]: Skipping because of failed dependencies
Notice: /Stage[main]/Auditd/Service[auditd]: Dependency Package[yum-plugin-versionlock] has failures: true
Warning: /Stage[main]/Auditd/Service[auditd]: Skipping because of failed dependencies
Notice: /Stage[main]/Profiles::Puppet::Agent/Yum::Versionlock[0:puppet-agent-1.3.6-1.el7.]/File_line[versionlock.list-0:puppet-agent-1.3.6-1.el7.]: Dependency Package[yum-plugin-versionlock] has failures: true
Warning: /Stage[main]/Profiles::Puppet::Agent/Yum::Versionlock[0:puppet-agent-1.3.6-1.el7.]/File_line[versionlock.list-0:puppet-agent-1.3.6-1.el7.]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
Notice: Applied catalog in 5.95 seconds
prod [root@adplbs001prpntg ~]#