- Devel - oVirt List Archives

[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