- Devel - oVirt List Archives

proposing Ales Musil as a frontend maintainer
by Greg Sheremeta 17 May '19

17 May '19

Hi all, I'd like to propose Ales Musil as a frontend maintainer for network parts of the admin portal UI. Since joining the team 2 years ago, Ales has quickly become very knowledgeable about all of the GWT intricacies of the admin portal. I trust his expertise and judgment. Best wishes, Greg -- Greg Sheremeta Senior Software Engineer Red Hat <https://www.redhat.com/> <https://www.redhat.com/>

7 8

ovirt-system-tests_compat-4.2-suite-master failing for 3 weeks?
by Doron Fediuck 17 May '19

17 May '19

https://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/55… The current failure is on adding a storage domain. Did anyone review it?

7 10

Fedora 30 is available in STD-CI.
by Ehud Yonasi 16 May '19

16 May '19

Hey everyone, If you want to build your packages on top of fc30 it is now available. Also, we are planning to drop the support for fc27 as it is EOL, so if you could please prepare patches to remove it, it would be greatly appreciated. Regards, Ehud Yonasi.

2 1

engine setup on F30 is broken due to missing python3-ovirt_setup_lib
by Roy Golan 16 May '19

16 May '19

We still didn't build python3-ovirt-setup-lib for f30, so engine-setup will fail for those of you using f30. If you want it to work, install the f29 version: https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc29/noarch/pytho… +Gal Zaidman <gzaidman(a)redhat.com> +Yedidyah Bar David <didi(a)redhat.com>

2 1

Re: make rpm for vdsm on CentOS Linux release 7.6.1810 (Core)
by Nir Soffer 15 May '19

15 May '19

On Wed, May 15, 2019 at 4:28 PM Amit Bawer <abawer(a)redhat.com> wrote: > Hi, > > I am trying to follow the basic procedure described here > https://github.com/oVirt/vdsm > This is not a good place to look for the instructions. The right place is: https://ovirt.org/develop/developer-guide/vdsm/developers.html > to build vdsm rpm from source on my CentOS Linux release 7.6.1810 (Core) > host. > had to add some dependencies on the way ofcourse, so at that point i am > able to make most of it except for python error described below resulting > from the "make rpm" part of procedure. > > Am I missing something? > This is a good topic for devel, adding. > > Thanks > > make[1]: Entering directory `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0' > Makefile:1002: warning: overriding recipe for target `check-recursive' > Makefile:533: warning: ignoring old recipe for target `check-recursive' > Making all in contrib > make[2]: Entering directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/contrib' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/contrib' > Making all in helpers > make[2]: Entering directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/helpers' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/helpers' > Making all in init > make[2]: Entering directory `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/init' > Making all in systemd > make[3]: Entering directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/init/systemd' > MKDIR_P ./ > SED vdsm-tmpfiles.d.conf > make[3]: Leaving directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/init/systemd' > make[3]: Entering directory `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/init' > MKDIR_P ./ > SED vdsmd_init_common.sh > make[3]: Leaving directory `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/init' > make[2]: Leaving directory `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/init' > Making all in lib > make[2]: Entering directory `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/lib' > Making all in sos > make[3]: Entering directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/lib/sos' > MKDIR_P ./ > SED vdsm.py > make[3]: Leaving directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/lib/sos' > Making all in vdsm > make[3]: Entering directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/lib/vdsm' > Making all in api > make[4]: Entering directory > `/home/abawer/rpmbuild/BUILD/vdsm-4.40.0/lib/vdsm/api' > Generate vdsm-api.html > chmod u+w . > PYTHONPATH=./../../:./../../vdsm \ > python2.7 ./schema_to_html.py vdsm-api ./vdsm-api.html > Traceback (most recent call last): > File "./schema_to_html.py", line 250, in <module> > main() > File "./schema_to_html.py", line 240, in main > > * choices=[st.value for st in vdsmapi.SchemaType])TypeError: 'type' > object is not iterable* > Never had this error. After you prepare the host as described in: https://ovirt.org/develop/developer-guide/vdsm/developers.html#installing-t… https://ovirt.org/develop/developer-guide/vdsm/developers.html#getting-the-… https://ovirt.org/develop/developer-guide/vdsm/developers.html#installing-t… is to install latest release of vdsm: yum install vdsm vdsm-client Otherwise you will have to painfully install some of the packages or install lot of packages you don't need (e.g. mostly lot of hooks). When your host is ready, you can build vdsm from source and upgrade the installed packages: git clean -dxf ./autogen.sh --system --enable-timestamp make rm -rf ~/rpmbuild make rpm (cd ~/rpmbuild/RPMS && sudo yum upgrade */*.rpm) I think we should drop instructions in vdsm README, and point to the page on ovirt.org, or replace them with short version that works and easier to maintain. Nir

2 1

Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
by Nir Soffer 15 May '19

15 May '19

I tried to run check-patch and check-patch linters substage from the command line: using: https://github.com/nirs/oci/pull/37 I assumed that this will run the entire check-patch stage, including all the sub stages: ./ovirt-ci run -s check-patch 100007 But it run something that looks like check-patch with el7: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… The test environment seems to be different that what we have when check-patch is triggered from gerrit. Then I tried to run the linters substage: ./ovirt-ci run -s check-patch.linters 100007 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… ./ovirt-ci run -s check-patch.linters 100007 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… Both succeeded without running anything :-) Running build-artifacts works, not sure about check-network. Can we fix the manual job so: - it run exactly the same way as it run when gerrit trigger the job - allow selection of a sub stage? - nice to have - allow selection of multiple sub stages Nir

1 1

vdsm has been tagged (v4.30.15)
by Milan Zamazal 14 May '19

14 May '19

1 0

import VM from data domain
by IT INFRA 14 May '19

14 May '19

Hi, This forum really help me a lot..Thanks everyone I have an problem on importing VM from newly imported data domain storage, this is the scenario. 1) New engine restore from backup (4.1 version) 2) Import old storage domain using domain function (data) problem: I can't see any VM to import in (VM Import tab) Please help me import my old VM... Sorry for my bad English,... Thanks,

1 0

ovirt 4.1 backup/restore
by IT INFRA 14 May '19

14 May '19

Hi, It is possible to install ovirt 4.1 the old version upong checking on this link (http://mirror.centos.org/centos/7/virt/x86_64/) no 4.1 version, Used for restoring old backup engine. Thanks,

3 4

vdsm has been tagged (v4.30.14)
by Milan Zamazal 14 May '19

14 May '19

1 0