February 2017 - Devel - oVirt List Archives

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

[HEADS UP] Dropping Fedora 24 from master
by Sandro Bonazzola 17 Feb '17

17 Feb '17

Hi, as you may have already noticed, VDSM dropped FC24 support on master. If nobody has valid reason to keep fc24 on master, I'll go ahead and drop all remaining fc24 jobs from master next Friday, Feb 24th. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Unable to start vm on specific host via ruby sdk
by Marc Young 17 Feb '17

17 Feb '17

Using the ruby sdk I'm unable to start a VM on a specific host. According to the API docs at api/v4/model#types/vm_placement_policy : Name Type ---------------- hosts Host[] No matter what I specify, I run into this same bug: https://bugzilla.redhat.com/show_bug.cgi?id=1249521 65: require 'pry' 66: binding.pry 67: => 68: machine.start( 69: use_cloud_init: true, 70: vm: vm_configuration 71: ) 72: 73: @app.call(env) [1] pry(#<VagrantPlugins::OVirtProvider::Action::StartVM>)> vm_configuration[:placement_policy] = { :hosts => [{ :host => 'server.test.local' }], :affinity => 'pinned' } [2] pry(#<VagrantPlugins::OVirtProvider::Action::StartVM>)> vm_configuration => {:initialization=> {:host_name=>"test", :nic_configurations=>[{:name=>"eth0", :on_boot=>true, :boot_protocol=>"static", :ip=>{:version=>"v4", :address=>"192.168.2.200", :gateway=>"192.168.2.1"}}], :custom_script=> "write_files:\n - content: |\n wat\n path: /tmp/something.txt\n permissions: '0644'\nnetwork-interfaces: |\n auto eth0\n iface eth0 inet static\n address 192.168.2.201\n network 192.168.2.0\n netmask 255.255.255.0\n gateway 192.168.2.1\n dns-nameservers 192.168.2.113 192.168.2.1\n"}, :placement_policy=>{:hosts=>[{:host=>"server.test.local"}], :affinity=>"pinned"}} ==> default: An error occured. Recovering.. ==> default: Halting VM... ==> default: Waiting for VM to shutdown... ==> default: Removing VM... /home/myoung/.rvm/gems/ruby-2.2.3/gems/ovirt-engine-sdk-4.1.2/lib/ovirtsdk4/service.rb:52:in `raise_error': Fault reason is "Incomplete parameters". Fault detail is "Host [id|name] required for validateAndUpdateHostsInPlacementPolicy". HTTP response code is 400. (OvirtSDK4::Error) The same goes with giving an object instead of a hash object => 68: machine.start( 69: use_cloud_init: true, 70: vm: vm_configuration 71: ) 72: 73: @app.call(env) [1] pry(#<VagrantPlugins::OVirtProvider::Action::StartVM>)> hosts_service = env[:connection].system_service.hosts_service [2] pry(#<VagrantPlugins::OVirtProvider::Action::StartVM>)> host = hosts_service.list(search: 'name=server.test.local')[0] [3] pry(#<VagrantPlugins::OVirtProvider::Action::StartVM>)> host.status => "up" [4] pry(#<VagrantPlugins::OVirtProvider::Action::StartVM>)> vm_configuration[:placement_policy] = { :hosts => [{ :host => host }]} ==> default: An error occured. Recovering.. ==> default: Halting VM... ==> default: Waiting for VM to shutdown... ==> default: Removing VM... /home/myoung/.rvm/gems/ruby-2.2.3/gems/ovirt-engine-sdk-4.1.2/lib/ovirtsdk4/service.rb:52:in `raise_error': Fault reason is "Incomplete parameters". Fault detail is "Host [id|name] required for validateAndUpdateHostsInPlacementPolicy". HTTP response code is 400. (OvirtSDK4::Error) from /home/myoung/.rvm/gems/ruby-2.2.3/gems/ovirt-engine-sdk-4.1.2/lib/ovirtsdk4/service.rb:85:in `check_action' from /home/myoung/.rvm/gems/ruby-2.2.3/gems/ovirt-engine-sdk-4.1.2/lib/ovirtsdk4/services.rb:29460:in `start'

2 1

DataCenter, Quota, Threshold
by Tony Wang 16 Feb '17

16 Feb '17

Hi, I have a question about the Quota of DataCenter. I 'Add' Quota, and set the threshold to 0% is failed, because the AddQuotaCommand will set to the default value 80% when the threshold is 0%. But, when I 'Edit' this Quota, I can set the threshold to 0%. Set the threshold to 0%, the 'Add' and 'Edit' operation gets different results. The operation step: https://bugzilla.redhat.com/show_bug.cgi?id=1422922 Thanks.

1 0

[Announcement] new manual job for ost
by Daniel Belenky 16 Feb '17

16 Feb '17

Hi all, The oVirt infra team is proud to announce the *new manual job for ovirt-system-tests.* Link: http://jenkins.ovirt.org/job/ovirt-system-tests_manual/ The new job supports a new feature: testing oVirt upgrades! The job can test upgrading current oVirt release from a previous release with various options, see table below for full available testing matrix. The new upgrade jobs will be soon added to the experimental flow and will be part of the gating done to oVirt tested repo ( i.e any rpm which breaks upgrade won't reach the tested repo ). *How to use?* - In order to use the manual ost job, you first have to build RPMs from your open patches. Just add a comment to your open patch and write *'ci please build', *and you'll get a link to the job that builds your patch. - Go to the manual job, and click '*Build with parameters'*. - Choose the oVirt version you wish to test (should match to the oVirt version of your patch). - Choose the suite type from the drop-down menu. The Available options are: - *Basic* - *Upgrade from release* - *Upgrade from prev release* versionprevreleaserelease master 4.0 4.1 4.1 4.0 4.1 4.0 ---- 4.0 - Add your custom URLs: here you should supply the link to the Jenkins job that built your patch. - Choose the fallback repo: This is the repo that the Job will fetch the RPMs from. Your RPMs will be used on top of those RPMs. - Choose Lago version: (Unless you want to test Lago's new features, just use the table version) - Click on *Build*, and let the job run. You'll get all the relevant logs from the suites under the '*Build artifacts*' directory when the job is done. For more detailed review of using the manual job, please refer to Verifying an oVirt patch with ovirt-system-tests <http://ovirt-system-tests.readthedocs.io/en/latest/docs/CI/developers_info.…> . Please feel free to contact the infra team on infra(a)ovirt.org for any more questions you have. Sincerely, *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

2 1

Bugs in modified state for 4.1.1
by Sandro Bonazzola 16 Feb '17

16 Feb '17

Hi, we have currently 57 bugs on modified which are not referenced within today oVirt 4.1.1 test compose according to: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… Please go over them and set target-release to the build containing the fix. If the build has not been done yet, please do. If the build exists and it has not been yet added to test compose, please do. If everything has been already built and added to test compose, please also move the bug to ON_QA. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Update on Domain XML created by the engine
by Arik Hadas 16 Feb '17

16 Feb '17

Hi All, Yesterday we merged the class LibvirtVmXmlBuilder in ovirt-engine. It does not include the conversion of all the previously supported VM properties (e.g., payload devices, OVS stuff, cinder disks - any help would be appreciated btw) or covers all flows (e.g., run once) yet and there is surely a place for improvement, but in its current state LibvirtVmXmlBuilder is able to generate a libvirt's domxml on the engine side for many typical VMs in our development environment. If you happen to start working on a change that involves changing something in the domxml, please do it by modifying this class. Our plan is to deprecate the VM info map/dictionary soon. Let me try to motivate you by example: Let's say that you want to add support for a property of a disk called 'discard'. In 4.1: You had to patch VmInfoBuilderImpl to add another element to the VM info map and then modify VDSM to use it when encoding the Disk device into XML. Now: You need to patch LibvirtVmXmlBuilder so the 'discard' property would be set on the disk device element in the generated XML. In order to test such a change you can: (1) apply [1] to send the XML generated by the engine to VDSM (2) apply [2] to send the XML generated by the engine to libvirt [1] https://gerrit.ovirt.org/#/c/71088/ [2] https://gerrit.ovirt.org/#/c/65182/ Regards, Arik

2 1

VM, Stateless
by Tony Wang 15 Feb '17

15 Feb '17

Hi, I have some questions with following operations: Start a VM with "Stateless", then, edit this VM (is running) cancel the "Stateless", popup the "Change that require Virtual Machine restart" view, save all the operations. Restart this VM which still is Stateless. It is reasonable?

2 1

[ OST Failure Report ] [ ovirt master ] [ 14.02.17 ] [storage]
by Dusan Fodor 14 Feb '17

14 Feb '17

Hi, storage task manager returns following error (vdsm.log): 2017-02-14 06:58:27,975-0500 ERROR (jsonrpc/1) [storage.TaskManager.Task] (Task='1bc5b2ca-a44e-4794-81f9-d2415f27ad48') Unexpected error (task:871) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 878, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2215, in getAllTasksInfo allTasksInfo = self._pool.getAllTasksInfo() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state 2017-02-14 06:58:27,977-0500 INFO (jsonrpc/1) [storage.TaskManager.Task] (Task='1bc5b2ca-a44e-4794-81f9-d2415f27ad48') aborting: Task is aborted: u'Secured object is not in safe state' - code 100 (task:1176) 2017-02-14 06:58:27,978-0500 ERROR (jsonrpc/1) [storage.Dispatcher] Secured object is not in safe state (dispatcher:80) Traceback (most recent call last): File "/usr/share/vdsm/storage/dispatcher.py", line 72, in wrapper result = ctask.prepare(func, *args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 106, in wrapper return m(self, *a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1184, in prepare raise self.error SecureError: Secured object is not in safe state It doesn't make OST fail, but i believe it is not desired. Sadly, I'm not able to find patch that might be related, since all builds in history have this error. Link to build: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… Link to vdsm.log: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…

2 1

[ OST Failure Report ] [ oVirt master ] [ 14.02.17 ] [vm_run]
by Dusan Fodor 14 Feb '17

14 Feb '17

Hi, vm_run fails with following error: 12:01:21 [basic_suit_el7] # vm_run: 12:04:27 [basic_suit_el7] * Collect artifacts: 12:04:27 [basic_suit_el7] * Collect artifacts: ERROR (in 0:00:01) 12:04:27 [basic_suit_el7] # vm_run: ERROR (in 0:03:05) 12:04:27 [basic_suit_el7] # snapshots_merge: 12:08:35 [basic_suit_el7] Error while running thread 12:08:35 [basic_suit_el7] Traceback (most recent call last): 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 56, in _ret_via_queue 12:08:35 [basic_suit_el7] queue.put({'return': func()}) 12:08:35 [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 427, in snapshot_live_merge 12:08:35 [basic_suit_el7] lambda: api.vms.get(VM0_NAME).status.state == 'up' 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 260, in assert_true_within_short 12:08:35 [basic_suit_el7] assert_equals_within_short(func, True, allowed_exceptions) 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 244, in assert_equals_within_short 12:08:35 [basic_suit_el7] func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 230, in assert_equals_within 12:08:35 [basic_suit_el7] '%s != %s after %s seconds' % (res, value, timeout) 12:08:35 [basic_suit_el7] AssertionError: False != True after 180 seconds 12:08:35 [basic_suit_el7] * Collect artifacts: 12:08:36 [basic_suit_el7] * Collect artifacts: ERROR (in 0:00:02) 12:08:36 [basic_suit_el7] # snapshots_merge: ERROR (in 0:04:10) 12:08:36 [basic_suit_el7] # suspend_resume_vm: 12:08:36 [basic_suit_el7] * Collect artifacts: Link to job: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… Link to first failed build: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… Link to change with possible cause: https://gerrit.ovirt.org/#/c/71633/

4 4

[ OST Failure Report ] [ rhv master ] [ 14.02.17 ] [vm_run]
by Dusan Fodor 14 Feb '17

14 Feb '17

Hi, vm_run fails with following error: 12:01:21 [basic_suit_el7] # vm_run: 12:04:27 [basic_suit_el7] * Collect artifacts: 12:04:27 [basic_suit_el7] * Collect artifacts: ERROR (in 0:00:01) 12:04:27 [basic_suit_el7] # vm_run: ERROR (in 0:03:05) 12:04:27 [basic_suit_el7] # snapshots_merge: 12:08:35 [basic_suit_el7] Error while running thread 12:08:35 [basic_suit_el7] Traceback (most recent call last): 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 56, in _ret_via_queue 12:08:35 [basic_suit_el7] queue.put({'return': func()}) 12:08:35 [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 427, in snapshot_live_merge 12:08:35 [basic_suit_el7] lambda: api.vms.get(VM0_NAME).status.state == 'up' 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 260, in assert_true_within_short 12:08:35 [basic_suit_el7] assert_equals_within_short(func, True, allowed_exceptions) 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 244, in assert_equals_within_short 12:08:35 [basic_suit_el7] func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 230, in assert_equals_within 12:08:35 [basic_suit_el7] '%s != %s after %s seconds' % (res, value, timeout) 12:08:35 [basic_suit_el7] AssertionError: False != True after 180 seconds 12:08:35 [basic_suit_el7] * Collect artifacts: 12:08:36 [basic_suit_el7] * Collect artifacts: ERROR (in 0:00:02) 12:08:36 [basic_suit_el7] # snapshots_merge: ERROR (in 0:04:10) 12:08:36 [basic_suit_el7] # suspend_resume_vm: 12:08:36 [basic_suit_el7] * Collect artifacts: 12:08:38 [basic_suit_el7] * Collect artifacts: ERROR (in 0:00:01) 12:08:38 [basic_suit_el7] # suspend_resume_vm: ERROR (in 0:00:02) Link to job: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…

1 0

Failing CI jobs on FC24
by Barak Korren 13 Feb '17

13 Feb '17

Our Fedora 24 updates mirror got currupted. This is currently causing all FC24 jobs to fail. We are working on fixing that but it'll take a while until we finish re-syncing all the 14293 packages the repo needs to contain. For more details pealse see: https://ovirt-jira.atlassian.net/browse/OVIRT-1141 Please be patient, Thanks, -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

2 2

Updated Invitation: DeepDive: SPDM shared storage management (infrastructure/... @ Wed Feb 22, 2017 6pm - 7pm (IST) (devel@ovirt.org)
by laravot＠redhat.com 13 Feb '17

13 Feb '17

This event has been changed. Title: DeepDive: SPDM shared storage management (infrastructure/copy scale out/progress reporting) When: Wed Feb 22, 2017 6pm – 7pm Jerusalem (changed) Where: https://redhat.bluejeans.com/laravot Calendar: devel(a)ovirt.org Who: * laravot(a)redhat.com - organizer * devel(a)ovirt.org * users(a)ovirt.org * rhevm-qe-dept Event details: https://www.google.com/calendar/event?action=VIEW&eid=Ym9kazZyZHVjbjdjZzl2c… 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

Request to pull Italian translation for Master
by Gianluca Cecchi 11 Feb '17

11 Feb '17

Hello, I have completed 100% of all parts except ApplicationConstants one, on which I'm going to work during next weeks. In the mean time I ask if it is possible to commit the current situation so that upcoming oVirt 4.1 reflects it. Thanks in advance, Gianluca

3 5

trying to run ovirt wiki locally
by Tomas Jelinek 10 Feb '17

10 Feb '17

Hi all, so when doing something on the ovirt wiki I have found a slight imperfection in the admin guide: http://www.ovirt.org/documentation/admin-guide/ So I decided to fix it but to verify it I wanted to run the page locally but failed miserably. Spent some time trying to make it run but it seems I will need some help. I'm running Fedora 25. So, first tried to use the non docker setup. The setup passed but when running run-server.sh it first were complaining that: bundler: command not found: middleman even though the middleman is installed: $ bundle show middleman /home/tjelinek/.gem/ruby/gems/middleman-3.3.12 when set the path explicitly to point to it: $ export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/tjelinek/.gem/ruby/gems/middleman-core-3.3.12/bin I've got: bundler: failed to load command: middleman (/home/tjelinek/.gem/ruby/gems/middleman-core-3.3.12/bin/middleman) LoadError: libruby.so.2.0: cannot open shared object file: No such file or directory - /home/tjelinek/.gem/ruby/gems/http_parser.rb-0.6.0/lib/ruby_http_parser.so even the file is there: ls /home/tjelinek/.gem/ruby/gems/http_parser.rb-0.6.0/lib/ruby_http_parser.so /home/tjelinek/.gem/ruby/gems/http_parser.rb-0.6.0/lib/ruby_http_parser.so So I gave up and tied the docker setup. The docker-setup.sh passed without any problems. Now the docker-run: first of all it needs selinux disbaled otherwise it fails on: panic: standard_init_linux.go:178: exec user process caused "permission denied" [recovered] panic: standard_init_linux.go:178: exec user process caused "permission denied" And with selinux disabled I get: Running docker image springboard-20170210-28960 /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- active_support (LoadError) from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from fetch-dashboard.rb:12:in `<main>' An error occurred while installing nokogiri (1.7.0.1), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.7.0.1'` succeeds before bundling. And there I have stopped. Does it work to anyone? What needs to be done? Thank you, Tomas

3 2

planned Jenkins restart
by Evgheni Dereveanchin 10 Feb '17

10 Feb '17

Hi everyone, I'll be performing a planned Jenkins restart today. No new builds will be scheduled during this maintenance period. I will announce you once it is finished. Regards, Evgheni Dereveanchin

1 1

Jenkins jobs ownership
by Sandro Bonazzola 10 Feb '17

10 Feb '17

Hi, I'm taking a discussion starting in gerrit to the mailing lists for broader audience discussion. In https://gerrit.ovirt.org/69268 it has been asked: 8<--------------------------------------------------------- Sandro, can someone from you team fix this? It does not make sense that ovirt-imageio maintainers will babysit this code base. This must be the responsibility of your team. We have separate projects for this; we maintain ovirt-imageio, your team maintain the jenkins project. If you want us to maintain this, this code must move into ovirt-imageio repository, so we have full control of it. ---------------------------------------------------->8 So I'd like to make clear a couple of things. Integration team is not committing to maintain the hundreds of jenkins jobs currently existing alone. Integration team is also not committing monitoring them. integration team is not maintaining Jenkins project. Jenkins project is used by developers who need their tests and builds to be executed in Jenkins. you're free to run your tests wherever you feel more comfortable and build packages in your preferred build service (copr, koji, openbuild, Jenkins, centos cbs,...) provided that on release day the source code is correctly tagged in gerrit and tarball available on resources.ovirt.org. If the rpms are not available within CentOS Virt SIG and Fedora main repository or in a copr repository referenced by ovirt-release rpm, you're also required to provide rpms and src.rpms to be published within oVirt yum repository. As release engineering manager, I try to fix Jenkins issues whenever I can for those jobs which are needed to get the release built and published so in this specific case, I will probably end up with taking over the patch and get it to merged state just because fc23 is EOL and as release engineering we don't want fc23 packages being shipped anymore. If you want to use Jenkins, you're allowed to. oVirt infra team is maintaining the Jenkins server infrastructure and the Standard CI framework to make it easier to write tests and build scripts. If you need help on that area, please open a ticket on infra-support(a)ovirt.org. I'm here for any further question or open discussion. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 14

OST: vm_run fails for me (basic-suite-master)
by Ondrej Svoboda 10 Feb '17

10 Feb '17

Hi everyone, Even though I have nested virtualization enabled in my Arch Linux system which I use to run OST, vm_run is the first test to fail in 004_basic_sanity (followed by snapshots_merge and suspend_resume_vm). Can you point me to what I might be missing? I believe I get the same failure even on Fedora. This is what host0's CPU capabilities look like (vmx is there): [root@lago-basic-suite-master-host0 ~]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Westmere E56xx/L56xx/X56xx (Nehalem-C) stepping : 1 microcode : 0x1 cpu MHz : 2711.988 cache size : 16384 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm constant_tsc rep_good nopl xtopology pni pclmulqdq vmx ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm arat tpr_shadow vnmi flexpriority ept vpid bogomips : 5423.97 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: journalctl -b on host0 shows that libvirt complains about NUMA configuration: Feb 07 06:33:23 lago-basic-suite-master-host0 libvirtd[12888]: libvirt version: 2.0.0, package: 10.el7_3.4 (CentOS BuildSystem < http://bugs.centos.org>, 2017-01-17-23:37:48, c1bm.rdu2.centos.org) Feb 07 06:33:23 lago-basic-suite-master-host0 kernel: ovirtmgmt: port 2(vnet0) entered disabled state Feb 07 06:33:23 lago-basic-suite-master-host0 kernel: device vnet0 left promiscuous mode Feb 07 06:33:23 lago-basic-suite-master-host0 kernel: ovirtmgmt: port 2(vnet0) entered disabled state Feb 07 06:33:23 lago-basic-suite-master-host0 libvirtd[12888]: hostname: lago-basic-suite-master-host0.lago.local Feb 07 06:33:23 lago-basic-suite-master-host0 libvirtd[12888]: Unable to read from monitor: Connection reset by peer Feb 07 06:33:23 lago-basic-suite-master-host0 libvirtd[12888]: internal error: qemu unexpectedly closed the monitor: 2017-02-07T11:33:23.058571Z qemu-kvm: warning: CPU(s) not present in any NUMA nodes: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 2017-02-07T11:33:23.058826Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config qemu-kvm: /builddir/build/BUILD/qemu-2.6.0/target-i386/kvm.c:1736: kvm_put_msrs: Assertion `ret == n' failed. Feb 07 06:33:23 lago-basic-suite-master-host0 NetworkManager[657]: <info> [1486467203.1025] device (vnet0): state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3] Feb 07 06:33:23 lago-basic-suite-master-host0 kvm[22059]: 0 guests now active Feb 07 06:33:23 lago-basic-suite-master-host0 systemd-machined[22044]: Machine qemu-1-vm0 terminated. Thanks, Ondra

4 10

[ANN] oVirt 4.1.1 Test compose
by Sandro Bonazzola 09 Feb '17

09 Feb '17

The oVirt Project is pleased to announce the availability of the First Test Compose of oVirt 4.1.1 for testing, as of February 9th, 2017 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is a test compose allowing to test fixes included in ovirt-4.1.1 since 4.1.0 release. See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 24 (tech preview) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Live, oVirt Node and oVirt Engine appliance has not been built for this test compose Additional Resources: * Read more about the oVirt 4.1.1 release highlights: http://www.ovirt.org/release/4.1.1/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.1/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Google Summer of Code: Call for Projects
by Brian Proffitt 09 Feb '17

09 Feb '17

All: Today is the deadline for the application for organizations to apply to be a part of the 2017 Google Summer of Code. The good news is, the application was completed yesterday and we are mostly set to go. Currently we have three projects listed on our project page[1], but if you have a project in mind for a student, you should send me the idea right away or edit the page directly. Use the format found for the ideas already listed on the Summer of Code page. Please note: we don't know how many student slots we will get from Google. In 2015, we were awarded two. But the more ideas we have, the more student choice there will be, and the stronger our project will look as a candidate organization. This should be done as soon as possible. While we are editing our page and not the original application, Google will review the page at any point and it might not go over well if we are adding projects after the application deadline of 1700 GMT today. I would say we should have projects added by 1700 GMT Friday, Jan. 10. They don't have to be hyper complete: just enough to get the idea across. Peace, Brian [1] HTTP://www.ovirt.org/community/activities/summer-of-code/ <http://www.ovirt.org/community/activities/summer-of-code/> -- Brian Proffitt Principal Community Analyst Open Source and Standards @TheTechScribe 574.383.9BKP

1 0

[HEADS UP] dropping fc24 support on master
by Sandro Bonazzola 09 Feb '17

09 Feb '17

Hi, I see today VDSM team dropped support for fc24 on master by getting https://gerrit.ovirt.org/#/c/71668/ merged. This will break several jenkins jobs depending on vdsm in the following days so expect failures on projects requiring vdsm (like hosted engine) on fc24. Please note that I didn't finish to complete fedora 25 jobs so for the next week or so we are without fedora support. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0