June 2016 - Devel - oVirt List Archives

DRBD Integration with oVirt
by Hayley Swimelar 26 Jul '16

26 Jul '16

Hello all, A DRBD integration into oVirt is currently being planned. DRBD provides replicated, highly available block storage. For those unfamiliar with DRBD more information can be found here: https://www.drbd.org/en/comp/drbd-linux-driver DRBD 9 is the latest version of DRBD and interacts with DRBD Manage which is a daemon exposed via a D-Bus api. More information can be found here: https://www.drbd.org/en/comp/drbdmanage DRBD Manage handles the creation, assignment, etc. of DRBD volumes and is the interface through which Cinder manages DRBD. We are looking for advice on how best to have oVirt communicate with DRBD Manage and we have come to two options: 1) Use Cinder. Although we are integrated into Cinder, there are concerns about the need to set up a complete Cinder instance to provide access to DRBD. 2) The alternative to Cinder would be to have the oVirt Engine communicate directly to DRBD Manage via D-Bus. Any advice on the best way to achieve this would be much appreciated. -- Hayley Swimelar LINBIT | Keeping the Digital World Running DRBD — Corosync — Pacemaker +1-503-573-1262 x212

5 11

How to build and install oVirt on Product Environment
by Dewey Du 25 Jul '16

25 Jul '16

To build and install ovirt-engine execute the folllowing command: $ make clean install-dev PREFIX="${PREFIX}" What about installing it on Product Environment. Is the folllowing command right? $ make clean install PREFIX="${PREFIX}"

2 1

Integration tests future (and very nice alternative for the DAO fixture file)
by Roman Mohr 04 Jul '16

04 Jul '16

Hi all, In [1] you can find some patches which are meant to improve the test writing experience in ovirt-engine. They provide the following things: A) Domain Object builders which can be used for creating and/or persisting domain objects [2] B) DAO testing without writing fixtures because of the builders C) Integration testing for commands in conjunction with a real database Arquillian, injectable commands and the builders [3] # How to run what? A) In normal unit tests just create a new instance of a builder and use it. This should help us to get rid of all the small createDefaultVm(), createHostWithX() helper methods in our tests. B) In dao tests just inject them and go ahead. The advantage of not using the fixture file is that we can now set up clean scenarios for every test in a setup method. See example 2 below on how easy it is to set up a new cluster. C) Arquillian integration tests need to be marked with "@Category(IntegrationTest.class)" and can inherit from TransactionalTestBase. The @Category annotation makes sure that the integration tests are only run when mvn clean verify -DskipITs=false is invoked. Note that these tests are then executed in the integration test phase of maven. For them we use the maven-failsafe-plugin[5] which will also make sure that the testing database is up to date. See [4] for more details. # Examples 1) Add a running VM to a host, persist everything to the database and load all VMs which are running on the host: VDS host = vdsBuilder.cluster(persistedCluster).persist(); vmBuilder.host(host).up().persist(); List<VM> vms = vmDao.getAllRunningForVds(host.getId()); 2) Add 10 hosts with 1 GB of RAM to a cluster, persist the hosts to the database in a DAO test: public class MyHostDaoTest extends BaseDaoTestCase { @Inject private VdsBuilder vdsBuilder; @Test public void createHosts() { VdsBuilder builder = vdsBuilder.cluster(persistedCluster).physicalMemory(1000); for (int x =0; x < 10; x++){ builder.id(Guid.newGuid()).persist(); } } } 3) Full integration test with arquillian and the database @Category(IntegrationTest.class) public class VmDaoIntegrationTest extends TransactionalTestBase { @Inject VmDao vmDao; private final Guid VM1_GUID = Guid.createGuidFromString("0fe4bc81-5999-4ab6-80f8-7a4a2d4bfacd"); @Deployment public static JavaArchive deploy(){ return createDeployment(); } @Test public void shouldFailOnExistingEntity() { vmBuilder.id(VM1_GUID).cluster(clusterBuilder.reset().persist()).persist(); // This uses assertThat from assertj: assertThat(vmDao.get(VM1_GUID)).isNotNull(); } } 4) Using the builders in a normal unit test without a database: VM vm = new VmBuilder().id(Guid.newGuid()).up().build(); # How to add your own Domain objects? There are just a few simple rules: 1) Your builder should extend org.ovirt.engine.core.builder.AbstractBuilder 2) Make sure that you only access DAOs injected into the builder during #prePersist() and #persist(). This allows to use the #build() method also without injections 3) #prePersist() should set all fields which are necessary to suffice database constraints. The fields should only be set if they are not already set before by the builder. When following this rule we can always persist new objects to the database by simply calling myBuilder.reset().persist(). 4) Mark your builder with @Repository to make them useable for our Spring DAO tests and our Arquillian integration tests. So have a look at the patches at [1] and let me know what you think about them. Best Regards and happy testing, Roman [1] https://gerrit.ovirt.org/#/q/topic:integration [2] https://gerrit.ovirt.org/#/c/47008/17 [3] https://gerrit.ovirt.org/#/c/47007/10 [4] https://gerrit.ovirt.org/#/c/47008/17 [5] https://maven.apache.org/surefire/maven-failsafe-plugin/

5 7

ovirt tests failing on missing libxml2-python
by Eyal Edri 04 Jul '16

04 Jul '16

2016-06-24 17:28:17,843 DEBUG [org.ovirt.otopi.dialog.MachineDialogParser] (VdsDeploy) [796140d9] Got: ***L:ERROR Failed to execute stage 'Package installation': [u'libxml2-python-2.9.1-6.el7_2.3.x86_64 requires libxml2 = 2.9.1-6.el7_2.3'] 2016-06-24 17:28:17,844 DEBUG [org.ovirt.otopi.dialog.MachineDialogParser] (VdsDeploy) [796140d9] nextEvent: Log ERROR Failed to execute stage 'Package installation': [u'libxml2-python-2.9.1-6.el7_2.3.x86_64 requires libxml2 = 2.9.1-6.el7_2.3'] 2016-06-24 17:28:17,860 ERROR This is failing 3.6,4.0 and master tests, anyone knows on a recent dependency change in vdsm or other host level pkg? -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 9

master won't compile
by Alexander Wels 03 Jul '16

03 Jul '16

Hi, I just rebased master and now it won't compile user portal with the following exception, looks like the for ACTION_TYPE_FAILED_SETUP_NETWORKS_OR_REFRESH _IN_PROGESS is missing in user portal: [INFO] Generating method body for coloredText()

5 14

[ACTION REQUIRED] oVirt Engine 4.0.1 branched
by Rafael Martins 30 Jun '16

30 Jun '16

Hi, ovirt-engine-4.0.1 has been created and is currently an exact copy of ovirt-engine-4.0. >From now on, all patches targeted to 4.0.1 will need to be cherry-picked to that branch too. A patch for bumping the ovirt-engine-4.0 branch to 4.0.2 will follow. Thanks, Rafael

1 0

oVirt 4.0.1 RC1 build starting
by Lev Veyde 30 Jun '16

30 Jun '16

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. Thanks in advance, Lev Veyde.

1 0

Logs showing in the oVirt Engine localization/translation
by Juliette Tux 29 Jun '16

29 Jun '16

Hello, gentlemen, Is there a way to translate the logs which appear in the Engine interface at the bottom part of the window, see the secreenshot here: http://rgho.st/75Y5P2jXM.view ? Were the logs meant to be translated at all, i.e. are they i18'd in the source code? Kindly direct me towards the relevant files in the v 3.6.x. Sorry for another small stupid question, and lots of thanks in advance! -- Best regards, Julia Dronova С уважением, Дронова Юлия

2 1

oVirt 4.0.1 RC1 merge / tag / bugzilla reminder
by Lev Veyde 29 Jun '16

29 Jun '16

All stable branch maintainers, please make sure to: * merge all relevant open bugs until Thursday morning 11:00 AM TLV time. * https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-3.6.3.2, tr: 3.6.3.2) Thanks in advance, Lev Veyde.

1 0

Subject: oVirt 4.0.1 RC1 build planned
by Lev Veyde 29 Jun '16

29 Jun '16

Fyi oVirt developers, Please disregard the previous e-mail. An oVirt build is planned for this Thursday 11:00 AM TLV time (10:00 AM CEST). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by today (Wednesday) 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging Thursday morning. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… Thanks in advance, Lev Veyde.

1 0

oVirt 4.0.1 RC1 build planned
by Lev Veyde 29 Jun '16

29 Jun '16

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM CEST). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by Monday 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging Tuesday morning. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… Thanks in advance, Lev Veyde.

1 0

Killing XMLRPC on master
by Nir Soffer 29 Jun '16

29 Jun '16

Hi all, We are still wasting time on maintaining both xmlrpc and jsonrpc. If we kill xmlrpc, we can greatly simplify the code base, making it easier to mainain and add new features. I suggest to kill xmlrpc in 4.1, and disable it *now* on master. Currently the we have 3 issues: 1. Mom is still using xmlrpc Mom must move to jsonrpc. Martin: can you update on progress of this work? 2. sos plugin using vdsClient Need to port it to use jsonrpc library, or jsonrpc client New jsonrpc client: https://gerrit.ovirt.org/35181 3. Engine is using xmlrpc server for ovf upload/download We must support current engine in 4.1, so we cannot remove upload/download feature in this version, but we can remove the xmlrpc support in this server. Currently we abuse the xmlrpc server, supporting PUT and GET for upload and download (XMLRPC is using only POST). We can disable POST requests in protocoldetector, and not register anything with the xmlrpc server. Thoughts? Nir

7 26

Multiple versions used in oVirt JAVA libraries
by Eyal Edri 29 Jun '16

29 Jun '16

Hi, Using the latest tool we deployed to finding various issues in oVirt,. I found one of the reports were on multiple occurances of the same library but using different versions, can someone verify if this is true and if we need to align all to use the same version? Library Type Description commons-logging-1.1.1.jar Multiple Library Versions Version 1.2 is being used in project engine-server-ear xml-apis-1.0.b2.jar Multiple Library Versions Version 1.3.04 is being used in project restapi-jaxrs commons-logging-1.0.4.jar Multiple Library Versions Version 1.2 is being used in project engine-server-ear commons-beanutils-1.7.0.jar Multiple Library Versions Version 1.8.2 is being used in project interface-common-jaxrs commons-beanutils-core-1.8.0.jar Multiple Library Versions Version 1.8.3 is being used in project ovirt-checkstyle-extension jboss-logging-3.1.1.GA.jar Multiple Library Versions Version 3.1.4.GA is being used in project interface-common-jaxrs jackson-jaxrs-1.9.4.jar Multiple Library Versions Version 1.9.9 is being used in project restapi-jaxrs jboss-logging-3.1.2.GA.jar Multiple Library Versions Version 3.1.4.GA is being used in project interface-common-jaxrs jaxrs-api-2.1.0.GA.jar Multiple Library Versions Version 2.3.2.Final is being used in project engine-server-ear -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 1

[VDSM] New network test failing randomly
by Nir Soffer 28 Jun '16

28 Jun '16

Hi all, Seen this new failure yesterday: 20:44:20 ====================================================================== 20:44:20 FAIL: testGetDeviceByIP (network.netinfo_test.TestNetinfo) 20:44:20 ---------------------------------------------------------------------- 20:44:20 Traceback (most recent call last): 20:44:20 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/netinfo_test.py", line 144, in testGetDeviceByIP 20:44:20 addresses.getDeviceByIP(addr['address'].split('/')[0])) 20:44:20 AssertionError: 'bond1' != 'eno2' http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/3451/conso… The did not fail on the next run. Nir

1 1

[VDSM] Failing tests on fresh install
by Edward Haas 28 Jun '16

28 Jun '16

Hello, I got the error below when running make check after a fresh install. Has anyone seen this before? Thanks, Edy. ====================================================================== ERROR: testAlignedAppend (miscTests.DdWatchCopy) ---------------------------------------------------------------------- Traceback (most recent call last): File "/root/workspace/vdsm/tests/miscTests.py", line 373, in testAlignedAppend "/dev/zero", path, None, misc.MEGA, os.stat(path).st_size) File "/root/workspace/vdsm/lib/vdsm/storage/misc.py", line 308, in ddWatchCopy deathSignal=signal.SIGKILL) File "/root/workspace/vdsm/lib/vdsm/commands.py", line 71, in execCmd deathSignal=deathSignal) File "/usr/lib64/python2.7/site-packages/cpopen/__init__.py", line 63, in __init__ **kw) File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__ errread, errwrite) File "/usr/lib64/python2.7/site-packages/cpopen/__init__.py", line 82, in _execute_child_v276 restore_sigpipe=restore_sigpipe File "/usr/lib64/python2.7/site-packages/cpopen/__init__.py", line 107, in _execute_child_v275 restore_sigpipe OSError: [Errno 0] Error -------------------- >> begin captured logging << -------------------- 2016-06-28 03:51:05,481 DEBUG [Storage.Misc.excCmd] (MainThread) /usr/bin/taskset --cpu-list 0-0 /usr/bin/nice -n 19 /usr/bin/ionice -c 3 /usr/bin/dd if=/dev/zero of=/var/tmp/tmp_HJ3St bs=1048576 seek=1 skip=1 conv=notrunc count=1 oflag=direct (cwd None) --------------------- >> end captured logging << --------------------- ---------------------------------------------------------------------- Ran 2468 tests in 126.028s FAILED (SKIP=133, errors=1)

2 1

Re: [ovirt-devel] Build failed in Jenkins: ovirt_3.6_system-tests #168
by Nir Soffer 28 Jun '16

28 Jun '16

I think this was sent by mistake to devel(a)ovirt.org, please do not send such message to this list. On Tue, Jun 28, 2016 at 7:49 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > See <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/168/changes> > > Changes: > > [Ondra Machacek] Deploy FreeIPA to storage machine > > ------------------------------------------ > [...truncated 554 lines...] > ## took 2194 seconds > ## rc = 1 > ########################################################## > ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv > ##! Last 20 log enties: logs/mocker-fedora-23-x86_64.fc23.basic_suite_3.6.sh/basic_suite_3.6.sh.log > ##! > @ Collect artifacts: > # ovirt-role metadata entry will be soon deprecated, instead you should use the vm-provider entry in the domain definiton and set it no one of: ovirt-node, ovirt-engine, ovirt-host > # [Thread-1] lago_basic_suite_3_6_engine: > # [Thread-2] lago_basic_suite_3_6_host1: > # [Thread-3] lago_basic_suite_3_6_host0: > # [Thread-4] lago_basic_suite_3_6_storage: > # [Thread-3] lago_basic_suite_3_6_host0: Success (in 0:00:16) > # [Thread-2] lago_basic_suite_3_6_host1: Success (in 0:00:16) > # [Thread-1] lago_basic_suite_3_6_engine: Success (in 0:00:16) > # [Thread-4] lago_basic_suite_3_6_storage: Success (in 0:00:16) > @ Collect artifacts: Success (in 0:00:16) > <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests> > @@@@ ERROR: Failed running <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/b…> > ######################### > ======== Cleaning up > ----------- Cleaning with lago > ----------- Cleaning with lago done > ======== Cleanup done > Took 2033 seconds > =================================== > ##! > ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ##!######################################################## > ########################################################## > Build step 'Execute shell' marked build as failure > Performing Post build task... > Match found for :.* : True > Logical operation result is TRUE > Running script : #!/bin/bash -xe > echo 'shell_scripts/system_tests.collect_logs.sh' > > # > # Required jjb vars: > # version > # > VERSION=3.6 > SUITE_TYPE= > > WORKSPACE="$PWD" > OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" > TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" > > rm -rf "$WORKSPACE/exported-artifacts" > mkdir -p "$WORKSPACE/exported-artifacts" > > if [[ -d "$TESTS_LOGS" ]]; then > mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" > fi > > [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson3155110657872379488.sh > + echo shell_scripts/system_tests.collect_logs.sh > shell_scripts/system_tests.collect_logs.sh > + VERSION=3.6 > + SUITE_TYPE= > + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> > + OVIRT_SUITE=3.6 > + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> > + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/168/artifact/exported-a…> > + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/168/artifact/exported-a…> > + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> ]] > + mv <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/168/artifact/exported-a…> > POST BUILD TASK : SUCCESS > END OF POST BUILD TASK : 0 > Match found for :.* : True > Logical operation result is TRUE > Running script : #!/bin/bash -xe > echo "shell-scripts/mock_cleanup.sh" > > shopt -s nullglob > > > WORKSPACE="$PWD" > > # Make clear this is the cleanup, helps reading the jenkins logs > cat <<EOC > _______________________________________________________________________ > ####################################################################### > # # > # CLEANUP # > # # > ####################################################################### > EOC > > > # Archive the logs, we want them anyway > logs=( > ./*log > ./*/logs > ) > if [[ "$logs" ]]; then > tar cvzf exported-artifacts/logs.tgz "${logs[@]}" > rm -rf "${logs[@]}" > fi > > # stop any processes running inside the chroot > failed=false > mock_confs=("$WORKSPACE"/*/mocker*) > # Clean current jobs mockroot if any > for mock_conf_file in "${mock_confs[@]}"; do > [[ "$mock_conf_file" ]] || continue > echo "Cleaning up mock $mock_conf" > mock_root="${mock_conf_file##*/}" > mock_root="${mock_root%.*}" > my_mock="/usr/bin/mock" > my_mock+=" --configdir=${mock_conf_file%/*}" > my_mock+=" --root=${mock_root}" > my_mock+=" --resultdir=$WORKSPACE" > > #TODO: investigate why mock --clean fails to umount certain dirs sometimes, > #so we can use it instead of manually doing all this. > echo "Killing all mock orphan processes, if any." > $my_mock \ > --orphanskill \ > || { > echo "ERROR: Failed to kill orphans on $chroot." > failed=true > } > > mock_root="$(\ > grep \ > -Po "(?<=config_opts\['root'\] = ')[^']*" \ > "$mock_conf_file" \ > )" || : > [[ "$mock_root" ]] || continue > mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : > if [[ "$mounts" ]]; then > echo "Found mounted dirs inside the chroot $chroot. Trying to umount." > fi > for mount in "${mounts[@]}"; do > sudo umount --lazy "$mount" \ > || { > echo "ERROR: Failed to umount $mount." > failed=true > } > done > done > > # Clean any leftover chroot from other jobs > for mock_root in /var/lib/mock/*; do > this_chroot_failed=false > mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : > if [[ "$mounts" ]]; then > echo "Found mounted dirs inside the chroot $mock_root." \ > "Trying to umount." > fi > for mount in "${mounts[@]}"; do > sudo umount --lazy "$mount" \ > || { > echo "ERROR: Failed to umount $mount." > failed=true > this_chroot_failed=true > } > done > if ! $this_chroot_failed; then > sudo rm -rf "$mock_root" > fi > done > > if $failed; then > echo "Aborting." > exit 1 > fi > > # remove mock system cache, we will setup proxies to do the caching and this > # takes lots of space between runs > shopt -u nullglob > sudo rm -Rf /var/cache/mock/* > > # restore the permissions in the working dir, as sometimes it leaves files > # owned by root and then the 'cleanup workspace' from jenkins job fails to > # clean and breaks the jobs > sudo chown -R "$USER" "$WORKSPACE" > > [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson1974597178250713835.sh > + echo shell-scripts/mock_cleanup.sh > shell-scripts/mock_cleanup.sh > + shopt -s nullglob > + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> > + cat > _______________________________________________________________________ > ####################################################################### > # # > # CLEANUP # > # # > ####################################################################### > + logs=(./*log ./*/logs) > + [[ -n ./ovirt-system-tests/logs ]] > + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs > ./ovirt-system-tests/logs/ > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/ > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/state.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/build.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/stdout_stderr.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/root.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/ > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/stdout_stderr.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.basic_suite_3.6.sh/ > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.basic_suite_3.6.sh/basic_suite_3.6.sh.log > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/ > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/stdout_stderr.log > + rm -rf ./ovirt-system-tests/logs > + failed=false > + mock_confs=("$WORKSPACE"/*/mocker*) > + for mock_conf_file in '"${mock_confs[@]}"' > + [[ -n <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/m…> ]] > + echo 'Cleaning up mock ' > Cleaning up mock > + mock_root=mocker-fedora-23-x86_64.fc23.cfg > + mock_root=mocker-fedora-23-x86_64.fc23 > + my_mock=/usr/bin/mock > + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests'> > + my_mock+=' --root=mocker-fedora-23-x86_64.fc23' > + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/'> > + echo 'Killing all mock orphan processes, if any.' > Killing all mock orphan processes, if any. > + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests> --root=mocker-fedora-23-x86_64.fc23 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> --orphanskill > WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/l….> Using default... > INFO: mock.py version 1.2.17 starting (python version = 3.4.3)... > Start: init plugins > INFO: selinux enabled > Finish: init plugins > Start: run > Finish: run > ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/m…> > + mock_root=fedora-23-x86_64-ecdfd9c866cbf1a2d41342199fdb011f > + [[ -n fedora-23-x86_64-ecdfd9c866cbf1a2d41342199fdb011f ]] > + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) > ++ mount > ++ grep fedora-23-x86_64-ecdfd9c866cbf1a2d41342199fdb011f > ++ awk '{print $3}' > + : > + [[ -n '' ]] > + false > + shopt -u nullglob > + sudo rm -Rf /var/cache/mock/fedora-23-x86_64-ecdfd9c866cbf1a2d41342199fdb011f > + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> > POST BUILD TASK : SUCCESS > END OF POST BUILD TASK : 1 > Recording test results > Archiving artifacts > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra

2 3

Re: [ovirt-devel] Storage in VDSM questions
by Liron Aravot 27 Jun '16

27 Jun '16

> > ---------- Forwarded message ---------- > From: Shmuel Melamud <smelamud(a)redhat.com> > Date: Wed, Jun 22, 2016 at 4:51 PM > Subject: [ovirt-devel] Storage in VDSM questions > To: devel <devel(a)ovirt.org> > > > Hi! > > I have a bunch of questions related to storage in VDSM. I would be happy > if anybody familiar with the subject can help me with them. > > 1. What is HSM? IRS? > IRS = SPM HSM=non SPM host > 2. What is SDM? > SDM= Storage Domain Management A feature currently under development that provides alternate method to SPM to manage shared storage. > 3. What hsm.spmSchedule() method does? > Schedules a task to be executed as SPM (used to perform operation that alter the shared storage or data operations currently). > 4. What does domainMonitor.getHostId(vol_info.sd_id) method return? > I'd recomment to do some SANLock reading (see below). Basically, its the id the host uses to acquire locks on the shared storage. http://linux.die.net/man/8/sanlock http://old.ovirt.org/SANLock > > Storage domain > > 5. What is StorageDomainManifest? Why there are separate StorageDomain and > StorageDomainManifest classes? (And the same with Volume and > VolumeManifest.) > Those are changes made in order to share "SPM" related code with "SDM" related code (as not all of the code is relevant for both). alitke/nsoffer could share more information on the decisions behind adding those. > 6. What does sd_manifest.domain_lock(host_id) guard? Why do we need the > host_id parameter? > see answer to question 4. > 7. Why in HSM we are using vars.task.getSharedLock(STORAGE, sdUUID) > sometimes instead of domain lock? > The task lock (which uses the resource manager) is used to acquire in memory logical lock within the current host. Theoretical example- you wouldn't want to attempt to delete a domain while you create a volume on it. 8. What does sd_manifest.get_volume_artifacts(img_id, vol_id) return? > > Resource manager > > 9. What is ResourceManager? > Resource manager is basically a in memory lock manager in vdsm. > 10. What rmanager.acquireResource(image_res_ns, img_id, lockType) does? > What types of resources it may be used with? > Well, the best answer would be the simple one - its used to acquire a resource, you can specify a namespace and id, the lock will be taken on namespace_ID so basically you can acquire lock on the same id under different namespaces. > > Images and volumes > > 11. What methods dom.linkBCImage(imgPath, imgUUID) and > dom.unlinkBCImage(imgUUID) do? > Creates/Removes a symlink to a given image. > 12. What methods dom.activateVolumes(imgUUID, imgVolumes) and > dom.deactivateImage(imgUUID) do? > Can you be a bit more specific in the question? I don't have much to add over the method names. > > 13. What method dom.getVolumeLease(imgUUID, volUUID) does? > see related SANLock question before. > 14. What methods volume.prepare() and volume.teardown() do? > > Thanks in advance for your answers! > > Shmuel > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > >

2 1

Weekly bug status for ovirt-system-tests (using Lago) [ 27/06/16 ]
by Eyal Edri 27 Jun '16

27 Jun '16

*Open bugs:* https://goo.gl/eUaPUY *Fixed/Closed bugs:* Bug 1298646 <https://bugzilla.redhat.com/show_bug.cgi?id=1298646> [Lago] - hosted engine setup causes kernel panic Bug 1280361 <https://bugzilla.redhat.com/show_bug.cgi?id=1280361> Create the jenkins jobs to check the ovirt-system-tests patches Bug 1282691 <https://bugzilla.redhat.com/show_bug.cgi?id=1282691> Make the ovirt lago tests run for master code *Open issues:* - add Lago & test logs to check-patch job (bug opened) - add install cockpit-ovirt-dashboard to 4.0/master (now its taking in 500 pkg) - move master and 4.0 tests to use API V4 (bug opened) - hosted engine 4.0 tests are in progress *Open patches:* (reviews are welcome) https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:open *Jenkins jobs:* http://jenkins.ovirt.org/view/oVirt%20system%20tests/ *Recently merged patches:* https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:merged+since… *A lot of new stuff went in during last week! here are some of the highlights:* 1. New per patch 'check-patch' job added, now jenkins will automatically verify your patches to ovirt-system-tests 2. New 'install cockpit-ovirt-dashboard' test added to 3.6 3. New 'remove default DC & cluster' test added 4. New 'add VM from Glance template' test added 5. New basic 'network add' tests added 6. Compatibility version updated to 4.0 & 4.1 to 4.0 & master respectively Keep those tests coming... -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Jenkins.ovirt.org outage
by Eyal Edri 24 Jun '16

24 Jun '16

Following on previous message, we are still suffering issues on jenkins.ovirt.org, And some jobs are failing on network connectivity. We'll update when the problem is resolved, though might be resolved only on Sunday due to unavailability of most people during the weekend. -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Node updates broken
by Fabian Deutsch 24 Jun '16

24 Jun '16

Hey, the node updates on 4.0, 4.0-pre, and 4.0-snapshot are currently broken because of two things: 1. We need an ovirt-release release in 4.0 to pull in some node fixes 2. We need regular updates of 4.0-snapshot to build the updates - fabian -- Fabian Deutsch <fdeutsch(a)redhat.com> RHEV Hypervisor Red Hat

2 1

[Attention] Jenkins maintenance today(24/06/2016 01:00 AM TLV)
by Nadav Goldin 23 Jun '16

23 Jun '16

Hi, As part of an infrastructure upgrade, in approximately one hour at 01:00 AM TLV, http://jenkins.ovirt.org will be shut down for maintenance, expected downtime is 15 minutes. Patches sent during the downtime will be checked afterwards, patches sent around 40 minutes prior to the downtime might not get checked. If patches you sent did not trigger CI, you can login after the downtime and re-trigger them manually. Thanks, Nadav.

1 1

planned restart of ci-templates-repo.phx.ovirt.org and glance.phx.ovirt.org
by Evgheni Dereveanchin 23 Jun '16

23 Jun '16

Hello everyone, I'll restart these two VMs to move them to the new oVirt cluster: ci-templates-repo.phx.ovirt.org glance.phx.ovirt.org The first VM is used by lago. If any jobs fail due to template unavailability please restart them. If you find any persisting issues please let me know. Regards, Evgheni Dereveanchin

1 0

[ANN] oVirt 4.0.0 Final Release is now available
by Sandro Bonazzola 23 Jun '16

23 Jun '16

The oVirt Project is pleased to announce today the general availability of oVirt 4.0.0. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 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]. See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO will be available soon. [4] * A new oVirt Next Generation Node will be available soon [4]. * A new oVirt Engine Appliance will be available soon. * A new oVirt Guest Tools ISO is already available [4]. * Mirrors[5] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 4.0.0 release highlights: http://www.ovirt.org/release/4.0.0/ * 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.0.0/ [4] http://resources.ovirt.org/pub/ovirt-4.0/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Fwd: Reminder: Fedora 22 end of life 2016-07-19
by Sandro Bonazzola 23 Jun '16

23 Jun '16

FYI ---------- Messaggio inoltrato ---------- Da: "Dennis Gilmore" <dennis(a)ausil.us> Data: 23/Giu/2016 06:43 Oggetto: Reminder: Fedora 22 end of life 2016-07-19 A: <devel-announce(a)lists.fedoraproject.org>, "test-announce" < test-announce(a)lists.fedoraproject.org>, "announce" < announce(a)lists.fedoraproject.org> Cc: > Greetings. > > This is a reminder email about the end of life process for Fedora 22. > > Fedora 22 will reach end of life on 2016-07-19, and no further updates > will be pushed out after that time. Additionally, with the recent > release of Fedora 24, no new packages will be added to the Fedora 22 > collection. > > Please see https://fedoraproject.org/wiki/DNF_system_upgrade for more > information on upgrading from Fedora 22 to a newer release. > > Dennis > _______________________________________________ > devel-announce mailing list > devel-announce(a)lists.fedoraproject.org > https://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedoraproj…

1 0

Storage in VDSM questions
by Shmuel Melamud 22 Jun '16

22 Jun '16

Hi! I have a bunch of questions related to storage in VDSM. I would be happy if anybody familiar with the subject can help me with them. 1. What is HSM? IRS? 2. What is SDM? 3. What hsm.spmSchedule() method does? 4. What does domainMonitor.getHostId(vol_info.sd_id) method return? Storage domain 5. What is StorageDomainManifest? Why there are separate StorageDomain and StorageDomainManifest classes? (And the same with Volume and VolumeManifest.) 6. What does sd_manifest.domain_lock(host_id) guard? Why do we need the host_id parameter? 7. Why in HSM we are using vars.task.getSharedLock(STORAGE, sdUUID) sometimes instead of domain lock? 8. What does sd_manifest.get_volume_artifacts(img_id, vol_id) return? Resource manager 9. What is ResourceManager? 10. What rmanager.acquireResource(image_res_ns, img_id, lockType) does? What types of resources it may be used with? Images and volumes 11. What methods dom.linkBCImage(imgPath, imgUUID) and dom.unlinkBCImage(imgUUID) do? 12. What methods dom.activateVolumes(imgUUID, imgVolumes) and dom.deactivateImage(imgUUID) do? 13. What method dom.getVolumeLease(imgUUID, volUUID) does? 14. What methods volume.prepare() and volume.teardown() do? Thanks in advance for your answers! Shmuel

1 0