Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on virtuozzo in workspace /var/lib/jenkins/workspace/virtuozzo-update
No emails were triggered.
[virtuozzo-update] $ /bin/sh -xe /tmp/jenkins7904427897309351198.sh
++ df /home/
++ tail -n +2
++ awk '{print $4}'
+ '[' 34964228 -lt 5242880 ']'
+ /usr/bin/yum -y --enablerepo factory --enablerepo virtuozzolinux-factory update
Loaded plugins: fastestmirror, langpacks, priorities, product-id, refresh-
              : packagekit, rhsm-auto-add-pools, search-disabled-repos,
              : virtuozzo, vzlinux
Trying to discover and attach new pools
https://appcatalog-stage.virtuozzo.com/repo/readykernel-vz7/repodata/repomd.xml: [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate."
Trying other mirror.


 One of the configured repositories failed (Virtuozzo ReadyKernel),
 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=virtuozzo-readykernel ...

     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 virtuozzo-readykernel
        or
            subscription-manager repos --disable=virtuozzo-readykernel

     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=virtuozzo-readykernel.skip_if_unavailable=true

failure: repodata/repomd.xml from virtuozzo-readykernel: [Errno 256] No more mirrors to try.
https://appcatalog-stage.virtuozzo.com/repo/readykernel-vz7/repodata/repomd.xml: [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate."
Build step 'Execute shell' marked build as failure
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Request made to compress build log
Sending email to: ptikhomirov@virtuozzo.com snorcht@gmail.com
Finished: FAILURE