Re: [ovirt-devel] VDSM crashed while adding host to newly created cluster
On 26-03-2015 19:24, Christopher Pereira wrote: Is it normal that 1) the engine stops VDSM during activation and 2) that VDSM stops or restarts the storage during shutdown? Well, no wonder that the engine-storage disappears since the gluster process is a child-process of the vdsmd.service CGroup: /system.slice/vdsmd.service ├─14895 /usr/bin/python /usr/share/vdsm/vdsm ├─14964 /usr/libexec/ioprocess --read-pipe-fd 43 --write-pipe-fd 42 --max-threads 10 --ma ├─15836 /usr/libexec/ioprocess --read-pipe-fd 49 --write-pipe-fd 48 --max-threads 10 --ma * ├─15911 /usr/sbin/glusterfs --volfile-server=h2.imatronix.com --volfile-id=engine /rhev/d* └─15922 /usr/libexec/ioprocess --read-pipe-fd 61 --write-pipe-fd 60 --max-threads 10 --ma A workarround is to mount the engine-storage manually, so that restarting vdsmd on the host doesn't kill the engine VM. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] VDSM crashed while adding host to newly created cluster
On 26-03-2015 18:16, Christopher Pereira wrote:
Now, how can I fix the "invalid lockspace"?
hosted-engine start-pool + connect-storage + vm-start solved the invalid
lockspace problem and made it possible to restart the engine VM, but the
hosted-engine-setup is unable to resume:
2015-03-26 21:56:42 DEBUG
otopi.plugins.ovirt_hosted_engine_setup.engine.add_host
add_host._wait_host_ready:189 VDSM host in non_responsive state
2015-03-26 21:56:44 DEBUG
otopi.plugins.ovirt_hosted_engine_setup.engine.add_host
add_host._wait_host_ready:189 VDSM host in non_responsive state
2015-03-26 21:56:46 DEBUG
otopi.plugins.ovirt_hosted_engine_setup.engine.add_host
add_host._wait_host_ready:189 VDSM host in non_responsive state
[...]
Then, inside the web-manager, I tried to activate the host manually and
it seems like the engine stops VDSM:
Mar 26 22:01:10 h2 systemd: Stopping Virtual Desktop Server Manager...
Mar 26 22:01:10 h2 journal: vdsm IOProcessClient ERROR IOProcess failure
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py",
line 107, in _communicate
raise Exception("FD closed")
Exception: FD closed
And the engine-storage disappeared again.
Then, since QEMU doesn't reopen the (invalid) file descriptors, the VM
can't be resumed (BZ 1058300).
Is it normal that 1) the engine stops VDSM during activation and 2) that
VDSM stops or restarts the storage during shutdown?
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] VDSM crashed while adding host to newly created cluster
Continuing with the 3.6 Night Builds testing...
While hosted-engine-setup was adding the host to the newly created
cluster, VDSM crashed, probably because the gluster engine storage
disappeared as in BZ 1201355 [1]
Facts:
- the engine storage (/rhev/data-center/mmt/...) was umounted
during this process
- another mount of the same volume was still mounted after the VDSM
crash (maybe the problem is not related with gluster)
After doing a "hosted-engine --connect-storage", the volume is mounted
again.
Now, when trying to restart VDSM, I get an "invalid lockspace":
Thread-46::ERROR::2015-03-26
19:24:31,843::vm::1237::vm.Vm::(_startUnderlyingVm)
vmId=`191045ac-79e4-4ce8-aad7-52cc9af313c5`::The vm start process failed
Traceback (most recent call last):
File "/usr/share/vdsm/virt/vm.py", line 1185, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/virt/vm.py", line 2253, in _run
self._connection.createXML(domxml, flags),
File
"/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 126,
in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3427,
in createXML
if ret is None:raise libvirtError('virDomainCreateXML()
failed', conn=self)
libvirtError: Failed to acquire lock: No space left on device
Thread-46::INFO::2015-03-26
19:24:31,844::vm::1709::vm.Vm::(setDownStatus)
vmId=`191045ac-79e4-4ce8-aad7-52cc9af313c5`::Changed state to Down:
Failed to acquire lock: No space left on device (code=1)
Thread-46::DEBUG::2015-03-26
19:24:31,844::vmchannels::214::vds::(unregister) Delete fileno 60 from
listener.
VM Channels Listener::DEBUG::2015-03-26
19:24:32,346::vmchannels::121::vds::(_do_del_channels) fileno 60 was
removed from listener.
In sanlock.log we have:
2015-03-26 19:24:30+ 7589 [752]: cmd 9 target pid 9559 not found
2015-03-26 19:24:31+ 7589 [764]: r7 cmd_acquire 2,8,9559
invalid lockspace found -1 failed 935819904 name
7ba46e75-51af-4648-becc-5a469cb8e9c2
(All 3 lease files are present)
This problem is similar to BZ 1201355 reported by Sandro [1].
About the hosted-engine VM not being resumed after restarting VDSM,
please check [2] and [3] (duplicated).
I confirmed that QEMU is not reopening the file descriptors when
resuming a paused VMs, which explains those issues.
Now, how can I fix the "invalid lockspace"?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1201355
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1172905
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1058300
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
[...] Il 26/03/2015 08:56, Christopher Pereira ha scritto: [...] During the "Waiting for the host to become operational in the engine" stage, the hosted-engine-setup fails because of the following VDSM requirement: "VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for clusterLevel >= 3.6 is disabled. For Fedora 20 users, please consider upgrading libvirt from the virt-preview repository" According to [1], libvirt version >= 1.2.3 is required. Any suggestion where to get this packages + dependencies for CentOS 7? [...] OTOH, I wrote the above only because Centos 7.1 is not yet released, so one must use the RC (Release Candidate) Centos repos, and because I can't recommend any extra repo. [...] For the records, I installed libvirt 1.2.8 from CR repo: yum --enablerepo=cr install libvirt-daemon This broke vdsm because of a "no connection driver available for qemu:///system" error. The problem was that libvirt 1.2.8 "failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so" and "/usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so: undefined symbol: virStorageFileCreate". The solution is to upgrade device-mapper-libs: yum --enablerepo=cr upgrade device-mapper-libs Conclusion: A device-mapper dependency should be added to libvirt This are my installed packages: device-mapper-1.02.93-3.el7.x86_64 device-mapper-event-1.02.93-3.el7.x86_64 device-mapper-event-libs-1.02.93-3.el7.x86_64 device-mapper-libs-1.02.93-3.el7.x86_64 device-mapper-multipath-0.4.9-66.el7.x86_64 device-mapper-multipath-libs-0.4.9-66.el7.x86_64 device-mapper-persistent-data-0.3.2-1.el7.x86_64 libvirt-client-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-config-nwfilter-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-driver-interface-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-driver-network-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-driver-nodedev-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-driver-nwfilter-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-driver-qemu-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-driver-secret-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-driver-storage-1.2.8-16.el7_1.1.x86_64 libvirt-daemon-kvm-1.2.8-16.el7_1.1.x86_64 libvirt-lock-sanlock-1.2.8-16.el7_1.1.x86_64 libvirt-python-1.2.8-7.el7_1.1.x86_64 Regards, Christopher ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Greg Sheremeta is now an ovirt-engine UI maintainer
On 03/26/2015 09:20 AM, Vojtech Szocs wrote: Congrats Greg! :) Indeed, Congrats Greg! Well deserved. :-) Vojtech - Original Message - From: "Einav Cohen" To: "Lior Vernia" , "Alona Kaplan" , "Daniel Erez" , "Gilad Chaplik" , "Tomas Jelinek" , "Vojtech Szocs" , "Alexander Wels" , "Kanagaraj" , "Tal Nisan" , "Greg Sheremeta" Cc: devel@ovirt.org Sent: Wednesday, March 25, 2015 5:58:40 PM Subject: Greg Sheremeta is now an ovirt-engine UI maintainer Thanks, everyone, for your support. Greg is now an oVirt-engine UI maintainer. Greg - congratulations! Regards, Einav - Original Message - From: "Einav Cohen" To: "Lior Vernia" , "Alona Kaplan" , "Daniel Erez" , "Gilad Chaplik" , "Tomas Jelinek" , "Vojtech Szocs" , "Alexander Wels" , "Kanagaraj" , "Tal Nisan" Cc: in...@ovirt.org, devel@ovirt.org Sent: Wednesday, March 25, 2015 8:59:17 AM Subject: [ovirt-devel] proposing Greg Sheremeta as an ovirt-engine UI maintainer Hello UI Maintainers, I would like to propose Greg Sheremeta as an ovirt-engine UI maintainer. Greg started being actively involved in ovirt on July 2013, contributing over 150 patches (to 'master' alone), including improvements to the branding mechanism (e.g. support cascading resources), grid-column width persistence, phase 1 of the PatternFly styling adoption, dialog-id (tag) based mapping infrastructure, multiple automated-UI-tests (Selenium) related enhancements and the recent overhaul of the tool-tips throughout the code. Your response would be highly appreciated. Many thanks in advance. Regards, Einav ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel -- Cheers Douglas ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Greg Sheremeta is now an ovirt-engine UI maintainer
Congrats Greg! :) Vojtech - Original Message - > From: "Einav Cohen" > To: "Lior Vernia" , "Alona Kaplan" , > "Daniel Erez" , > "Gilad Chaplik" , "Tomas Jelinek" , > "Vojtech Szocs" , > "Alexander Wels" , "Kanagaraj" , "Tal > Nisan" , "Greg > Sheremeta" > Cc: devel@ovirt.org > Sent: Wednesday, March 25, 2015 5:58:40 PM > Subject: Greg Sheremeta is now an ovirt-engine UI maintainer > > Thanks, everyone, for your support. > Greg is now an oVirt-engine UI maintainer. > Greg - congratulations! > > > Regards, > Einav > > - Original Message - > > From: "Einav Cohen" > > To: "Lior Vernia" , "Alona Kaplan" > > , "Daniel Erez" , > > "Gilad Chaplik" , "Tomas Jelinek" > > , "Vojtech Szocs" , > > "Alexander Wels" , "Kanagaraj" , > > "Tal Nisan" > > Cc: in...@ovirt.org, devel@ovirt.org > > Sent: Wednesday, March 25, 2015 8:59:17 AM > > Subject: [ovirt-devel] proposing Greg Sheremeta as an ovirt-engine UI > > maintainer > > > > Hello UI Maintainers, > > > > I would like to propose Greg Sheremeta as an ovirt-engine > > UI maintainer. > > > > Greg started being actively involved in ovirt on July 2013, > > contributing over 150 patches (to 'master' alone), including > > improvements to the branding mechanism (e.g. support cascading > > resources), grid-column width persistence, phase 1 of the > > PatternFly styling adoption, dialog-id (tag) based mapping > > infrastructure, multiple automated-UI-tests (Selenium) related > > enhancements and the recent overhaul of the tool-tips throughout > > the code. > > > > Your response would be highly appreciated. > > > > Many thanks in advance. > > > > > > Regards, > > Einav > > ___ > > Devel mailing list > > Devel@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > > > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] gerrit jenkins bot has gotten noisier
On 03/26, Michal Skrivanek wrote: > > > On 25 Mar 2015, at 13:58, David Caro wrote: > > > > > This was done because it was requested some time ago. > > > > That will also remind devels that they should not merge any patches that > > have > > not finished running the jenkins jobs yet. > > > > In a (hopefully) near future, that will not be needed as jobs will become a > > gateway to merge, meaning that the regular merge flow will require passing > > the > > jenkins jobs. > > I would strongly object to this, until we have a positive experience of no > false positives for at least couple of months. > Then it is a great idea. > That's like expecting that every patch sent for review to pass all the tests, all the time for a month and not failing once, and I don't mean each MERGED patch, I mean each one sent for review. Just so you have some numbers on what you are currently asking for, some stats about builds for the last two weeks: Number of SUCCESS builds:50061 Number of FAILED builds: 1777 Number of UNSTABLE builds: 749 Number of ABORTED builds: 124 Number of NOTBUILT builds: 326 Total number of builds: 53037 Percentage of failed builds: 5.61% Here, failed builds includes infra issues and test failures, we don't have means yet to properly distinguish both. I know this is including all the projects, not just the most 'complicated' ones, but that means that, on small projects, where the maintainer of the project is also writing it's own acceptance tests, the failure ratio is a lot lower than on the bigger projects, where the failures are ignored and the tests not maintained, or left for the lonely infra guy that has ~50% of it's time to handle them all, doing a quick ugly calculation, that guy has 48 seconds to review each failure and fix it (being it an infra issue or not). So you expect that someone that has no involvement on the development of most of the projects, single-handedly fix and triage all those builds, 48 seconds each, and also care about all the other infra-related duties. And not only succeed doing that, but maintain all the system from failing once during two months. I'm sorry but as I see it a lot has to change for that to be feasible, and I really don't think it's fair to request it to that 1/2 guy. > > > In the meantime, it's just a remainder. > > > > On 03/25, Martin Perina wrote: > >> > >> > >> - Original Message - > >>> From: "Greg Sheremeta" > >>> To: in...@ovirt.org, "Eyal Edri" , "David Caro" > >>> > >>> Cc: devel@ovirt.org > >>> Sent: Wednesday, March 25, 2015 1:40:35 PM > >>> Subject: [ovirt-devel] gerrit jenkins bot has gotten noisier > >>> > >>> Hey guys, > >>> > >>> Sometime last week, the jenkins bot upped the verbosity of his > >>> notifications on patches. Was this by design? > >>> > >>> Example: https://gerrit.ovirt.org/#/c/39098/ > >>> > >>> He now adds many "build started" messages. He used to only let > >>> us know about success / failure. > >>> > >>> Not a huge deal, but it's more noise to filter through -- both > >>> in gerrit and email. > >> > >> Agreed, especially for emails. Personally I don't care about build > >> process details, I'd like to know only final result of the build. > >> If the build failed, I could find details on jenkins. > >> > >> Martin > >> > >>> > >>> Thanks, > >>> Greg > >>> > >>> Greg Sheremeta > >>> Red Hat, Inc. > >>> Sr. Software Engineer, RHEV > >>> Cell: 919-807-1086 > >>> gsher...@redhat.com > >>> ___ > >>> Devel mailing list > >>> Devel@ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/devel > > > > -- > > David Caro > > > > Red Hat S.L. > > Continuous Integration Engineer - EMEA ENG Virtualization R&D > > > > Tel.: +420 532 294 605 > > Email: dc...@redhat.com > > Web: www.redhat.com > > RHT Global #: 82-62605 > > ___ > > Devel mailing list > > Devel@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 pgpDQcsl10kf1.pgp Description: PGP signature ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
On Mar 26, 2015, at 09:36 , Francesco Romani wrote: > - Original Message - >> From: "Michal Skrivanek" >> To: "Francesco Romani" >> Cc: "Sandro Bonazzola" , devel@ovirt.org >> Sent: Thursday, March 26, 2015 9:27:58 AM >> Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM >> requirements > >>> - Original Message - From: "Sandro Bonazzola" To: "Christopher Pereira" , devel@ovirt.org, "Francesco Romani" Sent: Thursday, March 26, 2015 9:05:02 AM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements Il 26/03/2015 08:56, Christopher Pereira ha scritto: > > On 25-03-2015 10:07, Sandro Bonazzola wrote: >> Il 25/03/2015 14:05, Christopher Pereira ha scritto: >>> [...] >>> Maybe you want to add some more dependencies to the nightly build repo. >> Thanks for reporting, we're already on it. > > During the "Waiting for the host to become operational in the engine" > stage, the hosted-engine-setup fails because of the following VDSM > requirement: > > "VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for > clusterLevel >= 3.6 is disabled. For Fedora 20 users, please consider > upgrading > libvirt from the virt-preview repository" > > According to [1], libvirt version >= 1.2.3 is required. > > Any suggestion where to get this packages + dependencies for CentOS 7? Francesco? >>> >>> I need to check/start a few discussions, but most likely we'll need Centos >>> 7.1. >>> I'm not aware of any (reliable) repos like virt-preview for Centos. >>> >>> Bottom line: for hosted engine we may need to revert the patch requiring >>> AUTO_CONVERGE. >>> So unfortunate. >> >> Why? >> Just get the right libvirt from anywhere in the interim period. Centos 7.1 is >> going to be released any day now > > I also believe it is better (less noise to everyone) to wait few days for > Centos 7.1, > which indeed should be out soon: > http://seven.centos.org/2015/03/centos-7-next-release/ > > OTOH, I wrote the above only because Centos 7.1 is not yet released, so one > must use > the RC (Release Candidate) Centos repos, and because I can't recommend any > extra repo. which is absolutely fine, IMHO. if someone wants to work with nightly he/she needs to know some things. no nightly builds in any project are intended as a problem-free general-public ready releases…especially this early in 3.6 cycle Waiting for all the libraries to go out significantly hurts the development process. IMO the best compromise is that CI on master needs to be ready for these things and update to the similar (at least Beta or RC) repositories of our dependencies Thanks, michal > > > -- > Francesco Romani > RedHat Engineering Virtualization R & D > Phone: 8261328 > IRC: fromani ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
- Original Message - > From: "Michal Skrivanek" > To: "Francesco Romani" > Cc: "Sandro Bonazzola" , devel@ovirt.org > Sent: Thursday, March 26, 2015 9:27:58 AM > Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM > requirements > > - Original Message - > >> From: "Sandro Bonazzola" > >> To: "Christopher Pereira" , devel@ovirt.org, > >> "Francesco Romani" > >> Sent: Thursday, March 26, 2015 9:05:02 AM > >> Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM > >> requirements > >> > >> Il 26/03/2015 08:56, Christopher Pereira ha scritto: > >>> > >>> On 25-03-2015 10:07, Sandro Bonazzola wrote: > Il 25/03/2015 14:05, Christopher Pereira ha scritto: > > [...] > > Maybe you want to add some more dependencies to the nightly build repo. > Thanks for reporting, we're already on it. > >>> > >>> During the "Waiting for the host to become operational in the engine" > >>> stage, the hosted-engine-setup fails because of the following VDSM > >>> requirement: > >>> > >>>"VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for > >>>clusterLevel >= 3.6 is disabled. For Fedora 20 users, please consider > >>>upgrading > >>>libvirt from the virt-preview repository" > >>> > >>> According to [1], libvirt version >= 1.2.3 is required. > >>> > >>> Any suggestion where to get this packages + dependencies for CentOS 7? > >> > >> Francesco? > > > > I need to check/start a few discussions, but most likely we'll need Centos > > 7.1. > > I'm not aware of any (reliable) repos like virt-preview for Centos. > > > > Bottom line: for hosted engine we may need to revert the patch requiring > > AUTO_CONVERGE. > > So unfortunate. > > Why? > Just get the right libvirt from anywhere in the interim period. Centos 7.1 is > going to be released any day now I also believe it is better (less noise to everyone) to wait few days for Centos 7.1, which indeed should be out soon: http://seven.centos.org/2015/03/centos-7-next-release/ OTOH, I wrote the above only because Centos 7.1 is not yet released, so one must use the RC (Release Candidate) Centos repos, and because I can't recommend any extra repo. -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Il 26/03/2015 09:27, Michal Skrivanek ha scritto: > > > On 26 Mar 2015, at 09:14, Francesco Romani wrote: > >> Hi, >> >> - Original Message - >>> From: "Sandro Bonazzola" >>> To: "Christopher Pereira" , devel@ovirt.org, >>> "Francesco Romani" >>> Sent: Thursday, March 26, 2015 9:05:02 AM >>> Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM >>> requirements >>> >>> Il 26/03/2015 08:56, Christopher Pereira ha scritto: On 25-03-2015 10:07, Sandro Bonazzola wrote: > Il 25/03/2015 14:05, Christopher Pereira ha scritto: >> [...] >> Maybe you want to add some more dependencies to the nightly build repo. > Thanks for reporting, we're already on it. During the "Waiting for the host to become operational in the engine" stage, the hosted-engine-setup fails because of the following VDSM requirement: "VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for clusterLevel >= 3.6 is disabled. For Fedora 20 users, please consider upgrading libvirt from the virt-preview repository" According to [1], libvirt version >= 1.2.3 is required. Any suggestion where to get this packages + dependencies for CentOS 7? >>> >>> Francesco? >> >> I need to check/start a few discussions, but most likely we'll need Centos >> 7.1. >> I'm not aware of any (reliable) repos like virt-preview for Centos. >> >> Bottom line: for hosted engine we may need to revert the patch requiring >> AUTO_CONVERGE. >> So unfortunate. > > Why? > Just get the right libvirt from anywhere in the interim period. Centos 7.1 is > going to be released any day now 1.2.8 is available in the CR repo:http://mirror.centos.org/centos/7/cr/x86_64 while we wait for official 7.1 release > > Thanks, > michal >> >> -- >> Francesco Romani >> RedHat Engineering Virtualization R & D >> Phone: 8261328 >> IRC: fromani >> ___ >> Devel mailing list >> Devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] gerrit jenkins bot has gotten noisier
On 25 Mar 2015, at 13:58, David Caro wrote: > > This was done because it was requested some time ago. > > That will also remind devels that they should not merge any patches that have > not finished running the jenkins jobs yet. > > In a (hopefully) near future, that will not be needed as jobs will become a > gateway to merge, meaning that the regular merge flow will require passing the > jenkins jobs. I would strongly object to this, until we have a positive experience of no false positives for at least couple of months. Then it is a great idea. > In the meantime, it's just a remainder. > > On 03/25, Martin Perina wrote: >> >> >> - Original Message - >>> From: "Greg Sheremeta" >>> To: in...@ovirt.org, "Eyal Edri" , "David Caro" >>> >>> Cc: devel@ovirt.org >>> Sent: Wednesday, March 25, 2015 1:40:35 PM >>> Subject: [ovirt-devel] gerrit jenkins bot has gotten noisier >>> >>> Hey guys, >>> >>> Sometime last week, the jenkins bot upped the verbosity of his >>> notifications on patches. Was this by design? >>> >>> Example: https://gerrit.ovirt.org/#/c/39098/ >>> >>> He now adds many "build started" messages. He used to only let >>> us know about success / failure. >>> >>> Not a huge deal, but it's more noise to filter through -- both >>> in gerrit and email. >> >> Agreed, especially for emails. Personally I don't care about build >> process details, I'd like to know only final result of the build. >> If the build failed, I could find details on jenkins. >> >> Martin >> >>> >>> Thanks, >>> Greg >>> >>> Greg Sheremeta >>> Red Hat, Inc. >>> Sr. Software Engineer, RHEV >>> Cell: 919-807-1086 >>> gsher...@redhat.com >>> ___ >>> Devel mailing list >>> Devel@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel > > -- > David Caro > > Red Hat S.L. > Continuous Integration Engineer - EMEA ENG Virtualization R&D > > Tel.: +420 532 294 605 > Email: dc...@redhat.com > Web: www.redhat.com > RHT Global #: 82-62605 > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
On 26 Mar 2015, at 09:14, Francesco Romani wrote: > Hi, > > - Original Message - >> From: "Sandro Bonazzola" >> To: "Christopher Pereira" , devel@ovirt.org, >> "Francesco Romani" >> Sent: Thursday, March 26, 2015 9:05:02 AM >> Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM >> requirements >> >> Il 26/03/2015 08:56, Christopher Pereira ha scritto: >>> >>> On 25-03-2015 10:07, Sandro Bonazzola wrote: Il 25/03/2015 14:05, Christopher Pereira ha scritto: > [...] > Maybe you want to add some more dependencies to the nightly build repo. Thanks for reporting, we're already on it. >>> >>> During the "Waiting for the host to become operational in the engine" >>> stage, the hosted-engine-setup fails because of the following VDSM >>> requirement: >>> >>>"VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for >>>clusterLevel >= 3.6 is disabled. For Fedora 20 users, please consider >>>upgrading >>>libvirt from the virt-preview repository" >>> >>> According to [1], libvirt version >= 1.2.3 is required. >>> >>> Any suggestion where to get this packages + dependencies for CentOS 7? >> >> Francesco? > > I need to check/start a few discussions, but most likely we'll need Centos > 7.1. > I'm not aware of any (reliable) repos like virt-preview for Centos. > > Bottom line: for hosted engine we may need to revert the patch requiring > AUTO_CONVERGE. > So unfortunate. Why? Just get the right libvirt from anywhere in the interim period. Centos 7.1 is going to be released any day now Thanks, michal > > -- > Francesco Romani > RedHat Engineering Virtualization R & D > Phone: 8261328 > IRC: fromani > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Hi, - Original Message - > From: "Sandro Bonazzola" > To: "Christopher Pereira" , devel@ovirt.org, "Francesco > Romani" > Sent: Thursday, March 26, 2015 9:05:02 AM > Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM > requirements > > Il 26/03/2015 08:56, Christopher Pereira ha scritto: > > > > On 25-03-2015 10:07, Sandro Bonazzola wrote: > >> Il 25/03/2015 14:05, Christopher Pereira ha scritto: > >>> [...] > >>> Maybe you want to add some more dependencies to the nightly build repo. > >> Thanks for reporting, we're already on it. > > > > During the "Waiting for the host to become operational in the engine" > > stage, the hosted-engine-setup fails because of the following VDSM > > requirement: > > > > "VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for > > clusterLevel >= 3.6 is disabled. For Fedora 20 users, please consider > > upgrading > > libvirt from the virt-preview repository" > > > > According to [1], libvirt version >= 1.2.3 is required. > > > > Any suggestion where to get this packages + dependencies for CentOS 7? > > Francesco? I need to check/start a few discussions, but most likely we'll need Centos 7.1. I'm not aware of any (reliable) repos like virt-preview for Centos. Bottom line: for hosted engine we may need to revert the patch requiring AUTO_CONVERGE. So unfortunate. -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Il 26/03/2015 08:56, Christopher Pereira ha scritto: > > On 25-03-2015 10:07, Sandro Bonazzola wrote: >> Il 25/03/2015 14:05, Christopher Pereira ha scritto: >>> [...] >>> Maybe you want to add some more dependencies to the nightly build repo. >> Thanks for reporting, we're already on it. > > During the "Waiting for the host to become operational in the engine" stage, > the hosted-engine-setup fails because of the following VDSM requirement: > > "VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for clusterLevel > >= 3.6 is disabled. For Fedora 20 users, please consider upgrading > libvirt from the virt-preview repository" > > According to [1], libvirt version >= 1.2.3 is required. > > Any suggestion where to get this packages + dependencies for CentOS 7? Francesco? > > __ > > [1] http://lists.ovirt.org/pipermail/infra/2015-February/009199.html -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
On 25-03-2015 10:07, Sandro Bonazzola wrote: Il 25/03/2015 14:05, Christopher Pereira ha scritto: [...] Maybe you want to add some more dependencies to the nightly build repo. Thanks for reporting, we're already on it. During the "Waiting for the host to become operational in the engine" stage, the hosted-engine-setup fails because of the following VDSM requirement: "VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for clusterLevel >= 3.6 is disabled. For Fedora 20 users, please consider upgrading libvirt from the virt-preview repository" According to [1], libvirt version >= 1.2.3 is required. Any suggestion where to get this packages + dependencies for CentOS 7? __ [1] http://lists.ovirt.org/pipermail/infra/2015-February/009199.html ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
