- Devel - oVirt List Archives

Issues with Anaconda in CentOS 8.3
by Sandro Bonazzola 16 Dec '20

16 Dec '20

Hi, I've an issue with Anaconda in CentOS 8.3. In 8.2 storage allocation was presented as: [image: oVirtNode-4.4.3-custom.png] ISO: https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.3… while in 8.3: [image: oVirtNode-master-custom.png] ISO: https://jenkins.ovirt.org/job/ovirt-node-ng-image_standard-check-patch/276/… I checked and the ovirt.conf file is correctly placed into /etc/anaconda/product.d but then looking in /run/anaconda/anaconda.conf I see it has been detected as product Red Hat Enterprise Linux. Anaconda reports version 33.16.3.26. With same ovirt.conf but using CentOS Stream as base OS: [image: oVirtNode master stream.png] ISO: https://jenkins.ovirt.org/job/ovirt-node-ng-image_standard-check-patch/277/… here the ovirt.conf file seems correctly loaded, in /run/anaconda/anaconda.conf I correctly see oVirt Node Next as product. Here there's still a regression on /var/crash not on separate volume when compared to 8.2 but at least it seems the configuration is loaded correctly. anaconda reports version 33.16.3.26 as well as in CentOS 8.3. Any clue? -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Dropping all el7 OST runs
by Marcin Sobczyk 15 Dec '20

15 Dec '20

Hi, since all the important suites are working on el8 already, we're planning to drop all el7 OST runs with [1] very soon. This means we can finally say goodbye to py2 and other legacy stuff! We still need to move manual OST runs not to use containers for that to happen. This effort is tracked here [2]. Regards, Marcin [1] https://gerrit.ovirt.org/112378 [2] https://ovirt-jira.atlassian.net/browse/OST-145

5 13

ovirt-engine CI check-patch failed
by Eyal Shenitzky 15 Dec '20

15 Dec '20

Hi, I see the following error on the CI - *14:03:36* + usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc. <https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9286/consol…>*14:03:36* + [[ -x /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py ] <https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9286/consol…>*14:03:36* + /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py --log -d get <https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9286/consol…>*14:03:36* /usr/bin/env: ‘python’: No such file or directory See - https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9286/console Can someone please take a look? <https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9286/console> Regards, Eyal Shenitzky

2 1

OST failures on dnf_upgrade
by Marcin Sobczyk 14 Dec '20

14 Dec '20

Hi All, there's a known issue with OST failing right now during deployment on 'dnf_upgrade'. The problem is that 'mdevctl' package is missing in CentOS repos and new libvirt versions require it. While we wait for an official fix, we're rebuilding ost-images with the package included from a copr build. Hopefully OST will work in 1-2 hours. Sorry for the inconvenience. Regards, Marcin

2 1

Ovirt Engine migration to Wildfly 21
by Artur Socha 10 Dec '20

10 Dec '20

Hi, I am working at the moment on the migration of Ovirt Engine to Wildfly 21. I have encountered an issue with the http-remoting-connector which uses the 'default' connector. After the switch to Wildfly 21 this is no longer working. There is an error in server.log complaining about this service not being started ... however, I have not noticed that anything from the engine's core functionality is broken. There are even OST passing with this error. Does anyone know about any usages of remoting components in ovirt engine? Perhaps this could be removed as 'dead' configuration? Assuming, it is being used - I have a patch that seems to fix the problem [1]. The thing is that I still don't understand why this change is now required. 'Default' in reference configuration ie. standalone-full.xml is just http with redirect to https. Any help much appreciated. [1] https://gerrit.ovirt.org/#/c/ovirt-engine/+/112505/ -- Artur Socha Senior Software Engineer, RHV Red Hat

2 3

OST master fails on basic-suite-master.test-scenarios.test_004_basic_sanity.test_sparsify_disk1
by Galit Rosenthal 10 Dec '20

10 Dec '20

Hi It looks like basic suite master is failing on basic-suite-master.test-scenarios.test_004_basic_sanity.test_sparsify_disk1 (from pytest) [1] E ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot sparsify Virtual Disk. Sparsifying is not supported for QCOW2 disk vm1_disk1.]". HTTP response code is 400. Can someone have a look? Thanks Galit [1] https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_bas… -- Galit Rosenthal SOFTWARE ENGINEER Red Hat <https://www.redhat.com/> galit(a)redhat.com T: 972-9-7692230 <https://www.redhat.com/>

2 1

Problems building CentOS 8.3-based engine image for OST
by Marcin Sobczyk 09 Dec '20

09 Dec '20

Hi All, since CentOS 8.3 is out, I'm trying to build a new base image for OST, but there are problems on the engine side. The provisioning script we use to build the engine VM is here [1]. The build ends with errors: Error: Problems in request: missing groups or modules: javapackages-tools Last metadata expiration check: 0:00:02 ago on Mon Dec 7 16:00:56 2020. Error: Problem 1: cannot install the best candidate for the job - nothing provides apache-commons-compress needed by ovirt-engine-4.4.4.4-0.0.master.20201206151430.git1a096b0d4e7.el8.noarch - nothing provides apache-commons-jxpath needed by ovirt-engine-4.4.4.4-0.0.master.20201206151430.git1a096b0d4e7.el8.noarch Problem 2: package ovirt-engine-extension-aaa-ldap-setup-1.4.3-0.289.202010220206.el8.noarch requires ovirt-engine-extension-aaa-ldap = 1.4.3-0.289.202010220206.el8, but none of the providers can be installed - package ovirt-engine-extension-aaa-ldap-1.4.3-0.289.202010220206.el8.noarch requires slf4j-jdk14, but none of the providers can be installed - conflicting requests - package slf4j-jdk14-1.7.25-4.module_el8.3.0+454+67dccca4.noarch is filtered out by modular filtering Please advise. Thanks, Marcin [1] https://gerrit.ovirt.org/gitweb?p=ost-images.git;a=blob_plain;f=el8-provisi…

4 7

ovirt-engine has been tagged (ovirt-engine-4.4.4.4)
by Tal Nisan 09 Dec '20

09 Dec '20

2 1

OST images moved to CentOS 8.3
by Marcin Sobczyk 09 Dec '20

09 Dec '20

Hi, the prebuilt OST images have been migrated to CentOS 8.3. If you find any issues with the new images, please let me know. There is a known issue of 'test_098_ovirt_provider_ovn' failing, but it's not related to CentOS 8.3 and should be fixed as soon as we get a new engine build. We also have a new layer of 'ost-images-el8-he-installed' that contains 'ovirt-hosted-engine-appliance' installed and is beneficial to HE suites. Finally, somehow related to yesterday's announcement, fyi we already have nightly-built OST images based on CentOS Stream since quite some time. For those of you interested in trying them out it should be as simple as: dnf install ost-images-el8stream-engine-installed ost-images-el8stream-host-installed export OST_IMAGES_DISTRO=el8stream ./run_suite.sh basic-suite-master Regards, Marcin

1 0

ost check patch
by Eitan Raviv 08 Dec '20

08 Dec '20

Hi, Since yesterday check patch jobs [1][2] are failing for me on emulator not found... kvm executable not found Any hint appreciated. Thanks [1] https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… [2] https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta…

4 5