February 2017 - Devel - oVirt List Archives

[OST Failure Report] [oVirt master] [09.02.2017] [test-repo_ovirt_experimental_master]
by Shlomo Ben David 21 Feb '17

21 Feb '17

Hi, *Test failed:* [test-repo_ovirt_experimental_master] *Link to suspected patches:* n/a *Link to Job:* http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5217 *Link to all logs:* http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5217/artif… *Error snippet from the log: * <error> ifup/VLAN100_Network::ERROR::2017-02-09 06:21:15,236::concurrent::189::root::(run) FINISH thread <Thread(ifup/VLAN100_Network, started daemon 140189099861760)> failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 185, in run ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 949, in _exec_ifup _exec_ifup_by_name(iface.name, cgroup) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 935, in _exec_ifup_by_name raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '') ConfigNetworkError: (29, 'Determining IPv6 information for VLAN100_Network... failed.') </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

3 2

Ruby SDK NIC search
by Marc Young 21 Feb '17

21 Feb '17

Is there something malformed in this? Based on previous usages of `.list(search: "...")` this does not seem like correct behavior > env[:connection].system_service.vnic_profiles_service.list(search: "name=#{iface_options[:network_name]}").map(&:name) => ["ovirtmgmt", "ovirtmgmt"] > env[:connection].system_service.vnic_profiles_service.list(search: "name=foo").map(&:name) => ["ovirtmgmt", "ovirtmgmt"] > env[:connection].system_service.vnic_profiles_service.list.map(&:name) => ["ovirtmgmt", "ovirtmgmt"] No matter what I provide it always returns all Search works for other services: > env[:connection].system_service.vms_service.list(search: 'name=myvm').map(&:name) => [] > env[:connection].system_service.vms_service.list(search: 'name=testing').map(&:name) => ["testing"] > env[:connection].system_service.vms_service.list(search: 'name=e').map(&:name) => []

2 2

oVirt Cloud-init
by Marc Young 21 Feb '17

21 Feb '17

Are there limitations to cloud-init and oVirt? I wouldn't think so, but i"m having a weird issue. If i use the cloud-init yaml from the ovirt4 ruby sdk examples (ignore formatting, gmail is messing with it): write_files: - content: | Hello, world! path: /tmp/greeting.txt permissions: '0644' it works, that file exists, and it shows in the /var/lib/cloud where i'd expect $ sudo cat /var/lib/cloud/instance/user-data.txt #cloud-config output: all: '>> /var/log/cloud-init-output.log' disable_root: 0 runcmd: - 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo ''datasource_list: ["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg' ssh_pwauth: true chpasswd: expire: false user: root write_files: - content: | Hello, world! path: /tmp/greeting.txt permissions: '0644' If i use this: manage-resolv-conf: true resolv_conf: nameservers: ['192.168.2.113'] searchdomains: - blindrage.local - bar.example.com resolv_conf does not get modified. It looks as expected in /var/lib/cloud: $ sudo cat /var/lib/cloud/instance/user-data.txt #cloud-config output: all: '>> /var/log/cloud-init-output.log' disable_root: 0 runcmd: - 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo ''datasource_list: ["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg' ssh_pwauth: true chpasswd: expire: false user: root manage-resolv-conf: true resolv_conf: nameservers: ['192.168.2.113'] searchdomains: - foo.local - bar.example.com I also don't see anything in /var/log/cloud-init.log or /var/log/cloud-init-output.log on either run even though the write_files yaml worked.

4 12

oVirt 4.1 deep dive - VM leases
by Nir Soffer 21 Feb '17

21 Feb '17

Hi all, I uploaded the recording to youtube: https://www.youtube.com/watch?v=MVa-4fQo2V8 The slides are here: http://redhat.slides.com/nsoffer/vm-leases/fullscreen?token=Gk68hD-B I'll post the slides later to github. Enjoy, Nir

1 0

[ OST Failure Report ] [ ovirt 4.0 ] [ 17.02.17 ] [ add hosts ]
by Dusan Fodor 20 Feb '17

20 Feb '17

Hello, python cpopen missing error occured while deploying host: 2017-02-16 21:44:28 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum [u'python-ioprocess-0.16.1-1.el7.noarch requires python-cpopen', u'vdsm-4.18.21-1.el7.centos.x86_64 requires python-cpopen >= 1.4', u'vdsm-python-4.18.21-1.el7.centos.noarch requires python-cpopen >= 1.4'] Could you please assist? Thanks Link to build: http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_4.0_system-t… Link to host-deploy log: http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_4.0_system-t…

4 4

Invitation: Deep dive - VM leases @ Mon 2017-02-20 18:00 - 18:50 (IST) (devel@ovirt.org)
by nsoffer＠redhat.com 19 Feb '17

19 Feb '17

You have been invited to the following event. Title: Deep dive - VM leases Introduce VM leases, enabling HA failover without power management. - Overview - How VM leases work - What can possibly go wrong? - The xleases special volume - Debugging VM leases - Future work - Live demo When: Mon 2017-02-20 18:00 – 18:50 Jerusalem Where: https://redhat.bluejeans.com/nsoffer Calendar: devel(a)ovirt.org Who: * nsoffer(a)redhat.com - organizer * devel(a)ovirt.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=NThrdTY0cjVidW9pN3NxY… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account devel(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

ovirt-web-ui build failure (missing dep in ovirt-engine-nodejs-modules)
by Sandro Bonazzola 19 Feb '17

19 Feb '17

Build job is failing: http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Builders/job/ovirt-web… error "jquery-3.1.1.tgz": Tarball is not in network and can not be located in cache ("/usr/share/ovirt-engine-nodejs-modules/yarn-offline-cache/jquery-3.1.1.tgz") -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

5 7

Cant get yum update "ovirt-*-setup*" packages to upgrade from 4.0 to 4.1
by Lynn Dixon 19 Feb '17

19 Feb '17

I am following the three simple steps in the release notes here: https://www.ovirt.org/release/4.1.0/ I have added the repo fine, and did a yum clean all just to be cautions. However, when I try to run the yum update "ovirt-*-setup*" command it just returns no updates found. Likewise, if I even try to do a yum update ovirt-engine-setup it returns no updates found. I am currently running oVirt 4.0.6.3-1.el7.centos on a CentOS machine. I feel like I am missing something really simple here, but I can not get it to update any packages beyond the 4.0 repos. I have even tried disabling the 4.0 repos, but no luck. Any suggestions? *Lynn Dixon* | Red Hat Certified Architect #100-006-188 *Sr. Cloud Consultant* | Cloud Management Practice Google Voice: 423-618-1414 Cell/Text: 423-774-3188 Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>

3 12

[ACTION REQUIRED] new dependency -- ovirt-js-dependencies (replaces PatternFly)
by Greg Sheremeta 17 Feb '17

17 Feb '17

Hi, Tomorrow (Tues Feb 14) we'll merge a patch [1] that upgrades the version of PatternFly used by webadmin and userportal to the latest 3.y version. In addition to updating the library, we've also changed the delivery mechanism. We're no longer maintaining a PatternFly RPM on copr [2]. The new method is a new project called ovirt-js-dependencies [3] that contains any runtime JS dependencies required by the engine -- currently patternfly, bootstrap, and jquery. This project is using oVirt Standard CI [4], and thus you should get the RPM from the tested master repo [5]. TL;DR: What you need to do (from the README) Set Up the Tested Master Repository * Automatically - Run the following command (replace `@distro@` in the following code block with `fc` for Fedora or `el` for RHEL or an equivalent distribution): # dnf config-manager --add-repo \ http://plain.resources.ovirt.org/repos/ovirt/tested/master/rpm/@distro@/ * Manually - Create the file `/etc/yum.repos.d/ovirt-tested-master.repo`, and replace `@distro@` in the following code block with `fc` for Fedora or `el` for RHEL or an equivalent distribution. [ovirt-tested-master] name=ovirt-tested-master baseurl= http://plain.resources.ovirt.org/repos/ovirt/tested/master/rpm/@distro@/ enabled=1 gpgcheck=0 And then sudo dnf install ovirt-js-dependencies Let me know if you have any questions. Best wishes, Greg [1] https://gerrit.ovirt.org/#/c/61716 [2] https://copr.fedorainfracloud.org/coprs/patternfly/patternfly1/ [3] https://gerrit.ovirt.org/#/admin/projects/ovirt-js-dependencies [4] http://www.ovirt.org/develop/dev-process/build-and-test-standards/ [5] http://plain.resources.ovirt.org/repos/ovirt/tested/master/rpm/<distro> -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme(a)redhat.com

5 12

oVirt packages for JavaScript development have been updated
by Vojtech Szocs 17 Feb '17

17 Feb '17

Hello devs, following packages, intended as build-time dependencies of oVirt JavaScript projects, have been updated: * ovirt-engine-nodejs * ovirt-engine-nodejs-modules * ovirt-engine-yarn If you use those packages, please read on to learn how to adapt your project. oVirt Dashboard (master) is already adapted and you can use it as your reference. == 1, move your project from npm to Yarn: - using nodejs-modules implies that your project moves from npm to Yarn, please do this as your first step - make sure to add yarn.lock file to source control: rm -rf node_modules && yarn install # generates yarn.lock - your automation/*.packages should contain something like this: ovirt-engine-nodejs-6.9.4 ovirt-engine-nodejs-modules-1.0.3 ovirt-engine-yarn-0.19.1 - since oVirt CI uses yum cache, always specify exact version of nodejs-modules in your automation/*.packages - in your RPM build script, make sure to set up Node.js env.: source /usr/share/ovirt-engine-nodejs-modules/setup-env.sh == 2a, dependency handling - 1st time: - clone nodejs-modules repo & update the projects.list file - add URL(s) to your project's files (package.json + yarn.lock) - bump .z in RPM Version and reset the RPM Release number, submit patch to Gerrit - in your project, update automation/*.packages to use the right nodejs-modules version 2b, dependency handling - whenever your dependencies change: - clone nodejs-modules repo & bump RPM Release number, submit patch to Gerrit - in your project, update automation/*.packages to use the right nodejs-modules version == Q: how does the new nodejs-modules work? A: instead of maintaining one big package.json file to specify all dependencies of all projects (effectively forcing all projects to use single dependency tree), it contains the projects.list file with URL(s) to specific project files. When building nodejs-modules RPM, it goes through the list of URL(s), downloading project's files (package.json + yarn.lock), then downloading required dependencies (using Yarn) and collecting their .tar.gz sources. The nodejs-modules RPM therefore contains a flat list of all .tar.gz sources of all dependencies of all projects. When you source the setup-env.sh script, it does, among other things, tell Yarn to use /usr/share/ovirt-engine-nodejs-modules/yarn-offline-cache containing all .tar.gz sources. Then, it runs Yarn in offline mode to populate your project's node_modules directory. == Hope this helps. Regards, Vojtech

5 14