- Devel - oVirt List Archives

ovirt-engine version problem
by shubham dubey 13 Apr '17

13 Apr '17

Hello, Recently I have installed ovirt-engine development environment. The snapshot repository I have used is ovirt-release-master. Now I have installed vdsm in ovirt host with ovirt-release41, so when I am trying to add the host it is showing that ovirt node support cluster version 3.9,4.0 and 4.1 but 4.2 is available. So I have decided to installed ovirt engine with ovirt-engine41 repository. The steps I follow are :- 1) yum remove ovirt-release-master.noarch 2) yum install ovirt-release41.noarch 3) delete $HOME/ovirt-engine and $HOME/git/ovirt-engine 4) git clone ovirt-engine again 5) make install-dev PREFIX=$HOME/ovirt-engine The compiling ends successfully but the $HOME/ovirt-engine directory is coming out empty. So $HOME/ovirt-engine/bin/engine-setup is giving error that NO file or directory found. So can anyone tell me what I am doing wrong? Note:One more thing I have noticed is that even after changing repo to ovirt 4.1 the make is still compiling ovirt 4.2 snapshot. Thanks, Shubham

4 8

[OST Failure Report][oVirt master][2017-04-11] add_secondary_storage_domains
by Sandro Bonazzola 12 Apr '17

12 Apr '17

Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6303 *OST is failing in the last 50 builds* *00:18:22.090* [basic_suit_el7] # add_secondary_storage_domains: *00:18:22.090* [basic_suit_el7] Error while running thread*00:18:22.090* [basic_suit_el7] Traceback (most recent call last):*00:18:22.090* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.090* [basic_suit_el7] queue.put({'return': func()})*00:18:22.090* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 427, in add_nfs_storage_domain*00:18:22.090* [basic_suit_el7] add_generic_nfs_storage_domain(prefix, SD_NFS_NAME, SD_NFS_HOST_NAME, SD_NFS_PATH, nfs_version='v4_2')*00:18:22.091* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 441, in add_generic_nfs_storage_domain*00:18:22.091* [basic_suit_el7] add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)*00:18:22.091* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 490, in add_generic_nfs_storage_domain_4*00:18:22.091* [basic_suit_el7] host=_random_host_from_dc_4(api, DC_NAME),*00:18:22.091* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 106, in _random_host_from_dc_4*00:18:22.091* [basic_suit_el7] return random.choice(_hosts_in_dc_4(api, dc_name))*00:18:22.091* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 100, in _hosts_in_dc_4*00:18:22.091* [basic_suit_el7] raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)*00:18:22.092* [basic_suit_el7] RuntimeError: Could not find hosts that are up in DC test-dc*00:18:22.092* [basic_suit_el7] Error while running thread*00:18:22.092* [basic_suit_el7] Traceback (most recent call last):*00:18:22.092* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.092* [basic_suit_el7] queue.put({'return': func()})*00:18:22.092* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 583, in add_iso_storage_domain*00:18:22.092* [basic_suit_el7] add_generic_nfs_storage_domain(prefix, SD_ISO_NAME, SD_ISO_HOST_NAME, SD_ISO_PATH, sd_format='v1', sd_type='iso', nfs_version='v3')*00:18:22.092* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 441, in add_generic_nfs_storage_domain*00:18:22.092* [basic_suit_el7] add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)*00:18:22.093* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 490, in add_generic_nfs_storage_domain_4*00:18:22.093* [basic_suit_el7] host=_random_host_from_dc_4(api, DC_NAME),*00:18:22.093* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 106, in _random_host_from_dc_4*00:18:22.093* [basic_suit_el7] return random.choice(_hosts_in_dc_4(api, dc_name))*00:18:22.093* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 100, in _hosts_in_dc_4*00:18:22.093* [basic_suit_el7] raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)*00:18:22.093* [basic_suit_el7] RuntimeError: Could not find hosts that are up in DC test-dc*00:18:22.094* [basic_suit_el7] Error while running thread*00:18:22.094* [basic_suit_el7] Traceback (most recent call last):*00:18:22.094* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.094* [basic_suit_el7] queue.put({'return': func()})*00:18:22.094* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 587, in add_templates_storage_domain*00:18:22.094* [basic_suit_el7] add_generic_nfs_storage_domain(prefix, SD_TEMPLATES_NAME, SD_TEMPLATES_HOST_NAME, SD_TEMPLATES_PATH, sd_format='v1', sd_type='export', nfs_version='v4_1')*00:18:22.094* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 441, in add_generic_nfs_storage_domain*00:18:22.094* [basic_suit_el7] add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)*00:18:22.094* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 490, in add_generic_nfs_storage_domain_4*00:18:22.095* [basic_suit_el7] host=_random_host_from_dc_4(api, DC_NAME),*00:18:22.095* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 106, in _random_host_from_dc_4*00:18:22.095* [basic_suit_el7] return random.choice(_hosts_in_dc_4(api, dc_name))*00:18:22.095* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 100, in _hosts_in_dc_4*00:18:22.095* [basic_suit_el7] raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)*00:18:22.095* [basic_suit_el7] RuntimeError: Could not find hosts that are up in DC test-dc*00:18:22.095* [basic_suit_el7] Error while running thread*00:18:22.095* [basic_suit_el7] Traceback (most recent call last):*00:18:22.096* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.096* [basic_suit_el7] queue.put({'return': func()})*00:18:22.096* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 436, in add_second_nfs_storage_domain*00:18:22.096* [basic_suit_el7] SD_NFS_HOST_NAME, SD_SECOND_NFS_PATH)*00:18:22.096* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 441, in add_generic_nfs_storage_domain*00:18:22.096* [basic_suit_el7] add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)*00:18:22.096* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 490, in add_generic_nfs_storage_domain_4*00:18:22.096* [basic_suit_el7] host=_random_host_from_dc_4(api, DC_NAME),*00:18:22.096* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 106, in _random_host_from_dc_4*00:18:22.097* [basic_suit_el7] return random.choice(_hosts_in_dc_4(api, dc_name))*00:18:22.097* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 100, in _hosts_in_dc_4*00:18:22.097* [basic_suit_el7] raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)*00:18:22.097* [basic_suit_el7] RuntimeError: Could not find hosts that are up in DC test-dc*00:18:22.097* [basic_suit_el7] Error while running thread*00:18:22.097* [basic_suit_el7] Traceback (most recent call last):*00:18:22.097* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.098* [basic_suit_el7] queue.put({'return': func()})*00:18:22.098* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 803, in import_template_from_glance*00:18:22.098* [basic_suit_el7] generic_import_from_glance(api, image_name=CIRROS_IMAGE_NAME, image_ext='_glance_template', as_template=True)*00:18:22.098* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 637, in generic_import_from_glance*00:18:22.098* [basic_suit_el7] target_image.import_image(import_action)*00:18:22.098* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 26017, in import_image*00:18:22.098* [basic_suit_el7] headers={"Correlation-Id":correlation_id}*00:18:22.098* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request*00:18:22.098* [basic_suit_el7] persistent_auth=self.__persistent_auth*00:18:22.099* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request*00:18:22.099* [basic_suit_el7] persistent_auth)*00:18:22.099* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request*00:18:22.099* [basic_suit_el7] raise errors.RequestError(response_code, response_reason, response_body)*00:18:22.099* [basic_suit_el7] RequestError: *00:18:22.099* [basic_suit_el7] status: 400*00:18:22.099* [basic_suit_el7] reason: Bad Request*00:18:22.099* [basic_suit_el7] detail: Cannot import Virtual Disk: Storage Domain cannot be accessed.*00:18:22.099* [basic_suit_el7] -Please check that at least one Host is operational and Data Center state is up. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

7 21

vdsm-ppc64le builds is not deployed to ovirt-master-snapshot
by Sandro Bonazzola 12 Apr '17

12 Apr '17

The x86_64 job[1] has a downstream project[2] taking care of deploying the build to the repos while the ppc64le[3] hasn't. Result is that ovirt-master-snapshot is not receiving updates for ppc64le and is currently failing repository closure: *00:02:47.636* Error: Package: vdsm-gluster-4.20.0-612.git378d837.el7.centos.noarch (ovirt-master-snapshot)*00:02:47.637* Requires: vdsm = 4.20.0-612.git378d837.el7.centos*00:02:47.637* Installing: vdsm-4.18.999-925.git195c44e.el7.centos.ppc64le (ovirt-master-snapshot)*00:02:47.637* vdsm = 4.18.999-925.git195c44e.el7.centos*00:02:47.637* Error: Package: vdsm-hook-ethtool-options-4.20.0-612.git378d837.el7.centos.noarch (ovirt-master-snapshot)*00:02:47.637* Requires: vdsm = 4.20.0-612.git378d837.el7.centos*00:02:47.637* Installing: vdsm-4.18.999-925.git195c44e.el7.centos.ppc64le (ovirt-master-snapshot)*00:02:47.637* vdsm = 4.18.999-925.git195c44e.el7.centos Please fix vdsm job for triggering deploy-to-ovirt_experimental_master [1] http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/ [2] http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/ [3] http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

planned Jenkins restart
by Evgheni Dereveanchin 11 Apr '17

11 Apr '17

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new builds will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1

Failed to execute stage 'Misc configuration': Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute
by Sandro Bonazzola 11 Apr '17

11 Apr '17

engine-setup: 2017-04-11 09:43:29,659-0400 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 384, in _misc self._setupAdminUser() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 284, in _setupAdminUser name=adminUser, File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 64, in _userExists envAppend=toolEnv, File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in execute command=args[0], RuntimeError: Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute /usr/bin/ovirt-aaa-jdbc-tool: 2017-04-11 09:43:29,659-0400 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.config.aaajdbc plugin.execute:926 execute-output: ('/usr/bin/ovirt-aaa-jdbc-tool', '--db-config=/etc/ovirt-engine/aaa/internal.pro perties', 'query', '--what=user', '--pattern=name=admin') stderr: Exception in thread "main" org.jboss.modules.ModuleLoadError: Error loading module from /usr/share/ovirt-engine/modules/tools/org/slf4j/main/module.xml at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74) at org.jboss.modules.Module.getPathsUnchecked(Module.java:1435) at org.jboss.modules.Module.loadModuleClass(Module.java:601) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) at org.ovirt.engine.extension.aaa.jdbc.binding.cli.Cli.<clinit>(Cli.java:87) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.jboss.modules.Module.run(Module.java:320) at org.jboss.modules.Main.main(Main.java:505) Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'slf4j-jdk14.jar' at path 'slf4j-jdk14.jar' (position: END_TAG seen ...path="slf4j-api.jar"/>\n <resource-root path="slf4j- jdk14.jar"/>... @11:44) caused by: java.io.FileNotFoundException: /usr/share/ovirt-engine/modules/tools/org/slf4j/main/slf4j-jdk14.jar (File o directory non esistente) at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:891) at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:735) at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:535) at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:340) at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:226) at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:204) at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:170) at org.jboss.modules.LocalModuleFinder.lambda$findModule$0(LocalModuleFinder.java:149) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) at org.jboss.modules.Module.addPaths(Module.java:1079) at org.jboss.modules.Module.link(Module.java:1449) at org.jboss.modules.Module.getPaths(Module.java:1410) at org.jboss.modules.Module.getPathsUnchecked(Module.java:1433) ... 10 more # rpm -qf /usr/bin/ovirt-aaa-jdbc-tool ovirt-engine-extension-aaa-jdbc-1.1.5-0.0.master.git2a03d42.el7.centos.noarch # rpm -qv ovirt-engine ovirt-engine-4.2.0-0.0.master.20170408115943.gitea6bd62.el7.centos.noarch -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 3

[ OST Failure Report ] [ oVirt master ] [ 9/4/2017 ] [ add_secondary_storage_domains ]
by Barak Korren 10 Apr '17

10 Apr '17

Test failed: [ add_secondary_storage_domains ] Link to suspected patches: - https://gerrit.ovirt.org/#/c/74779/ Link to Job: - http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6257/ Link to all logs: - http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6257/artif… Error snippet from log: <error> detail: Cannot import Virtual Disk: Storage Domain cannot be accessed. -Please check that at least one Host is operational and Data Center state is up. ... AssertionError: False != True after 600 seconds </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

6 9

oVirt repositories 101; or everything you wanted to know about oVirt repositories and didn't ask
by Eyal Edri 09 Apr '17

09 Apr '17

Hi oVirt developers and users, Some of you might be familiar with the oVirt repositories and all their flavors, while some of you are just familiar with the official releases. The fact is, we have plenty of them and each has its own role and a right usage. Moreover, we did a significant overhaul on all the repositories in the past months, So hopefully now it will be easier to explain which repo to use when. I'll start with reviewing each oVirt repository and give a bit of background and the logic behind it, how to consume it and the relevant usage for it. For simplicity, I'll review the repositories on the 4.1 release, but it valid for all other oVirt releases ( except 'master' which doesn't have an official or pre-release repositories ). I will also upload this information to the oVirt.org site, but since this is important, I didn't want to wait with the sending this email. *oVirt repositories* *Official repositories* *Desc:* here you can find the official signed oVirt RPMs, immediately after an official release has been done. *Path:* http://resources.ovirt.org/pub/ovirt-4.1/rpm/$distro *Update frequency:* on every oVirt release, usually happens on a monthly cadence. *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm *Who should use it? * oVirt users, developers or anyone who wants a final and official release *Pre-release repositories* *Desc:* here you can find the pre-release bits of oVirt RC builds, just before they are released. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/$distro *Update frequency:* usually on a weekly or bi-weekly basis *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-pre.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt new version before its out, Keeping in mind this isn't a fully verified release and might still have critical bugs which are not fixed yet. Packages in this repo are verified by automation and checked by humans for basic sanity before publishing. *Nightly snapshot (verified) repositories* *Desc:* here you can find the nightly snapshot of RPMs, which passed basic sanity by our 'oVirt System Tests' framework in the oVirt CI system. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/$distro *Update frequency:* Every night *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-snapshot.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt latest bits right of the build oven! We trust our system tests, which already run more than 40 various tests such as 'add host', 'create VM', 'live migration' and more! *** Important note: the snapshot repositories are verified only in master currently, we might do the same for 4.1 soon, as we see no issues with master so far ** * *The above repos should suffice to most usres and developers, but if you feel its not enough and you still need a faster verified repo, look below! * *Advanced oVirt repositories* *Builds artifacts repo* *Desc:* This is a new feature from oVirt 'standard CI' project, where each 'build-artifacts' job is actually a yum repo as well. *Path:* http://jenkins.ovirt.org/job/ovirt-engine_4.1_ build-artifacts-on-demand-el7-x86_64/lastSuccessfulBuild/ artifact/exported-artifacts ( example ) *Update frequency:* after each commit or 'ci please build' comment *Release rpm: *N/A *Who should use it? * oVirt developers who need latest RPMs from another oVirt project and cannot or need not wait for that project`s packages to pass OST". oVirt developers running manual OST job and need to test an open Gerrit patch, using the 'ci please build' command. *Tested repositories* *Desc:* The tested repositories hold all the oVIrt packages which passed CI ( similar to snapshot repos ) and retain also version history for X versions back. *Path:* http://resources.ovirt.org/repos/ovirt/tested/4.1/rpm/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * If you want to have latest and greatest oVirt packages and can't wait for the nightly repo. If you are testing upgrades or need more than one version of a pacakge in your repo. *Experimental repositories * *Desc:* Internal CI repos which are a part of the 'experimental' flow which runs OST on each built package. *Path:* http://resources.ovirt.org/repos/ovirt/experimental/ 4.1/latest.tested/rpm/el7/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * *No one other than internal CI jobs.* These repos are constantly refreshed and RPMs are being removed from them, so they are very prone to errors, please don't use them. I hope this makes a bit of order in all the repos and how to use them. If you still have questions, please don't hesitate to contact the infra team at infra(a)ovirt.org or just reply to this thread. -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

ovirt-engine dependencies and packaging plans for 4.2
by Sandro Bonazzola 08 Apr '17

08 Apr '17

In https://bugzilla.redhat.com/show_bug.cgi?id=1439518 I'm suggesting a packaging change for ovirt-engine allowing to reduce the space needed to install a minimal ovirt-engine. Martin says: We should get rid of PostgreSQL RPM dependency when we move to SCL version of PG9.5/9.6, which is planned fo 4.2 Do we have a bz to track it? How engine-setup can upgrade from a non-scl to a scl postgres setup? Who's going to handle it? Following up from https://bugzilla.redhat.com/show_bug.cgi?id=1439518#c1 Do we have plans to split userportal/backend to their own containers at some point? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 2

[OST] [HC] HE VM fails to start
by Sahina Bose 06 Apr '17

06 Apr '17

The error in vdsm.log Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 2016, in _setup_devices dev_object.setup() File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/graphics.py", line 63, in setup net_api.create_libvirt_network(display_network, self.conf['vmId']) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 90, in create_libvirt_network libvirt.create_network(netname, user_reference) File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py", line 94, in create_network if not is_libvirt_network(netname): File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py", line 159, in is_libvirt_network netname = LIBVIRT_NET_PREFIX + netname TypeError: cannot concatenate 'str' and 'NoneType' objects 2017-03-29 22:58:39,559-0400 ERROR (vm/d71bdf4e) [virt.vm] (vmId='d71bdf4e-1eb3-4762-bd0e-05bb9f5e43ef') The vm start process failed (vm:659) The tests last passed on Mar 28. Did a recent patch break this? The full build logs at http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/52/artifact/expor… thanks sahina

4 12

Firewalld migration.
by Leon Goldberg 06 Apr '17

06 Apr '17

Hey, We're looking to migrate from iptables to firewalld. We came up with a couple of possible approaches we'd like opinions on. I'll list the options first, and will 1) Replicate existing flow: As of date, iptable rules are inserted in the database via SQL config files. During host deployment, VdsDeployIptablesUnit adds the required rules (based on cluster/firewall configuration) to the deployment configuration, en route to being deployed on the host via otopi and its iptables plugin. Pros: - Reuse of existing infrastructure. Cons: - Current infrastructure is overly complex... - Many of the required services are provided by firewalld. Rewriting them is wasteful; specifying them (instead of providing actual service .xml content) will require adaptations on both (engine/host) sides. More on that later. 2) Host side based configuration: Essentially, all the required logic (aforementioned cluster/firewall configuration) to determine if/how firewalld should be deployed could be passed on to the host via ohd. Vdsm could take on the responsibility of examining the relevant configuration, and then creating and/or adding the required services (using vdsm.conf and vdsm-tool). Pros: - Engine side involvement is greatly diminished. - Simple(r). Cons: - Custom services/rules capabilities will have to be rethought and re-implemented (current infrastructure supports custom iptables rules by being specified in the SQL config file). 3) Some other hybrid approach: If we're able to guarantee all the required firewalld services are statically provided one way or the other, the current procedure could be replicated and be made more simpler. Instead of providing xml content in the form of strings, service names could be supplied. The responsibility of actual service deployment becomes easier, and could be left to otopi (with the appropriate modifications) or switched over to vdsm. -- Regardless, usage of statically provided vs. dynamically created services remains an open question. I think we'd like to avoid implementing logic that ask whether some service is provided (and then write it if it isn't...), and so choosing between the dynamic and static approaches is also needed. Using the static approach, guaranteeing *all* services are provided will be required. I do believe guaranteeing the presence of all required services is worth it, however custom services aren't going to be naively compatible, and we'll still have to use similar mechanism as described in #1 (service string -> .xml -> addition of service name to active zone). Your thoughts are welcome. Thanks, Leon

10 37