[ovirt-devel] Non Responding Treatment not working?

I have seen 2 diferent installations not moving a host to non responsive. One host was failing to install and stayed in "Installing" and on my setup a host just stays in "Connecting" and the treatment doesn't kick in. Anyone seen this? ___ Devel mailing

Re: [ovirt-devel] Non Responding Treatment not working?

- Original Message - > From: "Roy Golan" > To: "Martin Perina" > Cc: "devel" , "masayag" > Sent: Wednesday, January 13, 2016 9:17:11 AM > Subject: Re: Non Responding Treatment not working? > > On Wed, Jan 13,

Re: [ovirt-devel] No more "vds group" in master code , instead please use "cluster"

+1 Great job! --- Shirly Radco BI Software Engineer Red Hat Israel Ltd. - Original Message - > From: "Yaniv Dary" > To: "Eli Mesika" > Cc: "devel" > Sent: Wednesday, January 13, 2016 1:12:43 AM > Subject: Re: [ovirt-devel] No

Re: [ovirt-devel] Non Responding Treatment not working?

On Wed, Jan 13, 2016 at 10:19 AM, Martin Perina wrote: > > > - Original Message - > > From: "Roy Golan" > > To: "Martin Perina" > > Cc: "devel" , "masayag" > > Sent: Wednesday, January 13,

Re: [ovirt-devel] Non Responding Treatment not working?

- Original Message - > From: "Roy Golan" > To: "Martin Perina" > Cc: "devel" , "masayag" > Sent: Wednesday, January 13, 2016 9:28:22 AM > Subject: Re: Non Responding Treatment not working? > > On Wed, Jan 13,

Re: [ovirt-devel] Summary for Vdsm sync 12.1

On Tue, Jan 12, 2016 at 5:15 PM, Yaniv Bronheim wrote: > (edwad, nsoffer, pkliczew, alitke, fromani, ybronhei) > > Python3 current work and gaps - > https://docs.google.com/a/redhat.com/spreadsheets/d/180F-C1jU54ajUn7TuR-NwrKRZY1IiZI1Z8U5HWbvEvM/edit?usp=sharing > Current

Re: [ovirt-devel] Non Responding Treatment not working?

I'm not aware of any errors in NonRespondingTreatment. Can I see logs? Martin - Original Message - > From: "Roy Golan" > To: "devel" > Cc: "masayag" , "Martin Perina" > Sent: Wednesday, January 13, 2016

Re: [ovirt-devel] Non Responding Treatment not working?

On Wed, Jan 13, 2016 at 10:09 AM, Martin Perina wrote: > I'm not aware of any errors in NonRespondingTreatment. Can I see logs? > > http://fpaste.org/310101/26729971/ > Martin > > - Original Message - > > From: "Roy Golan" > > To: "devel"

Re: [ovirt-devel] Non Responding Treatment not working?

On Wed, Jan 13, 2016 at 10:41 AM, Martin Perina wrote: > > > - Original Message - > > From: "Roy Golan" > > To: "Martin Perina" > > Cc: "devel" , "masayag" > > Sent: Wednesday, January 13,

[ovirt-devel] TransactionSupport during command validation

Hi, I wanted to draw your attention to something I found out while fixing a bug involving the use of transactions in commands. When calling a command using getBackend().runAction() when another transaction is open, by default the command will become part of the open transaction because by

[ovirt-devel] cpu profile permission error while editing/creating vm

Hi, If you get an error message like the following while editing/creating VM: """ User doesn't have permissions to assign the cpu profile ASFDS with id 3c990c63-8078-4916-bf18-f38596232a5a to VMs. """ Go to Clusters->choose your cluster-> cpu profiles in the subtab-> choose the any cpu

Re: [ovirt-devel] No more "vds group" in master code , instead please use "cluster"

Hi Eli, are db migration scripts supposed to handle this change? My `engine-setup` failed with following message in log: """ 2016-01-13 20:02:57 DEBUG otopi.ovirt_**FILTERED**_setup.**FILTERED**_common.database database.execute:172 Database: 'None', Statement: ' SELECT

Re: [ovirt-devel] No more "vds group" in master code , instead please use "cluster"

- Original Message - > From: "Jakub Niedermertl" > To: "Eli Mesika" > Cc: "devel" > Sent: Wednesday, January 13, 2016 9:18:57 PM > Subject: Re: [ovirt-devel] No more "vds group" in master code , instead > please use

Re: [ovirt-devel] Summary for Vdsm sync 12.1

On Wed, Jan 13, 2016 at 11:40 AM, Piotr Kliczewski wrote: > On Tue, Jan 12, 2016 at 5:15 PM, Yaniv Bronheim wrote: >> (edwad, nsoffer, pkliczew, alitke, fromani, ybronhei) >> >> Python3 current work and gaps - >>

[ovirt-devel] oVirt Node Upgrade Design

Hey, Douglas and I have been discussing how the oVirt Node upgrade can work in future with Node Next. The most obvious change is that upgrades will be delivered directly Node. Previously they've been pushed to Node by Engine. The updates will stay to be delivered in an rpm through yum

[ovirt-devel] [ANN] oVirt 3.6.2 Second Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 3.6.2 for testing, as of January 13th, 2016 This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux >= 7.2, CentOS Linux

[ovirt-devel] VARIANT_ID usage - with our without oVirt version?

Hey, we've now merged a patch [0] to use and populate the VARIANT and VARIANT_ID fields on Node. Currently the value is something like "ovirt-node-$BRANCH", i.e. "ovirt-node-master" or "ovirt-node-3.6". I'd like to question if we should include the oVirt version in the ID, or if we should just