Dominik Holler <dholler@redhat.com> writes:
> On Mon, Jun 22, 2020 at 9:34 AM Milan Zamazal <mzamazal@redhat.com> wrote:
>
>> Nir Soffer <nsoffer@redhat.com> writes:
>>
>> > On Sun, Jun 21, 2020 at 1:18 PM Amit Bawer <abawer@redhat.com> wrote:
>> >>
>> >> Hi
>> >
>> >>
>> >> Seems that in the last few days the el8 CI for vdsm cannot run, were
>> there any el8 repo changes?
>> >>
>> >> [2020-06-21T09:20:03.003Z] Mock Version: 2.2
>> >> [2020-06-21T09:20:03.003Z] INFO: Mock Version: 2.2
>> >> [2020-06-21T09:20:03.987Z] Start: dnf install
>> >> [2020-06-21T09:20:12.326Z] ERROR: Command failed:
>> >> [2020-06-21T09:20:12.326Z] # /usr/bin/dnf --installroot
>> >> /var/lib/mock/epel-8-x86_64-8e9eeb575ab4da7bf0fbfdc80a25b9c0-30232/root/
>> >> --releasever 8 --setopt=deltarpm=False --allowerasing
>> >> --disableplugin=local --disableplugin=spacewalk
>> >> --disableplugin=local --disableplugin=spacewalk install dnf tar
>> >> gcc-c++ redhat-rpm-config which xz sed make bzip2 gzip gcc coreutils
>> >> unzip shadow-utils diffutils cpio bash gawk rpm-build info patch
>> >> util-linux findutils grep python36 autoconf automake createrepo dnf
>> >> dnf-utils e2fsprogs gcc gdb git iproute-tc iscsi-initiator-utils
>> >> libguestfs-tools-c lshw make openvswitch ovirt-imageio-common
>> >> python3-augeas python3-blivet python3-coverage python3-dateutil
>> >> python3-dbus python3-decorator python3-devel python3-dmidecode
>> >> python3-inotify python3-ioprocess-1.4.1 python3-libselinux
>> >> python3-libvirt python3-magic python3-netaddr python3-nose
>> >> python3-pip python3-policycoreutils python3-pyyaml python3-requests
>> >> python3-sanlock python3-six python3-yaml rpm-build rpmlint sanlock
>> >> sudo systemd-udev xfsprogs --setopt=tsflags=nocontexts
>> >> [2020-06-21T09:20:12.326Z] No matches found for the following
>> >> disable plugin patterns: local, spacewalk
>> >> [2020-06-21T09:20:12.326Z] Last metadata expiration check: 0:00:02 ago
>> on Sun Jun 21 09:20:07 2020.
>> >> [2020-06-21T09:20:12.326Z] No match for argument: openvswitch
>> >> [2020-06-21T09:20:12.326Z] Error: Unable to find a match: openvswitch
>> >>
That
was required to fix this raises the question from which repo openvswitch was consumed before.
But never mind, it is fixed now.
>> >> Taken from
>> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/21966/consoleText
>> >
>> > I think this is a result of trying to move to CentOS 8.2 before all
>> > the packages are
>> > ready.
>>
>> There are problems with openvswitch package since the CentOS 8.2 update.
>> It also blocks Vdsm builds. Sandro and Dominik work on solving it.
>>
>>
> This seems to be something unrelated in the build system.
> CI should work since last Tuesday again.
I'm not sure which CI you mean, but Vdsm CI on master is still broken,
even with Sandro's patch adding the oVirt 4.4 virt repo
(https://gerrit.ovirt.org/109714):
Running transaction check
[2020-06-22T08:54:51.868Z] warning: Generating 18 missing index(es), please wait...
[2020-06-22T08:54:51.868Z] Error: transaction check vs depsolve:
[2020-06-22T08:54:51.868Z] /bin/sh is needed by ovirt-openvswitch-2.11-0.2020061801.el8.noarch
[2020-06-22T08:54:51.868Z] bash is needed by ovirt-openvswitch-2.11-0.2020061801.el8.noarch
[2020-06-22T08:54:51.868Z] systemd is needed by ovirt-openvswitch-2.11-0.2020061801.el8.noarch
[2020-06-22T08:54:51.868Z] To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
[2020-06-22T08:54:51.868Z] You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the issue.
[2020-06-22T08:54:51.868Z] The downloaded packages were saved in cache until the next successful transaction.
[2020-06-22T08:54:51.868Z] You can remove cached packages by executing 'dnf clean packages'.
Besides it puts -1 on each patch, we can't have any Vdsm builds until it
is fixed. Without the Sandro's patch, we get the error posted by Amit
above.
Any ideas how to proceed? Why is RPMDB reported as corrupted, were
caches on the CI flushed?
Anton and Evgheni, can you please help us?
> Is the list of allowed packages for the CI limited, or is every package
> from ovirt-repo allowed?
>
>
>> > Please use Travis until this issue is resolved. You should use it
>> > anyway for storage
>> > patches.
>> >
>> > Nir
>>
>>