Re: [ovirt-users] Prepare for version 4 of oVirt API

2016-05-05 Thread Juan Hernández
On 05/05/2016 11:34 AM, René Koch wrote: > On 05/04/2016 04:39 PM, Juan Hernández wrote: >> Hello all, >> >> For those of you that use oVirt API, I wanted to inform you that >> version 4 of oVirt will by default use a new version of the API, >> incompatible with the previous one. The previous

Re: [ovirt-users] Stale VM template

2016-05-05 Thread Bhaskarakiran
Hi Tomas, I have used unlock_entity.sh script to unlock the template. The setup is out now, will send out the logs once it is up. Thanks, Bhaskarakiran. On Thu, May 5, 2016 at 12:26 PM, Tomas Jelinek wrote: > Hi Bhaskarkairan, > > how long the template has been locked? >

[ovirt-users] Hosted engine on iscsi storage

2016-05-05 Thread Darran Carey
Hi All, I am trying to install the hosted engine on an iscsi target but get the following error: [root@virt-host01 ~]# hosted-engine --deploy ... --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. Please specify the storage you would like

Re: [ovirt-users] Hosted engine on iscsi storage

2016-05-05 Thread Simone Tiraboschi
On Thu, May 5, 2016 at 10:22 AM, Darran Carey wrote: > Hi All, > > I am trying to install the hosted engine on an iscsi target but get the > following error: > > [root@virt-host01 ~]# hosted-engine --deploy > ... > --== STORAGE CONFIGURATION ==-- > >

Re: [ovirt-users] Prepare for version 4 of oVirt API

2016-05-05 Thread René Koch
On 05/04/2016 04:39 PM, Juan Hernández wrote: Hello all, For those of you that use oVirt API, I wanted to inform you that version 4 of oVirt will by default use a new version of the API, incompatible with the previous one. The previous version will still be supported, but only for clients that

Re: [ovirt-users] Stale VM template

2016-05-05 Thread Tomas Jelinek
Hi Bhaskarkairan, how long the template has been locked? Could you please attach the logs (engine, vdsm) from the relevant time period? Thank you, Tomas - Original Message - > From: "Bhaskarakiran" > To: users@ovirt.org > Sent: Wednesday, May 4, 2016 6:58:26 PM >

Re: [ovirt-users] node unresponsive after reboot

2016-05-05 Thread Piotr Kliczewski
Cam, It is really hard to understand partial logs. Please send me directly full logs and I will analyze. Thanks, Piotr On Mon, May 2, 2016 at 4:35 PM, Cam Mac wrote: > Hi Piotr, > > Attached are the vdsm log, the engine log and the supervdsm log. I've > attached them as a

Re: [ovirt-users] node unresponsive after reboot

2016-05-05 Thread Campbell McLeay
No problem Piotr, I will send you the full logs shortly. Thanks, Campbell On 5 May 2016 at 11:37, Piotr Kliczewski wrote: > Cam, > > It is really hard to understand partial logs. Please send me directly > full logs and I will analyze. > > Thanks, > Piotr > > On Mon,

[ovirt-users] vdsmd and libvirtd services failed to start

2016-05-05 Thread Bhaskarakiran
Hi, I have a HCI setup running on 3 nodes and created 6 VM's. Was running IO (like dd and linux untar) on those VM's overnight. Next day i saw that for 2 of the nodes vdsmd and libvirtd services failed and if manually started, they don't come up. All the VM's state has changed to 'unknown' and

Re: [ovirt-users] node unresponsive after reboot

2016-05-05 Thread Cam Mac
To update the thread here after some offline discussion with Piotr, the problem was that vdsmd had stopped running and wasn't able to start. It wasn't reported in the logs that I could see, but I noticed it after trying to restart it at Piotr's suggestion, after running a 'systemctl'. A

Re: [ovirt-users] Hosted engine on iscsi storage

2016-05-05 Thread Simone Tiraboschi
On Thu, May 5, 2016 at 2:35 PM, Darran Carey wrote: > Hi Simone, > > Please find the log files attached. Thank you very much for taking the time > to look at this problem. > > Regards, > Darran. Indeed VDSM is returning an empty device list:

Re: [ovirt-users] Hosted engine on iscsi storage

2016-05-05 Thread Darran Carey
Hi Simone, The output from the vdsClient command is: [root@virt-host01 ~]# vdsClient -s 0 getVdsCaps | grep ISCSIInitiatorName ISCSIInitiatorName = 'iqn.2016-04.au.org.pawsey:initiator01' The ACL on the PS4000 is as follows: ID Initiator Ipaddress

Re: [ovirt-users] Hosted engine on iscsi storage

2016-05-05 Thread Darran Carey
Unfortunately I get the same result when using CHAP. Darran. On 2016-05-05 23:06, Darran Carey wrote: Hi Simone, The output from the vdsClient command is: [root@virt-host01 ~]# vdsClient -s 0 getVdsCaps | grep ISCSIInitiatorName ISCSIInitiatorName =