- Devel - oVirt List Archives

Building python 2 and python 3 packages for Fedora
by Nir Soffer 12 Jun '19

12 Jun '19

In several projects (e.g. vdsm, imageio, sanlock), we have the issue of building python 3 packages for Fedora. The current build process create packages with the same name for both python 2 and python 3. When the packages are published to oVirt repository, the python 3 packages overwrite the python 2 packages. We can rename the packages properly (e.g. python2-xxx, python3-xxx) but this requires lot of work and typically breaks later in the code publishing the packages. There is also the difficulty of building both python 2 and python 3 packages from same spec in the same build. This should be possible but not easy. Since python 2 is about to die soon, should we simplify by building python 2 *or* python 3, depending on version? Fedora 29: python 2.7 Fedora 30: python 3.7 CentOS 7: python 2.7 CentOS 8: python 3.6 This make it possible to test and develop on python 2.7 until vdsm is fully functional on python 3, and it save resources in the CI. Thoughts? Nir

3 4

Failed to add fedora-29 host to oVirt
by Eyal Shenitzky 12 Jun '19

12 Jun '19

Hi, I am trying to add fedora-29 host to me oVirt setup and failed due to the following error (from the engine log): 2019-06-11 11:24:59,123+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [73c7d83d] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host fedora_29: DNF Problem: conflicting requests - package ovirt-host-4.4.0-0.0.master.20190610132028.git410e453.fc29.x86_64 requires ovirt-hosted-engine-setup, but none of the providers can be installed - package ovirt-host-4.4.0-0.0.master.20190610131544.git410e453.fc29.s390x does not have a compatible architecture - nothing provides ovirt-host-dependencies = 4.4.0-0.0.master.20190610131544.git410e453.fc29 needed by ovirt-host-4.4.0-0.0.master.20190610131544.git410e453.fc29.s390x - nothing provides ovirt-hosted-engine-ha >= 2.4 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190606085519.gitf8402ad.fc29.noarch - nothing provides vdsm-python >= 4.30 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190606085519.gitf8402ad.fc29.noarch - nothing provides ovirt-hosted-engine-ha >= 2.4 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190610121403.gitb2ee866.fc29.noarch - nothing provides glusterfs-cli >= 5.6 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190610121403.gitb2ee866.fc29.noarch - nothing provides vdsm-python >= 4.40.0 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190610121403.gitb2ee866.fc29.noarch. 2019-06-11 11:24:59,133+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [73c7d83d] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host fedora_29: Failed to execute stage 'Package installation': Problem: conflicting requests - package ovirt-host-4.4.0-0.0.master.20190610132028.git410e453.fc29.x86_64 requires ovirt-hosted-engine-setup, but none of the providers can be installed - package ovirt-host-4.4.0-0.0.master.20190610131544.git410e453.fc29.s390x does not have a compatible architecture - nothing provides ovirt-host-dependencies = 4.4.0-0.0.master.20190610131544.git410e453.fc29 needed by ovirt-host-4.4.0-0.0.master.20190610131544.git410e453.fc29.s390x - nothing provides ovirt-hosted-engine-ha >= 2.4 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190606085519.gitf8402ad.fc29.noarch - nothing provides vdsm-python >= 4.30 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190606085519.gitf8402ad.fc29.noarch - nothing provides ovirt-hosted-engine-ha >= 2.4 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190610121403.gitb2ee866.fc29.noarch - nothing provides glusterfs-cli >= 5.6 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190610121403.gitb2ee866.fc29.noarch - nothing provides vdsm-python >= 4.40.0 needed by ovirt-hosted-engine-setup-2.4.0-0.0.master.20190610121403.gitb2ee866.fc29.noarch. When I try to install VDSM manually before adding the host the setup it installed the following version: vdsm-4.18.999-447.git0bb7717.fc28.x86_64 Any suggestions? -- Regards, Eyal Shenitzky

2 3

GetDeviceList and direct LUNs
by Fedor Gavrilov 11 Jun '19

11 Jun '19

Hi, I want to implement a feature that would allow one to manually refresh sizes for direct LUNs and I am not sure if existing code in the engine codebase is gonna help with that. RefreshLunsSizeCommand seems to be doing what is needed, but it operates on a premise that LUNs to refresh belong to a storage domain which makes most of its code irrelevant for purposes of direct LUNs. It seems that workhorse is GetDeviceList command, but from the code I can't quite understand if it's supposed to be used with external iSCSI targets. Especially 'VDS' part here confuses me since I am not sure what VDS we're talking about in the first place when using direct LUN. If GetDeviceList is of no use, is there anything else VDSM provides? Thanks, Fedor Gavrilov

2 5

vdsm has been tagged (v4.30.19)
by Milan Zamazal 11 Jun '19

11 Jun '19

2 1

vdsm has been tagged (v4.30.18)
by Milan Zamazal 11 Jun '19

11 Jun '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.5)
by Tal Nisan 11 Jun '19

11 Jun '19

1 0

Re: oVirt survey - May 2019
by Sandro Bonazzola 10 Jun '19

10 Jun '19

Il giorno lun 20 mag 2019 alle ore 13:30 Sandro Bonazzola < sbonazzo(a)redhat.com> ha scritto: > As we continue to develop oVirt 4.3 and future releases, the Development > and Integration teams at Red Hat would value insights on how you are > deploying the oVirt environment. > Please help us to hit the mark by completing this short survey. Survey > will close on June 7th. > If you're managing multiple oVirt deployments with very different use > cases or very different deployments you can consider answering this survey > multiple times. > Please note the answers to this survey will be publicly accessible. This > survey is under oVirt Privacy Policy available at > https://www.ovirt.org/site/privacy-policy.html > > The survey is available here: https://forms.gle/8uzuVNmDWtoKruhm8 > > The Survey is now closed Results are available here: https://docs.google.com/forms/d/e/1FAIpQLSdBoN2otjkxzJdsdmldpjg5tRl9aqg2vOF… Thanks everyone who participated to the survey! -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

planned gerrit downtime
by Evgheni Dereveanchin 10 Jun '19

10 Jun '19

Hi everyone, I will be migrating gerrit.ovirt.org to a different VM tonight so it will be unavailable for several hours as the process involves copying large amounts of data. It will not be possible to pull from or push to any repos as well as to review changes. I'll follow up as soon as the migration is complete. -- Regards, Evgheni Dereveanchin

3 4

FC28 Blacklisted in oVirt STDCI V2
by Barak Korren 10 Jun '19

10 Jun '19

Hi all, By Snadro's request, as of a few minutes ago FC28 had been blacklisted in oVirt's STDCI V2 system. What this means is that if any project has FC28 threads configured in its STDCI V2 YAML configuration file, those threads will be ignored by the STDCI system and not invoked. Threads for building and testing on other distributions will keep working as before. It is still recommended that projects with fc28 configuration will patch their configuration files to remove FC28, to make it easier to understand what the CI does and not rely on an implicit blacklist. Please note that this only concerns projects that have made the switch to STDCI V2. Projects that still use V1, and have FC28 jobs defined, those jobs will keep working as before. The following patch by Sandro, however, includes code to remove all those jobs: https://gerrit.ovirt.org/c/100556/ Thanks, Barak. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

cannot add host (oVirt 4.3.3.7)
by Hetz Ben Hamo 09 Jun '19

09 Jun '19

Hi, I'm trying to add a new host to oVirt. The main host is Xeon E5 while the new host is AMD Ryzen 5. The main host is running oVirt 4.3.3 and the new node is a minimal install of CentOS 7.6 (1810) with all the latest updates. I'm enclosing the log files. it complains that it cannot get the oVirt packages, perhaps wrong channel(?). Looking at the log, it's trying to use minidnf. I don't think CentOS 7 supports DNF.. Thanks Hetz תודה, *חץ בן חמו* אתם מוזמנים לבקר בבלוג היעוץ <http://linvirtstor.net/> או בבלוג הפרטי שלי <http://benhamo.org>

1 0