Re: [ovirt-devel] Where's ovirt-release-master RPM on resources.ovirt.org ?

On Wed, Mar 9, 2016 at 8:17 AM, Yedidyah Bar David wrote: > On Tue, Mar 8, 2016 at 11:38 PM, Yaniv Kaul wrote: > > I can find it @ > > >

Re: [ovirt-devel] Where's ovirt-release-master RPM on resources.ovirt.org ?

On Tue, Mar 8, 2016 at 11:38 PM, Yaniv Kaul wrote: > I can find it @ > http://rsync.nl.gentoo.org/pub/software/ovirt/ovirt-master-snapshot/rpm/el7Workstation/noarch/ovirt-release-master-4.0.0-0.1.master.20160304151417.gita200923.noarch.rpm Not sure what's this one - perhaps

[ovirt-devel] Where's ovirt-release-master RPM on resources.ovirt.org ?

I can find it @ http://rsync.nl.gentoo.org/pub/software/ovirt/ovirt-master-snapshot/rpm/el7Workstation/noarch/ovirt-release-master-4.0.0-0.1.master.20160304151417.gita200923.noarch.rpm I can't find it @ http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/el7Workstation/noarch/

Re: [ovirt-devel] [VDSM] check_merged failures

On 03/08 18:42, Sandro Bonazzola wrote: > Adding infra This was already discussed on the lago-devel list, it has been fixed already (later than 147th build) > Il 08/Mar/2016 15:34, "Nir Soffer" ha scritto: > > > Hi all, > > > > The new check_merged job is failing randomly.

Re: [ovirt-devel] [VDSM] check_merged failures

Adding infra Il 08/Mar/2016 15:34, "Nir Soffer" ha scritto: > Hi all, > > The new check_merged job is failing randomly. I have see this error today: > > 14:20:16 @ Start specified VMs: > 14:20:16 # Start nets: > 14:20:16 * Create network vdsm_functional_tests_lago: >

Re: [ovirt-devel] Welcome: New ovirt.org website!

Thanks Rene for the heads up! As I wrote, we welcome contributions, so if you have the bandwidth to submit a PR with fixing the links it would be really helpful. Otherwise, please open an issue for this on GitHub and we'll try to route the task accordingly :) Cheers, Mikey On 03/03/2016 03:53

[ovirt-devel] [VDSM] check_merged failures

Hi all, The new check_merged job is failing randomly. I have see this error today: 14:20:16 @ Start specified VMs: 14:20:16 # Start nets: 14:20:16 * Create network vdsm_functional_tests_lago: 14:20:16 libvirt: error : internal error: Network is already in use by interface 7f0c-bc616ef

Re: [ovirt-devel] Failing to attach iso domain to master engine

On Tue, Mar 8, 2016 at 3:12 PM, Nir Soffer wrote: > Please attach vdsm logs showing this flow. > > corresponding vdsm log: jsonrpc.Executor/3::DEBUG::2016-03-08 15:04:28,449::__init__::509::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'StoragePool.connectStorageServer' in

Re: [ovirt-devel] node-iso for 3.6

Hey Dobo, you can find the ISO here: http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/ - fabian On Tue, Mar 8, 2016 at 11:40 AM, Dobó László wrote: > Hi, > > I didn't find any node iso for ovirt 3.6, which one is recommended for > installation ? >

Re: [ovirt-devel] [VDSM] STOMP tests failures

Sure, will take a look. I suspect timing issue in the test. Thanks, Piotr 2016-03-08 14:55 GMT+01:00 Nir Soffer : > Hi all, > > We are seeing the following error randomly - there must be a timing > issue in the test, > or maybe in the code? > > Pitor, can you check this? >

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

- Original Message - > From: "Yaniv Bronheim" > To: "Sandro Bonazzola" > Cc: "Dan Kenigsberg" , "Nir Soffer" , > "Martin Perina" , > "Francesco Romani" , "devel"

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

latest is 4.17.19 right? so where we test latest 3.6 we checkout ovirt-3.6 branch, build the rpms and install them - can we do it when we disable the stable repository and remove the current installed version? Its either that, or each tag to stable will follow tag to latest 3.6 which will be

[ovirt-devel] [oVirt jenkins] Weekly report on open tasks for ovirt-engine

Files scanned: '**/*.java, **/*.py'. Strings searched: FIXME | TODO | @deprecated Report: http://jenkins.ovirt.org/job/ovirt-engine_master_scan-open-tasks_merged//45/tasksResult/?___ Devel mailing list Devel@ovirt.org

Re: [ovirt-devel] How can users use oVirtCli to complete "run once"?

On 03/08/2016 10:14 AM, Sandro Bonazzola wrote: > > > On Mon, Feb 29, 2016 at 8:21 AM, zhukaijie > wrote: > > As you know. In web, users can use "RUN ONCE" button to run a VM > with some params (such as certain custom properties). But can >

Re: [ovirt-devel] How can users use oVirtCli to complete "run once"?

On Mon, Feb 29, 2016 at 8:21 AM, zhukaijie wrote: > As you know. In web, users can use "RUN ONCE" button to run a VM with some > params (such as certain custom properties). But can oVirtCli be used to > complete "RUN ONCE"? Thank you. > Juan? >

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

- Original Message - > From: "Yaniv Bronheim" > To: "Sandro Bonazzola" > Cc: "Dan Kenigsberg" , "Nir Soffer" , > "Martin Perina" , > "Francesco Romani" , "devel"

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

On Tue, Mar 8, 2016 at 9:45 AM, Yaniv Bronheim wrote: > No. the jobs alright. ovirt-3.6 build each night will output vdsm 4.17.19. > older version than the build for ovirt-3.6.3 which will raise (currently > 4.17.23). That's all we wanted, no ? once 3.6.3 will end, ovirt-3.6

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

No. the jobs alright. ovirt-3.6 build each night will output vdsm 4.17.19. older version than the build for ovirt-3.6.3 which will raise (currently 4.17.23). That's all we wanted, no ? once 3.6.3 will end, ovirt-3.6 new tag will be the newer version for users that want it On Tue, Mar 8, 2016 at

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

On Tue, Mar 8, 2016 at 9:07 AM, Yaniv Bronheim wrote: > its reasonable that you can't upgrade 4.17.23 to 4.17.19 and it shouldn't > be that way.. latest (which afaiu means latest snapshot? ovirt-3.6.3) > should get higher numbering than last stable (which should be last tag

Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

its reasonable that you can't upgrade 4.17.23 to 4.17.19 and it shouldn't be that way.. latest (which afaiu means latest snapshot? ovirt-3.6.3) should get higher numbering than last stable (which should be last tag on ovirt-3.6 branch). in other words, tags in ovirt-3.6.3 must be newer than tags