gerrit.ovirt.org upgrade
by Denis Volkov
Hello
Gerrit.ovirt.org will be upgraded later today. Approximate start time is
4PM UTC.
During the upgrade service will be shut down and so will not be available.
--
Denis Volkov
2 years, 8 months
Build failed in Jenkins: system-sync_mirrors-mock-copr-el7-x86_64
#2907
by jenkins@jenkins.phx.ovirt.org
See <https://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-el7-x86_64/29...>
Changes:
------------------------------------------
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on mirrors-wdc.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-el7-x86_64/ws/>
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository http://gerrit.ovirt.org/jenkins.git
> git init <https://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-el7-x86_64/ws...> # timeout=10
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git --version # 'git version 2.27.0'
> git fetch --tags --force --progress -- http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git fetch --tags --force --progress --prune -- http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 92a262682fa85dca5eb3d155478ae03e83cbf686 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 92a262682fa85dca5eb3d155478ae03e83cbf686 # timeout=10
Commit message: "default checkout repo timeout extended to 30"
> git rev-list --no-walk 92a262682fa85dca5eb3d155478ae03e83cbf686 # timeout=10
[system-sync_mirrors-mock-copr-el7-x86_64] $ /bin/bash -xe /tmp/jenkins13550080929707638786.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror mock-copr-el7 x86_64 jenkins/data/mirrors-reposync.conf
+ MIRRORS_MP_BASE=/var/www/html/repos
+ MIRRORS_HTTP_BASE=http://mirrors-wdc.ovirt.org/repos
+ MIRRORS_CACHE=/home/jenkins/mirrors_cache
+ YUM_PATH=/yum/
+ MIRRORS_BASE_PREFIX=/var/www/html/repos/yum/
+ REPOQUERY_HTTP_BASE=http://mirrors-wdc.ovirt.org/repos/yum/
+ MAX_LOCK_ATTEMPTS=120
+ LOCK_WAIT_INTERVAL=5
+ LOCK_BASE=/home/jenkins
+ OLD_MD_TO_KEEP=100
+ MAX_AGE=14
+ HTTP_SELINUX_TYPE=httpd_sys_content_t
+ HTTP_FILE_MODE=644
+ main resync_yum_mirror mock-copr-el7 x86_64 jenkins/data/mirrors-reposync.conf
+ local command=resync_yum_mirror
+ command_args=("${@:2}")
+ local command_args
+ cmd_resync_yum_mirror mock-copr-el7 x86_64 jenkins/data/mirrors-reposync.conf
+ local repo_name=mock-copr-el7
+ local repo_archs=x86_64
+ local reposync_conf=jenkins/data/mirrors-reposync.conf
+ local sync_needed
+ mkdir -p /home/jenkins/mirrors_cache
+ verify_repo_fs mock-copr-el7 yum
+ local repo_name=mock-copr-el7
+ local repo_type=yum
+ sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/mock-copr-el7 /var/www/html/repos/yum/mock-copr-el7/base
+ modify_reposync_conf mock-copr-el7 jenkins/data/mirrors-reposync.conf
+ local repo_name=mock-copr-el7
+ local reposync_conf=jenkins/data/mirrors-reposync.conf
+ local tmp_file=reposync.tmp
+ awk -v RS= -v 'ORS=\n\n' /main/ jenkins/data/mirrors-reposync.conf
+ awk -v RS= -v 'ORS=\n\n' /mock-copr-el7/ jenkins/data/mirrors-reposync.conf
+ mv reposync.tmp jenkins/data/mirrors-reposync.conf
+ check_yum_sync_needed mock-copr-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed
+ local repo_name=mock-copr-el7
+ local repo_archs=x86_64
+ local reposync_conf=jenkins/data/mirrors-reposync.conf
+ local p_sync_needed=sync_needed
+ local reposync_out
+ echo 'Checking if mirror needs a resync'
Checking if mirror needs a resync
+ rm -rf /home/jenkins/mirrors_cache/mock-copr-el7
++ IFS=,
++ echo x86_64
+ for arch in $(IFS=,; echo $repo_archs)
++ run_reposync mock-copr-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet
++ local repo_name=mock-copr-el7
++ local repo_arch=x86_64
++ local reposync_conf=jenkins/data/mirrors-reposync.conf
++ extra_args=("${@:4}")
++ local extra_args
++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=mock-copr-el7 --arch=x86_64 --metadata-path=/home/jenkins/mirrors_cache --download-path=/var/www/html/repos/yum/mock-copr-el7/base --norepopath --urls --quiet
2022-01-13 07:18:01,709 [ERROR] reposync:3659696:MainThread @logutil.py:194 - [Errno 13] Permission denied: '/var/log/rhsm/rhsm.log' - Further logging output will be written to stderr
2022-01-13 07:18:01,711 [ERROR] reposync:3659696:MainThread @identity.py:156 - Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 13] Permission denied: '/etc/pki/consumer/key.pem'
Error: Failed to download metadata for repo 'mock-copr-el7': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
+ reposync_out=
Build step 'Execute shell' marked build as failure
2 years, 9 months
Re: Change in ovirt-engine[master]: packaging: engine-setup: Use
otopi's checkForSafeUpdate
by Yedidyah Bar David
On Wed, Jan 12, 2022 at 12:06 PM Code Review <gerrit(a)ovirt.org> wrote:
>
> From Jenkins CI <jenkins(a)ovirt.org>:
>
> Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-engine/+/116920 )
>
> Change subject: packaging: engine-setup: Use otopi's checkForSafeUpdate
> ......................................................................
>
>
> Patch Set 6:
>
> Build Failed
>
> https://jenkins.ovirt.org/job/standard-enqueue/36418/ :
> This change was not submitted to any change queues for system testing. You will need to create some 'build-artifacts' jobs if you want changes to be submitted to change queues, take part in the system tests and be deployed to the nightly snapshot repositories. If your project uses STDCI V2 and you have release branches configured, you may disregard this message.
>
>
> https://jenkins.ovirt.org/job/ovirt-engine_standard-on-merge/2762/ : UNSTABLE
I think it's because of:
[2022-01-12T09:42:30.703Z] Traceback (most recent call last):
[2022-01-12T09:42:30.703Z] File
"/home/jenkins/agent/workspace/ovirt-engine_standard-on-merge(a)tmp/durable-ecea2c02/script.sh",
line 10, in <module>
[2022-01-12T09:42:30.703Z] change = GerritMergedChange.from_jenkins_env()
[2022-01-12T09:42:30.703Z] File
"/home/jenkins/agent/workspace/ovirt-engine_standard-on-merge/jenkins/stdci_libs/change_queue/changes/__init__.py",
line 290, in from_jenkins_env
[2022-01-12T09:42:30.703Z] o =
cls(gerrit_patchset=GerritPatchset.from_jenkins_env())
[2022-01-12T09:42:30.703Z] File
"/home/jenkins/agent/workspace/ovirt-engine_standard-on-merge/jenkins/stdci_libs/gerrit.py",
line 157, in from_jenkins_env
[2022-01-12T09:42:30.703Z] 'GERRIT_PATCHSET_UPLOADER', env
[2022-01-12T09:42:30.703Z] File
"/home/jenkins/agent/workspace/ovirt-engine_standard-on-merge/jenkins/stdci_libs/gerrit.py",
line 97, in from_jenkins_env
[2022-01-12T09:42:30.703Z] return cls(env[prefix + '_NAME'],
env[prefix + '_EMAIL'])
[2022-01-12T09:42:30.703Z] File "/usr/lib64/python3.6/os.py", line
669, in __getitem__
[2022-01-12T09:42:30.703Z] raise KeyError(key) from None
[2022-01-12T09:42:30.703Z] KeyError: 'GERRIT_PATCHSET_UPLOADER_NAME'
and I *think* it's because I commented 'ost check' on two patches,
which were one above the other, and CI merged the upper one before
finishing the gating of the lower one (current).
Current case can most probably be ignored, but I wonder if we want to
do something in the general case - perhaps the code already does
everything well, didn't check - e.g. checking that all pending patches
in the stack have all acks, etc.
Best regards,
--
Didi
2 years, 9 months
resources.ovirt.org's cert expired
by Yedidyah Bar David
Hi all,
$Subject:
Not After Sun, 02 Jan 2022 05:06:16 GMT
Do we have the renewal automated?
This currently breaks some CI flows.
Thanks and best regards,
--
Didi
2 years, 9 months