Re: [Users] oVirt and iSCSI initiator

2013-06-17 Thread James James 
Yes there was an output.
This one :

192.68.0.98:3260,1 iqn.2013-05.com.example:target0





2013/6/18 Dan Yasny 

>
> On Mon, Jun 17, 2013 at 3:51 PM, James James  wrote:
>
>> # iscsiadm -m discovery -t sendtargets -p iscsi-1.example.com
>>
>>
> Was there no output when you ran this?
>
>
>> # iscsiadm -m node -Piqn.2013-05.com.example:target0:3260 --login
>>
>> dmesg gives me :
>>
>> scsi 17:0:0:0: RAID  IET  Controller   0001 PQ: 0
>> ANSI: 5
>> scsi 17:0:0:0: Attached scsi generic sg4 type 12
>> scsi 17:0:0:1: Direct-Access IET  VIRTUAL-DISK 0001 PQ: 0
>> ANSI: 5
>> sd 17:0:0:1: Attached scsi generic sg5 type 0
>> sd 17:0:0:1: [sdc] 52428800 512-byte logical blocks: (26.8 GB/25.0 GiB)
>> sd 17:0:0:1: [sdc] Write Protect is off
>> sd 17:0:0:1: [sdc] Mode Sense: 49 00 00 08
>> sd 17:0:0:1: [sdc] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>>  sdc: unknown partition table
>> sd 17:0:0:1: [sdc] Attached SCSI disk
>> sd 16:0:0:1: [sdb] Synchronizing SCSI cache
>> sd 17:0:0:1: [sdc] Synchronizing SCSI cache
>>  connection12:0: detected conn error (1020)
>>  connection11:0: detected conn error (1020)
>> SELinux: 2048 avtab hash slots, 278248 rules.
>> SELinux: 2048 avtab hash slots, 278248 rules.
>>
>>
>>
>> 2013/6/17 Dan Yasny 
>>
>>> how exactly did you run the iscsiadm commands that worked? The error
>>> clearly shows iscsiadm discovery failing
>>>
>>>
>>> On Mon, Jun 17, 2013 at 11:10 AM, James James  wrote:
>>>
 Thanks for your answer. I did it already : everything is ok with iscsi
 daemon. It can login and see the LUN.


 2013/6/17 Dan Yasny 

> I would manually probe with iscsiadm, looks like it's failing there
>
>  On Mon, Jun 17, 2013 at 9:50 AM, James James wrote:
>
>>   Hi guys,
>>
>> I've got some problems with my ovirt-engine. Currently I have one
>> iscsi storage volume and I want add a second one. The second has the same
>> configuration as the first. In my engine I can log into the iSCSI but I
>> cannot see the LUN. Ovirt gives me this message :
>>
>> 2013-06-17 15:50:04,013 ERROR
>> [org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery]
>> (ajp--127.0.0.1-8702-9) Query DiscoverSendTargetsQuery failed. Exception
>> message is VdcBLLException:
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
>> VDSGenericException: VDSErrorException: Failed in vdscommand to
>> DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets:
>> "portal=IscsiPortal(hostname='iscsi-1.example.com', port=3260),
>> err=(5, [], ['iscsiadm: Connection to Discovery Address 192.168.0.98
>> closed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
>> retrying discovery login to 192.168.0.98', 'iscsiadm: Connection to
>> Discovery Address 192.168.0.98 closed', 'iscsiadm: Login I/O error, 
>> failed
>> to receive a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98',
>> 'iscsiadm: Connection to Discovery Address 192.168.0.98 closed', 
>> 'iscsiadm:
>> Login I/O error, failed to receive a PDU', 'iscsiadm: retrying discovery
>> login to 192.168.0.98', 'iscsiadm: Connection to Discovery Address
>> 192.168.0.98 failed', 'iscsiadm: Login I/O error, failed to receive a 
>> PDU',
>> 'iscsiadm: retrying discovery login to 192.168.0.98', 'iscsiadm: 
>> Connection
>> to Discovery Address 192.168.0.98 failed', 'iscsiadm: Login I/O error,
>> failed to receive a PDU', 'iscsiadm: retrying discovery login to
>> 192.168.0.98', 'iscsiadm: Connection to Discovery Address 192.168.0.98
>> closed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
>> retrying discovery login to 192.168.0.98', 'iscsiadm: connection login
>> retries (reopen_max) 5 exceeded', 'iscsiadm: Could not perform 
>> SendTargets
>> discovery: encountered iSCSI login failure'])"
>> 2013-06-17 15:54:03,649 INFO
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand]
>> (ajp--127.0.0.1-8702-3) START, DiscoverSendTargetsVDSCommand(HostName =
>> hosts-1.example.com, HostId = 1c8e67de-c355-4b07-a09f-c58d08115e1e,
>> connection={ id: null, connection: iscsi-1.example.com, iqn: null,
>> vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null,
>> nfsTimeo: null };), log id: 3dca76fc
>>
>>
>> Can somebody help me ?
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>

>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt and iSCSI initiator

2013-06-17 Thread Dan Yasny 
On Mon, Jun 17, 2013 at 3:51 PM, James James  wrote:

> # iscsiadm -m discovery -t sendtargets -p iscsi-1.example.com
>
>
Was there no output when you ran this?


> # iscsiadm -m node -Piqn.2013-05.com.example:target0:3260 --login
>
> dmesg gives me :
>
> scsi 17:0:0:0: RAID  IET  Controller   0001 PQ: 0
> ANSI: 5
> scsi 17:0:0:0: Attached scsi generic sg4 type 12
> scsi 17:0:0:1: Direct-Access IET  VIRTUAL-DISK 0001 PQ: 0
> ANSI: 5
> sd 17:0:0:1: Attached scsi generic sg5 type 0
> sd 17:0:0:1: [sdc] 52428800 512-byte logical blocks: (26.8 GB/25.0 GiB)
> sd 17:0:0:1: [sdc] Write Protect is off
> sd 17:0:0:1: [sdc] Mode Sense: 49 00 00 08
> sd 17:0:0:1: [sdc] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
>  sdc: unknown partition table
> sd 17:0:0:1: [sdc] Attached SCSI disk
> sd 16:0:0:1: [sdb] Synchronizing SCSI cache
> sd 17:0:0:1: [sdc] Synchronizing SCSI cache
>  connection12:0: detected conn error (1020)
>  connection11:0: detected conn error (1020)
> SELinux: 2048 avtab hash slots, 278248 rules.
> SELinux: 2048 avtab hash slots, 278248 rules.
>
>
>
> 2013/6/17 Dan Yasny 
>
>> how exactly did you run the iscsiadm commands that worked? The error
>> clearly shows iscsiadm discovery failing
>>
>>
>> On Mon, Jun 17, 2013 at 11:10 AM, James James  wrote:
>>
>>> Thanks for your answer. I did it already : everything is ok with iscsi
>>> daemon. It can login and see the LUN.
>>>
>>>
>>> 2013/6/17 Dan Yasny 
>>>
 I would manually probe with iscsiadm, looks like it's failing there

  On Mon, Jun 17, 2013 at 9:50 AM, James James  wrote:

>   Hi guys,
>
> I've got some problems with my ovirt-engine. Currently I have one
> iscsi storage volume and I want add a second one. The second has the same
> configuration as the first. In my engine I can log into the iSCSI but I
> cannot see the LUN. Ovirt gives me this message :
>
> 2013-06-17 15:50:04,013 ERROR
> [org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery]
> (ajp--127.0.0.1-8702-9) Query DiscoverSendTargetsQuery failed. Exception
> message is VdcBLLException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
> VDSGenericException: VDSErrorException: Failed in vdscommand to
> DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets:
> "portal=IscsiPortal(hostname='iscsi-1.example.com', port=3260),
> err=(5, [], ['iscsiadm: Connection to Discovery Address 192.168.0.98
> closed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
> retrying discovery login to 192.168.0.98', 'iscsiadm: Connection to
> Discovery Address 192.168.0.98 closed', 'iscsiadm: Login I/O error, failed
> to receive a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98',
> 'iscsiadm: Connection to Discovery Address 192.168.0.98 closed', 
> 'iscsiadm:
> Login I/O error, failed to receive a PDU', 'iscsiadm: retrying discovery
> login to 192.168.0.98', 'iscsiadm: Connection to Discovery Address
> 192.168.0.98 failed', 'iscsiadm: Login I/O error, failed to receive a 
> PDU',
> 'iscsiadm: retrying discovery login to 192.168.0.98', 'iscsiadm: 
> Connection
> to Discovery Address 192.168.0.98 failed', 'iscsiadm: Login I/O error,
> failed to receive a PDU', 'iscsiadm: retrying discovery login to
> 192.168.0.98', 'iscsiadm: Connection to Discovery Address 192.168.0.98
> closed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
> retrying discovery login to 192.168.0.98', 'iscsiadm: connection login
> retries (reopen_max) 5 exceeded', 'iscsiadm: Could not perform SendTargets
> discovery: encountered iSCSI login failure'])"
> 2013-06-17 15:54:03,649 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand]
> (ajp--127.0.0.1-8702-3) START, DiscoverSendTargetsVDSCommand(HostName =
> hosts-1.example.com, HostId = 1c8e67de-c355-4b07-a09f-c58d08115e1e,
> connection={ id: null, connection: iscsi-1.example.com, iqn: null,
> vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null,
> nfsTimeo: null };), log id: 3dca76fc
>
>
> Can somebody help me ?
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>

>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt and iSCSI initiator

2013-06-17 Thread James James 
# iscsiadm -m discovery -t sendtargets -p iscsi-1.example.com

# iscsiadm -m node -Piqn.2013-05.com.example:target0:3260 --login

dmesg gives me :

scsi 17:0:0:0: RAID  IET  Controller   0001 PQ: 0 ANSI:
5
scsi 17:0:0:0: Attached scsi generic sg4 type 12
scsi 17:0:0:1: Direct-Access IET  VIRTUAL-DISK 0001 PQ: 0 ANSI:
5
sd 17:0:0:1: Attached scsi generic sg5 type 0
sd 17:0:0:1: [sdc] 52428800 512-byte logical blocks: (26.8 GB/25.0 GiB)
sd 17:0:0:1: [sdc] Write Protect is off
sd 17:0:0:1: [sdc] Mode Sense: 49 00 00 08
sd 17:0:0:1: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sdc: unknown partition table
sd 17:0:0:1: [sdc] Attached SCSI disk
sd 16:0:0:1: [sdb] Synchronizing SCSI cache
sd 17:0:0:1: [sdc] Synchronizing SCSI cache
 connection12:0: detected conn error (1020)
 connection11:0: detected conn error (1020)
SELinux: 2048 avtab hash slots, 278248 rules.
SELinux: 2048 avtab hash slots, 278248 rules.



2013/6/17 Dan Yasny 

> how exactly did you run the iscsiadm commands that worked? The error
> clearly shows iscsiadm discovery failing
>
>
> On Mon, Jun 17, 2013 at 11:10 AM, James James  wrote:
>
>> Thanks for your answer. I did it already : everything is ok with iscsi
>> daemon. It can login and see the LUN.
>>
>>
>> 2013/6/17 Dan Yasny 
>>
>>> I would manually probe with iscsiadm, looks like it's failing there
>>>
>>>  On Mon, Jun 17, 2013 at 9:50 AM, James James  wrote:
>>>
   Hi guys,

 I've got some problems with my ovirt-engine. Currently I have one iscsi
 storage volume and I want add a second one. The second has the same
 configuration as the first. In my engine I can log into the iSCSI but I
 cannot see the LUN. Ovirt gives me this message :

 2013-06-17 15:50:04,013 ERROR
 [org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery]
 (ajp--127.0.0.1-8702-9) Query DiscoverSendTargetsQuery failed. Exception
 message is VdcBLLException:
 org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
 VDSGenericException: VDSErrorException: Failed in vdscommand to
 DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets:
 "portal=IscsiPortal(hostname='iscsi-1.example.com', port=3260),
 err=(5, [], ['iscsiadm: Connection to Discovery Address 192.168.0.98
 closed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
 retrying discovery login to 192.168.0.98', 'iscsiadm: Connection to
 Discovery Address 192.168.0.98 closed', 'iscsiadm: Login I/O error, failed
 to receive a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98',
 'iscsiadm: Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm:
 Login I/O error, failed to receive a PDU', 'iscsiadm: retrying discovery
 login to 192.168.0.98', 'iscsiadm: Connection to Discovery Address
 192.168.0.98 failed', 'iscsiadm: Login I/O error, failed to receive a PDU',
 'iscsiadm: retrying discovery login to 192.168.0.98', 'iscsiadm: Connection
 to Discovery Address 192.168.0.98 failed', 'iscsiadm: Login I/O error,
 failed to receive a PDU', 'iscsiadm: retrying discovery login to
 192.168.0.98', 'iscsiadm: Connection to Discovery Address 192.168.0.98
 closed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
 retrying discovery login to 192.168.0.98', 'iscsiadm: connection login
 retries (reopen_max) 5 exceeded', 'iscsiadm: Could not perform SendTargets
 discovery: encountered iSCSI login failure'])"
 2013-06-17 15:54:03,649 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand]
 (ajp--127.0.0.1-8702-3) START, DiscoverSendTargetsVDSCommand(HostName =
 hosts-1.example.com, HostId = 1c8e67de-c355-4b07-a09f-c58d08115e1e,
 connection={ id: null, connection: iscsi-1.example.com, iqn: null,
 vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null,
 nfsTimeo: null };), log id: 3dca76fc


 Can somebody help me ?


 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Ovirt VM CD/DVD not booting

2013-06-17 Thread Rick Ingersoll 
That did the trick.  Thanks for the help.

Rick Ingersoll
IT Consultant
(919) 234-5100 main
(919) 234-5101 direct
(919) 757-5605 mobile
(919) 747-7409 fax
rick.ingers...@mjritsolutions.com
http://www.mjritsolutions.com
[mjritsolutions_logo_signature]

From: Ryan Wilkinson [mailto:ryanw...@gmail.com]
Sent: Monday, June 17, 2013 3:04 PM
To: Rick Ingersoll
Cc: users@ovirt.org
Subject: Re: [Users] Ovirt VM CD/DVD not booting

Rick,
I've had that happen a couple times lately myself.  The only way I could get 
them to boot was shutdown vms, put host in maintenance, and reboot server.  
Then they worked fine..

On Mon, Jun 17, 2013 at 11:39 AM, Rick Ingersoll 
mailto:rick.ingers...@mjritsolutions.com>> 
wrote:
Hi guys,
I have an issue where I have an allinone setup.  I was 
successful in building one VM, but now when I try to add additional vms and 
boot them, the ISO image I attach in run once isn't booting.  The VM is coming 
up saying could not read from CDROM.  Any ideas what I'm missing?

Thanks,

Rick Ingersoll
IT Consultant
(919) 234-5100 main
(919) 234-5101 direct
(919) 757-5605 mobile
(919) 747-7409 fax
rick.ingers...@mjritsolutions.com
http://www.mjritsolutions.com


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

<>___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Ovirt VM CD/DVD not booting

2013-06-17 Thread Ryan Wilkinson 
Rick,

I've had that happen a couple times lately myself.  The only way I could
get them to boot was shutdown vms, put host in maintenance, and reboot
server.  Then they worked fine..


On Mon, Jun 17, 2013 at 11:39 AM, Rick Ingersoll <
rick.ingers...@mjritsolutions.com> wrote:

>  Hi guys,
>
> I have an issue where I have an allinone setup.  I was
> successful in building one VM, but now when I try to add additional vms and
> boot them, the ISO image I attach in run once isn’t booting.  The VM is
> coming up saying could not read from CDROM.  Any ideas what I’m missing?**
> **
>
> ** **
>
> Thanks,
>
> ** **
>
> *Rick Ingersoll*
>
> *IT Consultant*
>
> (919) 234-5100 main
>
> (919) 234-5101 direct
>
> (919) 757-5605 mobile
>
> (919) 747-7409 fax
>
> rick.ingers...@mjritsolutions.com
>
> http://www.mjritsolutions.com
>
> [image: mjritsolutions_logo_signature]
>
> ** **
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt and iSCSI initiator

2013-06-17 Thread Dan Yasny 
how exactly did you run the iscsiadm commands that worked? The error
clearly shows iscsiadm discovery failing

On Mon, Jun 17, 2013 at 11:10 AM, James James  wrote:

> Thanks for your answer. I did it already : everything is ok with iscsi
> daemon. It can login and see the LUN.
>
>
> 2013/6/17 Dan Yasny 
>
>> I would manually probe with iscsiadm, looks like it's failing there
>>
>>  On Mon, Jun 17, 2013 at 9:50 AM, James James  wrote:
>>
>>>   Hi guys,
>>>
>>> I've got some problems with my ovirt-engine. Currently I have one iscsi
>>> storage volume and I want add a second one. The second has the same
>>> configuration as the first. In my engine I can log into the iSCSI but I
>>> cannot see the LUN. Ovirt gives me this message :
>>>
>>> 2013-06-17 15:50:04,013 ERROR
>>> [org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery]
>>> (ajp--127.0.0.1-8702-9) Query DiscoverSendTargetsQuery failed. Exception
>>> message is VdcBLLException:
>>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
>>> VDSGenericException: VDSErrorException: Failed in vdscommand to
>>> DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets:
>>> "portal=IscsiPortal(hostname='iscsi-1.example.com', port=3260), err=(5,
>>> [], ['iscsiadm: Connection to Discovery Address 192.168.0.98 closed',
>>> 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm: retrying
>>> discovery login to 192.168.0.98', 'iscsiadm: Connection to Discovery
>>> Address 192.168.0.98 closed', 'iscsiadm: Login I/O error, failed to receive
>>> a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98', 'iscsiadm:
>>> Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm: Login I/O
>>> error, failed to receive a PDU', 'iscsiadm: retrying discovery login to
>>> 192.168.0.98', 'iscsiadm: Connection to Discovery Address 192.168.0.98
>>> failed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
>>> retrying discovery login to 192.168.0.98', 'iscsiadm: Connection to
>>> Discovery Address 192.168.0.98 failed', 'iscsiadm: Login I/O error, failed
>>> to receive a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98',
>>> 'iscsiadm: Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm:
>>> Login I/O error, failed to receive a PDU', 'iscsiadm: retrying discovery
>>> login to 192.168.0.98', 'iscsiadm: connection login retries (reopen_max) 5
>>> exceeded', 'iscsiadm: Could not perform SendTargets discovery: encountered
>>> iSCSI login failure'])"
>>> 2013-06-17 15:54:03,649 INFO
>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand]
>>> (ajp--127.0.0.1-8702-3) START, DiscoverSendTargetsVDSCommand(HostName =
>>> hosts-1.example.com, HostId = 1c8e67de-c355-4b07-a09f-c58d08115e1e,
>>> connection={ id: null, connection: iscsi-1.example.com, iqn: null,
>>> vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null,
>>> nfsTimeo: null };), log id: 3dca76fc
>>>
>>>
>>> Can somebody help me ?
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] Ovirt VM CD/DVD not booting

2013-06-17 Thread Rick Ingersoll 
Hi guys,
I have an issue where I have an allinone setup.  I was 
successful in building one VM, but now when I try to add additional vms and 
boot them, the ISO image I attach in run once isn't booting.  The VM is coming 
up saying could not read from CDROM.  Any ideas what I'm missing?

Thanks,

Rick Ingersoll
IT Consultant
(919) 234-5100 main
(919) 234-5101 direct
(919) 757-5605 mobile
(919) 747-7409 fax
rick.ingers...@mjritsolutions.com
http://www.mjritsolutions.com
[mjritsolutions_logo_signature]

<>___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt and iSCSI initiator

2013-06-17 Thread James James 
Thanks for your answer. I did it already : everything is ok with iscsi
daemon. It can login and see the LUN.


2013/6/17 Dan Yasny 

> I would manually probe with iscsiadm, looks like it's failing there
>
> On Mon, Jun 17, 2013 at 9:50 AM, James James  wrote:
>
>>  Hi guys,
>>
>> I've got some problems with my ovirt-engine. Currently I have one iscsi
>> storage volume and I want add a second one. The second has the same
>> configuration as the first. In my engine I can log into the iSCSI but I
>> cannot see the LUN. Ovirt gives me this message :
>>
>> 2013-06-17 15:50:04,013 ERROR
>> [org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery]
>> (ajp--127.0.0.1-8702-9) Query DiscoverSendTargetsQuery failed. Exception
>> message is VdcBLLException:
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
>> VDSGenericException: VDSErrorException: Failed in vdscommand to
>> DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets:
>> "portal=IscsiPortal(hostname='iscsi-1.example.com', port=3260), err=(5,
>> [], ['iscsiadm: Connection to Discovery Address 192.168.0.98 closed',
>> 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm: retrying
>> discovery login to 192.168.0.98', 'iscsiadm: Connection to Discovery
>> Address 192.168.0.98 closed', 'iscsiadm: Login I/O error, failed to receive
>> a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98', 'iscsiadm:
>> Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm: Login I/O
>> error, failed to receive a PDU', 'iscsiadm: retrying discovery login to
>> 192.168.0.98', 'iscsiadm: Connection to Discovery Address 192.168.0.98
>> failed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
>> retrying discovery login to 192.168.0.98', 'iscsiadm: Connection to
>> Discovery Address 192.168.0.98 failed', 'iscsiadm: Login I/O error, failed
>> to receive a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98',
>> 'iscsiadm: Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm:
>> Login I/O error, failed to receive a PDU', 'iscsiadm: retrying discovery
>> login to 192.168.0.98', 'iscsiadm: connection login retries (reopen_max) 5
>> exceeded', 'iscsiadm: Could not perform SendTargets discovery: encountered
>> iSCSI login failure'])"
>> 2013-06-17 15:54:03,649 INFO
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand]
>> (ajp--127.0.0.1-8702-3) START, DiscoverSendTargetsVDSCommand(HostName =
>> hosts-1.example.com, HostId = 1c8e67de-c355-4b07-a09f-c58d08115e1e,
>> connection={ id: null, connection: iscsi-1.example.com, iqn: null,
>> vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null,
>> nfsTimeo: null };), log id: 3dca76fc
>>
>>
>> Can somebody help me ?
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt and iSCSI initiator

2013-06-17 Thread Dan Yasny 
I would manually probe with iscsiadm, looks like it's failing there

On Mon, Jun 17, 2013 at 9:50 AM, James James  wrote:

>  Hi guys,
>
> I've got some problems with my ovirt-engine. Currently I have one iscsi
> storage volume and I want add a second one. The second has the same
> configuration as the first. In my engine I can log into the iSCSI but I
> cannot see the LUN. Ovirt gives me this message :
>
> 2013-06-17 15:50:04,013 ERROR
> [org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery]
> (ajp--127.0.0.1-8702-9) Query DiscoverSendTargetsQuery failed. Exception
> message is VdcBLLException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
> VDSGenericException: VDSErrorException: Failed in vdscommand to
> DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets:
> "portal=IscsiPortal(hostname='iscsi-1.example.com', port=3260), err=(5,
> [], ['iscsiadm: Connection to Discovery Address 192.168.0.98 closed',
> 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm: retrying
> discovery login to 192.168.0.98', 'iscsiadm: Connection to Discovery
> Address 192.168.0.98 closed', 'iscsiadm: Login I/O error, failed to receive
> a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98', 'iscsiadm:
> Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm: Login I/O
> error, failed to receive a PDU', 'iscsiadm: retrying discovery login to
> 192.168.0.98', 'iscsiadm: Connection to Discovery Address 192.168.0.98
> failed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
> retrying discovery login to 192.168.0.98', 'iscsiadm: Connection to
> Discovery Address 192.168.0.98 failed', 'iscsiadm: Login I/O error, failed
> to receive a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98',
> 'iscsiadm: Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm:
> Login I/O error, failed to receive a PDU', 'iscsiadm: retrying discovery
> login to 192.168.0.98', 'iscsiadm: connection login retries (reopen_max) 5
> exceeded', 'iscsiadm: Could not perform SendTargets discovery: encountered
> iSCSI login failure'])"
> 2013-06-17 15:54:03,649 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand]
> (ajp--127.0.0.1-8702-3) START, DiscoverSendTargetsVDSCommand(HostName =
> hosts-1.example.com, HostId = 1c8e67de-c355-4b07-a09f-c58d08115e1e,
> connection={ id: null, connection: iscsi-1.example.com, iqn: null,
> vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null,
> nfsTimeo: null };), log id: 3dca76fc
>
>
> Can somebody help me ?
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] oVirt and iSCSI initiator

2013-06-17 Thread James James 
Hi guys,

I've got some problems with my ovirt-engine. Currently I have one iscsi
storage volume and I want add a second one. The second has the same
configuration as the first. In my engine I can log into the iSCSI but I
cannot see the LUN. Ovirt gives me this message :

2013-06-17 15:50:04,013 ERROR
[org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery]
(ajp--127.0.0.1-8702-9) Query DiscoverSendTargetsQuery failed. Exception
message is VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
VDSGenericException: VDSErrorException: Failed in vdscommand to
DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets:
"portal=IscsiPortal(hostname='iscsi-1.example.com', port=3260), err=(5, [],
['iscsiadm: Connection to Discovery Address 192.168.0.98 closed',
'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm: retrying
discovery login to 192.168.0.98', 'iscsiadm: Connection to Discovery
Address 192.168.0.98 closed', 'iscsiadm: Login I/O error, failed to receive
a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98', 'iscsiadm:
Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm: Login I/O
error, failed to receive a PDU', 'iscsiadm: retrying discovery login to
192.168.0.98', 'iscsiadm: Connection to Discovery Address 192.168.0.98
failed', 'iscsiadm: Login I/O error, failed to receive a PDU', 'iscsiadm:
retrying discovery login to 192.168.0.98', 'iscsiadm: Connection to
Discovery Address 192.168.0.98 failed', 'iscsiadm: Login I/O error, failed
to receive a PDU', 'iscsiadm: retrying discovery login to 192.168.0.98',
'iscsiadm: Connection to Discovery Address 192.168.0.98 closed', 'iscsiadm:
Login I/O error, failed to receive a PDU', 'iscsiadm: retrying discovery
login to 192.168.0.98', 'iscsiadm: connection login retries (reopen_max) 5
exceeded', 'iscsiadm: Could not perform SendTargets discovery: encountered
iSCSI login failure'])"
2013-06-17 15:54:03,649 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand]
(ajp--127.0.0.1-8702-3) START, DiscoverSendTargetsVDSCommand(HostName =
hosts-1.example.com, HostId = 1c8e67de-c355-4b07-a09f-c58d08115e1e,
connection={ id: null, connection: iscsi-1.example.com, iqn: null, vfsType:
null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo:
null };), log id: 3dca76fc


Can somebody help me ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Booting oVirt CentOS nodes from PXE ?

2013-06-17 Thread Matt . 
Hi Matt,

Are you willing to share some information ? How do you build that CentOS
version and so on ?

Would be nice to now!

Thanks,

Matt


2013/6/17 Matt Curry 

>   Yeah it works fine; I do a LOT of them.
>   [image: Skopos Website]  *MATT CURRY * |
> Sr. Systems Administrator  | Skopos Web 
> *e:*  mcu...@skopos.us  *t:*  214.520.4600 x 5042  *f:*  214.520.5079 [image:
> LinkedIn]
>
>  
>
>   From: "Matt ." 
> Date: Monday, June 17, 2013 10:20 AM
> To: users 
> Subject: [Users] Booting oVirt CentOS nodes from PXE ?
>
>   Hi All,
>
> I'm wondering if it's possible to PXE boot nodes so we don't need to
> install every server on local disks.
>
>  I have read something in the docs about a Fedora ISO, but how does this
> work and will it be possible with CentOS ?
>
>  Thanks!
>
>  Cheers,
>
>  Matt
>
> --
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind SKOPOS to any order or other contract unless pursuant to explicit
> written agreement or government initiative expressly permitting the use of
> e-mail for such purpose.
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Booting oVirt CentOS nodes from PXE ?

2013-06-17 Thread Matt Curry 
Yeah it works fine; I do a LOT of them.
[Skopos Website]   MATT CURRY  | Sr. 
Systems Administrator  | Skopos Web
e:  mcu...@skopos.us  t:  214.520.4600 x 5042  f:  
214.520.5079 [LinkedIn]  


From: "Matt ." mailto:yamakasi@gmail.com>>
Date: Monday, June 17, 2013 10:20 AM
To: users mailto:users@ovirt.org>>
Subject: [Users] Booting oVirt CentOS nodes from PXE ?

Hi All,

I'm wondering if it's possible to PXE boot nodes so we don't need to install 
every server on local disks.

I have read something in the docs about a Fedora ISO, but how does this work 
and will it be possible with CentOS ?

Thanks!

Cheers,

Matt


This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to 
any order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] Booting oVirt CentOS nodes from PXE ?

2013-06-17 Thread Matt . 
Hi All,

I'm wondering if it's possible to PXE boot nodes so we don't need to
install every server on local disks.

I have read something in the docs about a Fedora ISO, but how does this
work and will it be possible with CentOS ?

Thanks!

Cheers,

Matt
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Small howto to install ovirt dreyou on Centos 6.4

2013-06-17 Thread Itamar Heim 

On 06/17/2013 05:10 PM, Kevin Maziere Aubry wrote:

Hi

For manager,

  *

yum install wget

  *

wget http://www.dreyou.org/ovirt/ovirt-dre.repo -P /etc/yum.repos.d/

  * yum install ovirt-engine


For hypervisor:
selinux and firewall are activated, DO NOT remove them
You must have a working dns between you nodes (if all-in-one it's ok),
at least put nameservers into /etc/hosts (hyp and manger)

  *

su -c 'rpm -Uvh

http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm'

  *

yum install wget

  *

wget http://www.dreyou.org/ovirt/ovirt-dre.repo -P /etc/yum.repos.d/

  *

yum clean all

  *

yum makecache

  * check that ifcfg-eth0 does not contain NETMASK and PREFIX, remove
PREFIX if needed
  * yum install vdsm
  * Ovirt node can now be added into the manager
  *

setsebool -P virt_use_sanlock=on

  * setsebool -P virt_use_nfs=on
  *

yum install vdsm-hook-qemucmdline vdsm-hook-fileinject vdsm-hook-floppy

  *

service vdsmd restart

Hope it can help.


Kevin



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



mostly for sake of my ignorance - is the dreyou repo maintained with 
patches post the 3.2.1 version which added .el6 support?

if so, why not doing so directly to the 3.2.x stable gerrit branch?

Thanks,
   Itamar
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] Small howto to install ovirt dreyou on Centos 6.4

2013-06-17 Thread Kevin Maziere Aubry 
Hi

For manager,

   -

   yum install wget
   -

   wget http://www.dreyou.org/ovirt/ovirt-dre.repo -P /etc/yum.repos.d/
   - yum install ovirt-engine


For hypervisor:
selinux and firewall are activated, DO NOT remove them
You must have a working dns between you nodes (if all-in-one it's ok), at
least put nameservers into /etc/hosts (hyp and manger)

   -

   su -c 'rpm -Uvh
   
http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
   '
   -

   yum install wget
   -

   wget http://www.dreyou.org/ovirt/ovirt-dre.repo -P /etc/yum.repos.d/
   -

   yum clean all
   -

   yum makecache
   - check that ifcfg-eth0 does not contain NETMASK and PREFIX, remove
   PREFIX if needed
   - yum install vdsm
   - Ovirt node can now be added into the manager
   -

   setsebool -P virt_use_sanlock=on
   - setsebool -P virt_use_nfs=on
   -

   yum install vdsm-hook-qemucmdline vdsm-hook-fileinject vdsm-hook-floppy
   -

   service vdsmd restart

Hope it can help.


Kevin
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer

2013-06-17 Thread Matt . 
Hi,

At the moment I have removed it as it was not possible to update:

  file /usr/share/ovirt-engine/services/config.pyc from install of
ovirt-engine-websocket-proxy-3.3.0-0.2.master.20130615222011.gitf92a4af.el6.noarch
conflicts with file from package
ovirt-engine-3.3.0-0.2.master.20130609231551.gitc493152.el6.noarch


I was running:

ovirt-engine-websocket-proxy-3.3.0-0.2.master.20130609231551.gitc493152.el6.noarch


Thanks!


2013/6/17 Frantisek Kobzik 

> Hi Matt,
>
> could you specify what version/build of ovirt-websocket-proxy do you use?
>
> Thanks,
> Frank.
>
> - Original Message -
> From: "Matt ." 
> To: "Frantisek Kobzik" 
> Cc: "Alon Bar-Lev" , "users" 
> Sent: Friday, June 14, 2013 6:08:47 PM
> Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
>
> Hi Frank,
>
> I want to use the standard HTML noVNC client.
>
> I have installed the webproxy but it starts with an error on line 77 of the
> init script, there is a "e" where I don't know of what it is.
>
> Where do I have to set the engine to xyz ? Is this still nog 100%
> inplemented or am I wrong that we have to do this manually.
>
> Thanks again!!
>
> Cheers,
>
> Matt
>
>
> 2013/6/14 Frantisek Kobzik 
>
> > Hi Matt!
> >
> > Right now I'm not sure whether you are trying to launch console via MIME
> > (i.e. the console.vv is served to your locally installed virt-viewer) or
> > you want to run noVNC html client. (I'm a little bit confused because the
> > $subj contains noVNC but console.vv is actually the MIME way.)
> >
> > The noVNC client is now in the engine, but it runs only via plain http
> out
> > of the box (for the moment). If you want to use it, you must ensure two
> > things:
> >  1, You must run ovirt-websocket-proxy (preferably on the machine where
> > the engine runs) - just use ovirt-websocket-proxy package and run the
> > service.
> >  2, You must configure the engine so that it knows that you want to use
> > noVNC instead of MIME invocation. You can do it in the database or using
> > the tools via WebSocketProxy option. If your websocket-proxy runs on the
> > engine, set it to 'Engine:xyz', where xyz is the port on which the proxy
> > runs (6100 is the default now).
> >
> > Regards,
> > Frank.
> >
> > - Original Message -
> > From: "Matt ." 
> > To: "Alon Bar-Lev" 
> > Cc: "Frantisek Kobzik" , "users" 
> > Sent: Friday, June 14, 2013 3:45:25 PM
> > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
> >
> > Hi Alon,
> >
> > I have stopped there, but I get a console.vv download again on my Firefox
> > and no console!
> >
> > Cheers,
> >
> > Matt
> >
> >
> > 2013/6/14 Alon Bar-Lev 
> >
> > >
> > > Hi Matt,
> > >
> > > You should have stopped when it worked to you... :)
> > > I guess by placing 'console/'
> > >
> > > I was talking to Frank regarding the future changes.
> > >
> > > Thanks,
> > > Alon
> > >
> > > - Original Message -
> > > > From: "Matt ." 
> > > > To: "Alon Bar-Lev" 
> > > > Cc: "Frantisek Kobzik" , "users" <
> users@ovirt.org>
> > > > Sent: Friday, June 14, 2013 4:39:34 PM
> > > > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
> > > >
> > > > OK, thanks.
> > > >
> > > > I'm not 100% sure about what to do now. I have to change the servlet,
> > but
> > > > where ? A locate on the servlet didn't have me any match.
> > > >
> > > > Cheers,
> > > >
> > > > Matt
> > > >
> > > >
> > > > 2013/6/14 Alon Bar-Lev 
> > > >
> > > > >
> > > > >
> > > > > - Original Message -
> > > > > > From: "Alon Bar-Lev" 
> > > > > > To: "Frantisek Kobzik" 
> > > > > > Cc: "users" 
> > > > > > Sent: Friday, June 14, 2013 4:29:53 PM
> > > > > > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
> > > > > >
> > > > > > OK.
> > > > > >
> > > > > > So please modify it to /ovirt-engine-attachments
> > > > >
> > > > > I mean the org.ovirt.engine.core.GetAttachmentServlet servlet will
> be
> > > > > mapped to /ovirt-engine-attachment and serve
> > > > > /ovirt-ovirt-engine-attachment/*
> > > > >
> > > > > This is generic as it actually has nothing to do with console...
> > > > >
> > > > > The ovirt-engine prefix will allow us to avoid conflicts.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > - Original Message -
> > > > > > > From: "Frantisek Kobzik" 
> > > > > > > To: "Alon Bar-Lev" 
> > > > > > > Cc: "users" 
> > > > > > > Sent: Friday, June 14, 2013 4:19:26 PM
> > > > > > > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC
> viewer
> > > > > > >
> > > > > > > There is only one reason: we have to serve .rdp descriptors too
> > > and IE
> > > > > > > doesn't work well with attachment header (the filename is
> derived
> > > from
> > > > > the
> > > > > > > last part of the URL).
> > > > > > >
> > > > > > > - Original Message -
> > > > > > > From: "Alon Bar-Lev" 
> > > > > > > To: "Frantisek Kobzik" 
> > > > > > > Cc: "users" 
> > > > > > > Sent: Friday, June 14, 2013 3:11:36 PM
> > > > > > > S

Re: [Users] Fedora upgrading from 3.1 to 3.2

2013-06-17 Thread Karli Sjöberg 
mån 2013-06-17 klockan 10:11 +0003 skrev Alex Lourie:



On Fri, Jun 14, 2013 at 12:26 PM, Karli Sjöberg 
mailto:karli.sjob...@slu.se>>
wrote:
> Hi!
>

Hi Karli,

>
> More than two months have passed without any notices or updates on
> this issue, and looking at the bugreport absolutely nothing has been
> done since then. What´s confusing me is that the release management
> for oVirt 3.2 has this clearly printed:
> "MUST: Upgrade from previous release"
>
> And you all seem too busy with getting the next release out of the
> door before fixing the current... What gives? Don´t you care about
> early adopters?
>

I apologise that this issue wasn't taken care of yet. It is clear that
the priorities of developers shifted towards work on features in 3.3
release, which feature freeze is happening in about 2 weeks, so you can
understand the time pressure they all have. There's no need to be angry
about that. It is an open source project and as resources for the
development are limited, we're trying to do our best to cover as much
issues as possible. This can lead to situations as this issue, which
may be left behind for some time.


I´m not angry, as I stated before, I´m more confused, and maybe a little 
disappointed that important(in my opinion) pieces of a projects continuum have 
been ignored like that. I´m having a hard time understanding the reasoning 
behind the priorities that have made this issue appear. In my mind, making sure 
that users of any project are able to follow between minor upgrades is a given, 
with a schedule like; 1) Feature freeze, 2) Fix release blockers (upgrading 
being one of them), 3) Release, in that order. Now what´s happening is that you 
are kind of hoping to drag this out until the problem goes away by itself when 
you decide it´s time to stop supporting 3.1.




That said, the process for upgrading the oVirt 3.1 on Fedora 17 to
oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it is
taking time to resolve all the issues that come up in the process.

If this matter is not extremely urgent, we are currently working on a
tool that may make this upgrade easier, albeit, maybe, not completely
automatic.

On the other hand, if this is a completely and utterly urgent, we may
try to guide you through possible manual attempts to perform the
upgrade. Mind though, that they weren't thoroughly tested, and not
promised to go smoothly or even work, and we may have to think about
possible alternative solutions on the go.


Straight answer: Am I ever going to be able to upgrade from 3.1 to 3.2?

My concern (fear) is about being left behind, abandoned. It makes me feel 
non-important. Just like any admin, the work put down to make Templates, to set 
up quotas, create VMPools, a dozen of guests. And then have to export 
everything (nullifying the idea of "Thin Provisioning"), redo every Role, reset 
every permission, quota, and so on, isn´t (in my opinion) viable in the long 
run for oVirt as a project to demand. That´s why I had the notion that 
upgrading surely had to be a high priority. Was I wrong about that?




Best regards,
Alex Lourie,
Software Developer in Integration,
RHEV, Red Hat.

>
> Best Regards
> Karli Sjöberg
>
> fre 2013-04-05 klockan 10:24 +0200 skrev Sandro Bonazzola: Hi Karli,
>> we're still working on it
>>
>>
>> Il 02/04/2013 12:22, Karli Sjöberg ha scritto:
>>
>>
>  Hi,
>>>
>>> has there been any progress regarding this matter?
>>>
>>> Best Regards
>>> Karli Sjöberg
>>>
>>> fre 2013-03-15 klockan 14:12 + skrev Karli Sjöberg:
 fre 2013-03-15 klockan 14:59 +0100 skrev Sandro Bonazzola:
> Il 13/03/2013 12:24, Karli Sjöberg ha scritto:
>
>> ons 2013-03-13 klockan 12:00 +0100 skrev Dave Neary: Hi Karli,
>>>
>>> On 03/11/2013 12:16 PM, Karli Sjöberg wrote:
>>> > Hi,
>>> >
>>> > in the absence of any official path,  we have started working
>>> out our own
>>> > procedure for going from oVirt-3.1/Fedora 17 to
>>> oVirt-3.2/Fedora 18.
>>>
>>> Indeed, I have not seen any documentation in the wiki yet on
>>> upgrading
>>> oVirt - would you be interested in writing up your experiences
>>> there as
>>> a guide to others?
>>>
>>> Thanks!
>>> Dave.
>>>
>>>
>>  That was my intention to share a working procedure once it was
>> complete but I unfortunately hit a wall at "engine-upgrade". I
>> would be very glad, and able to continue, if that obstacle could
>> be lifted.
>>
>
> My experience in upgrading from oVirt-3.1/Fedora 17 to
> oVirt-3.2/Fedora 18:
>
> On Fedora 17:
> Be sure to have the latest updates running: yum distro-sync
> Set exclude=ovirt* in /etc/yum.conf
> Execute: fedup --disablerepo=ovirt* --network 18
>
> When you have a running Fedora 18:
> # systemctl list-units --failed
> UNIT   LOAD   ACTIVE SUBDESCRIPTION
> httpd.service  loaded failed failed The Apache HTTP Server
>>

Re: [Users] cpu stuck after joining fedora 18 node to ovirt

2013-06-17 Thread Pavia Daniele 
Hi Joop,
thanks for your feedback, the workaround you suggested did the trick. I 
noticed that we've got other ovirt nodes running fine with 
kernel-3.9.4-200.fc18.x86_64 but that does not seem to be present in the 
fedora stable repo. Looks like we were having issues with 
kernel-3.9.5-201.fc18.x86_64.

I owe you one ice-cold beer.

Cheers,
Daniele

On 06/16/2013 09:02 AM, Joop wrote:
> Hi Daniele,
>
> Search the mailinglist for cpu stuck and you'll find more threads about it 
> and the only answer yet, stick to kernel 3.6.10. Anything higher will cause 
> random cpu stuck on boot in combo with multipath. Some bugreports seem to 
> indicate that energy saving mode ( c states) is responsible but can't confirm 
> this but you can try setting bios to max performance, no powersave states.
>
> Regards,
>
> Joop
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Fedora upgrading from 3.1 to 3.2

2013-06-17 Thread Itamar Heim 

On 06/17/2013 01:08 PM, Alex Lourie wrote:



On Fri, Jun 14, 2013 at 12:26 PM, Karli Sjöberg 
wrote:

Hi!



Hi Karli,



More than two months have passed without any notices or updates on
this issue, and looking at the bugreport absolutely nothing has been
done since then. What´s confusing me is that the release management
for oVirt 3.2 has this clearly printed:
"MUST: Upgrade from previous release"

And you all seem too busy with getting the next release out of the
door before fixing the current... What gives? Don´t you care about
early adopters?



I apologise that this issue wasn't taken care of yet. It is clear that
the priorities of developers shifted towards work on features in 3.3
release, which feature freeze is happening in about 2 weeks, so you can
understand the time pressure they all have. There's no need to be angry
about that. It is an open source project and as resources for the
development are limited, we're trying to do our best to cover as much
issues as possible. This can lead to situations as this issue, which may
be left behind for some time.

That said, the process for upgrading the oVirt 3.1 on Fedora 17 to oVirt
3.2 on Fedora 18 is complex and non-trivial, that's why it is taking
time to resolve all the issues that come up in the process.

If this matter is not extremely urgent, we are currently working on a
tool that may make this upgrade easier, albeit, maybe, not completely
automatic.

On the other hand, if this is a completely and utterly urgent, we may
try to guide you through possible manual attempts to perform the
upgrade. Mind though, that they weren't thoroughly tested, and not
promised to go smoothly or even work, and we may have to think about
possible alternative solutions on the go.


it seems that upgrades on .el6 platforms (RHEL/CentOS) are easier (since 
not a major upgrade of the underlying OS)?




Best regards,
Alex Lourie,
Software Developer in Integration,
RHEV, Red Hat.



Best Regards
Karli Sjöberg

fre 2013-04-05 klockan 10:24 +0200 skrev Sandro Bonazzola: Hi Karli,

we're still working on it


Il 02/04/2013 12:22, Karli Sjöberg ha scritto:



 Hi,


has there been any progress regarding this matter?

Best Regards
Karli Sjöberg

fre 2013-03-15 klockan 14:12 + skrev Karli Sjöberg:

fre 2013-03-15 klockan 14:59 +0100 skrev Sandro Bonazzola:

Il 13/03/2013 12:24, Karli Sjöberg ha scritto:


ons 2013-03-13 klockan 12:00 +0100 skrev Dave Neary: Hi Karli,


On 03/11/2013 12:16 PM, Karli Sjöberg wrote:
> Hi,
>
> in the absence of any official path,  we have started working
out our own
> procedure for going from oVirt-3.1/Fedora 17 to
oVirt-3.2/Fedora 18.

Indeed, I have not seen any documentation in the wiki yet on
upgrading oVirt - would you be interested in writing up your
experiences there as a guide to others?

Thanks!
Dave.



 That was my intention to share a working procedure once it was
complete but I unfortunately hit a wall at "engine-upgrade". I
would be very glad, and able to continue, if that obstacle could
be lifted.



My experience in upgrading from oVirt-3.1/Fedora 17 to
oVirt-3.2/Fedora 18:

On Fedora 17:
Be sure to have the latest updates running: yum distro-sync
Set exclude=ovirt* in /etc/yum.conf
Execute: fedup --disablerepo=ovirt* --network 18

When you have a running Fedora 18:
# systemctl list-units --failed
UNIT   LOAD   ACTIVE SUBDESCRIPTION
httpd.service  loaded failed failed The Apache HTTP Server
postgresql.service loaded failed failed PostgreSQL database server

# systemctl stop postgresql.service
# tar cJvf pgsql-backup.tar.xz /var/lib/pgsql/data/
# yum install postgresql-upgrade

# cp /var/lib/pgsql/data/pg_hba.conf /root/pg_hba.conf.ovirt

edit /var/lib/pgsql/data/pg_hba.conf changing md5 to trust on the
local line.

# diff -u pg_hba.conf.ovirt pg_hba.conf
--- pg_hba.conf.ovirt2013-01-30 20:58:49.40400 +0100
+++ pg_hba.conf2013-01-30 20:59:06.70900 +0100
@@ -77,7 +77,7 @@
 # TYPE  DATABASEUSERADDRESS METHOD

 # "local" is for Unix domain socket connections only
-local   all all md5
+local   all all trust
 # IPv4 local connections:
 hostall all 127.0.0.1/32 md5
 # IPv6 local connections:



# postgresql-setup upgrade
Redirecting to /bin/systemctl stop  postgresql.service
Upgrading database: OK

See /var/lib/pgsql/pgupgrade.log for details.

# cp /root/pg_hba.conf.ovirt /var/lib/pgsql/data/pg_hba.conf
# systemctl postgrsql.service restart


edit /etc/httpd/conf.d/ssl.conf:
# diff -u ssl.conf.ovirt ssl.conf
--- ssl.conf.ovirt2013-01-30 21:21:06.90600 +0100
+++ ssl.conf2013-01-30 21:22:02.75700 +0100
@@ -9,7 +9,7 @@
 # consult the online docs. You have been warned.  #

-LoadModule ssl_module modules/mod_ssl.so
+#LoadModule ssl_module modules/mod_ssl.so

 #
 # When we also provide SSL we have to listen to the @@ -40,7
+40,7 @@
 #   Semaphore:
 #   Configure the path to the mutual exclusion semaphore the
 #

Re: [Users] Fedora upgrading from 3.1 to 3.2

2013-06-17 Thread Alex Lourie 



On Fri, Jun 14, 2013 at 12:26 PM, Karli Sjöberg  
wrote:

Hi!



Hi Karli,



More than two months have passed without any notices or updates on 
this issue, and looking at the bugreport absolutely nothing has been 
done since then. What´s confusing me is that the release management 
for oVirt 3.2 has this clearly printed:

"MUST: Upgrade from previous release"

And you all seem too busy with getting the next release out of the 
door before fixing the current... What gives? Don´t you care about 
early adopters?




I apologise that this issue wasn't taken care of yet. It is clear that 
the priorities of developers shifted towards work on features in 3.3 
release, which feature freeze is happening in about 2 weeks, so you can 
understand the time pressure they all have. There's no need to be angry 
about that. It is an open source project and as resources for the 
development are limited, we're trying to do our best to cover as much 
issues as possible. This can lead to situations as this issue, which 
may be left behind for some time.


That said, the process for upgrading the oVirt 3.1 on Fedora 17 to 
oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it is 
taking time to resolve all the issues that come up in the process.


If this matter is not extremely urgent, we are currently working on a 
tool that may make this upgrade easier, albeit, maybe, not completely 
automatic.


On the other hand, if this is a completely and utterly urgent, we may 
try to guide you through possible manual attempts to perform the 
upgrade. Mind though, that they weren't thoroughly tested, and not 
promised to go smoothly or even work, and we may have to think about 
possible alternative solutions on the go.


Best regards,
Alex Lourie,
Software Developer in Integration,
RHEV, Red Hat.



Best Regards
Karli Sjöberg

fre 2013-04-05 klockan 10:24 +0200 skrev Sandro Bonazzola: Hi Karli,

we're still working on it


Il 02/04/2013 12:22, Karli Sjöberg ha scritto:



 Hi,


has there been any progress regarding this matter?

Best Regards
Karli Sjöberg

fre 2013-03-15 klockan 14:12 + skrev Karli Sjöberg:
fre 2013-03-15 klockan 14:59 +0100 skrev Sandro Bonazzola: 

Il 13/03/2013 12:24, Karli Sjöberg ha scritto:


ons 2013-03-13 klockan 12:00 +0100 skrev Dave Neary: Hi Karli,


On 03/11/2013 12:16 PM, Karli Sjöberg wrote:
> Hi,
>
> in the absence of any official path,  we have started working 
out our own
> procedure for going from oVirt-3.1/Fedora 17 to 
oVirt-3.2/Fedora 18.


Indeed, I have not seen any documentation in the wiki yet on 
upgrading 
oVirt - would you be interested in writing up your experiences 
there as 
a guide to others?


Thanks!
Dave.


 That was my intention to share a working procedure once it was 
complete but I unfortunately hit a wall at "engine-upgrade". I 
would be very glad, and able to continue, if that obstacle could 
be lifted.


 
My experience in upgrading from oVirt-3.1/Fedora 17 to 
oVirt-3.2/Fedora 18:


On Fedora 17:
Be sure to have the latest updates running: yum distro-sync
Set exclude=ovirt* in /etc/yum.conf
Execute: fedup --disablerepo=ovirt* --network 18

When you have a running Fedora 18:
# systemctl list-units --failed
UNIT   LOAD   ACTIVE SUBDESCRIPTION
httpd.service  loaded failed failed The Apache HTTP Server
postgresql.service loaded failed failed PostgreSQL database server

# systemctl stop postgresql.service
# tar cJvf pgsql-backup.tar.xz /var/lib/pgsql/data/
# yum install postgresql-upgrade

# cp /var/lib/pgsql/data/pg_hba.conf /root/pg_hba.conf.ovirt

edit /var/lib/pgsql/data/pg_hba.conf changing md5 to trust on the 
local line.


# diff -u pg_hba.conf.ovirt pg_hba.conf
--- pg_hba.conf.ovirt   2013-01-30 20:58:49.40400 +0100
+++ pg_hba.conf 2013-01-30 20:59:06.70900 +0100
@@ -77,7 +77,7 @@
 # TYPE  DATABASEUSERADDRESS 
METHOD
 
 # "local" is for Unix domain socket connections only
-local   all all 
md5
+local   all all 
trust

 # IPv4 local connections:
 hostall all 127.0.0.1/32
md5

 # IPv6 local connections:



# postgresql-setup upgrade
Redirecting to /bin/systemctl stop  postgresql.service
Upgrading database: OK

See /var/lib/pgsql/pgupgrade.log for details.

# cp /root/pg_hba.conf.ovirt /var/lib/pgsql/data/pg_hba.conf
# systemctl postgrsql.service restart


edit /etc/httpd/conf.d/ssl.conf:
# diff -u ssl.conf.ovirt ssl.conf
--- ssl.conf.ovirt  2013-01-30 21:21:06.90600 +0100
+++ ssl.conf2013-01-30 21:22:02.75700 +0100
@@ -9,7 +9,7 @@
 # consult the online docs. You have been warned.  
 #
 
-LoadModule ssl_module modules/mod_ssl.so

+#LoadModule ssl_module modules/mod_ssl.so
 
 #
 # When we also provide SSL we have to listen to the 
@@ -40,7 +40,7 @@

 #   Semaphore:
 #   Configure the path to the mutual exclusion semaphore the
 #   SSL engine

Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer

2013-06-17 Thread Frantisek Kobzik 
Hi Matt,

could you specify what version/build of ovirt-websocket-proxy do you use?

Thanks,
Frank.

- Original Message -
From: "Matt ." 
To: "Frantisek Kobzik" 
Cc: "Alon Bar-Lev" , "users" 
Sent: Friday, June 14, 2013 6:08:47 PM
Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer

Hi Frank,

I want to use the standard HTML noVNC client.

I have installed the webproxy but it starts with an error on line 77 of the
init script, there is a "e" where I don't know of what it is.

Where do I have to set the engine to xyz ? Is this still nog 100%
inplemented or am I wrong that we have to do this manually.

Thanks again!!

Cheers,

Matt


2013/6/14 Frantisek Kobzik 

> Hi Matt!
>
> Right now I'm not sure whether you are trying to launch console via MIME
> (i.e. the console.vv is served to your locally installed virt-viewer) or
> you want to run noVNC html client. (I'm a little bit confused because the
> $subj contains noVNC but console.vv is actually the MIME way.)
>
> The noVNC client is now in the engine, but it runs only via plain http out
> of the box (for the moment). If you want to use it, you must ensure two
> things:
>  1, You must run ovirt-websocket-proxy (preferably on the machine where
> the engine runs) - just use ovirt-websocket-proxy package and run the
> service.
>  2, You must configure the engine so that it knows that you want to use
> noVNC instead of MIME invocation. You can do it in the database or using
> the tools via WebSocketProxy option. If your websocket-proxy runs on the
> engine, set it to 'Engine:xyz', where xyz is the port on which the proxy
> runs (6100 is the default now).
>
> Regards,
> Frank.
>
> - Original Message -
> From: "Matt ." 
> To: "Alon Bar-Lev" 
> Cc: "Frantisek Kobzik" , "users" 
> Sent: Friday, June 14, 2013 3:45:25 PM
> Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
>
> Hi Alon,
>
> I have stopped there, but I get a console.vv download again on my Firefox
> and no console!
>
> Cheers,
>
> Matt
>
>
> 2013/6/14 Alon Bar-Lev 
>
> >
> > Hi Matt,
> >
> > You should have stopped when it worked to you... :)
> > I guess by placing 'console/'
> >
> > I was talking to Frank regarding the future changes.
> >
> > Thanks,
> > Alon
> >
> > - Original Message -
> > > From: "Matt ." 
> > > To: "Alon Bar-Lev" 
> > > Cc: "Frantisek Kobzik" , "users" 
> > > Sent: Friday, June 14, 2013 4:39:34 PM
> > > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
> > >
> > > OK, thanks.
> > >
> > > I'm not 100% sure about what to do now. I have to change the servlet,
> but
> > > where ? A locate on the servlet didn't have me any match.
> > >
> > > Cheers,
> > >
> > > Matt
> > >
> > >
> > > 2013/6/14 Alon Bar-Lev 
> > >
> > > >
> > > >
> > > > - Original Message -
> > > > > From: "Alon Bar-Lev" 
> > > > > To: "Frantisek Kobzik" 
> > > > > Cc: "users" 
> > > > > Sent: Friday, June 14, 2013 4:29:53 PM
> > > > > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
> > > > >
> > > > > OK.
> > > > >
> > > > > So please modify it to /ovirt-engine-attachments
> > > >
> > > > I mean the org.ovirt.engine.core.GetAttachmentServlet servlet will be
> > > > mapped to /ovirt-engine-attachment and serve
> > > > /ovirt-ovirt-engine-attachment/*
> > > >
> > > > This is generic as it actually has nothing to do with console...
> > > >
> > > > The ovirt-engine prefix will allow us to avoid conflicts.
> > > >
> > > > Thanks!
> > > >
> > > > >
> > > > > Thanks!
> > > > >
> > > > > - Original Message -
> > > > > > From: "Frantisek Kobzik" 
> > > > > > To: "Alon Bar-Lev" 
> > > > > > Cc: "users" 
> > > > > > Sent: Friday, June 14, 2013 4:19:26 PM
> > > > > > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
> > > > > >
> > > > > > There is only one reason: we have to serve .rdp descriptors too
> > and IE
> > > > > > doesn't work well with attachment header (the filename is derived
> > from
> > > > the
> > > > > > last part of the URL).
> > > > > >
> > > > > > - Original Message -
> > > > > > From: "Alon Bar-Lev" 
> > > > > > To: "Frantisek Kobzik" 
> > > > > > Cc: "users" 
> > > > > > Sent: Friday, June 14, 2013 3:11:36 PM
> > > > > > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC viewer
> > > > > >
> > > > > > Frank,
> > > > > >
> > > > > > BTW: why do we need multiple servlet for attachments?
> > > > > >
> > > > > > Alon
> > > > > >
> > > > > > - Original Message -
> > > > > > > From: "Alon Bar-Lev" 
> > > > > > > To: "Frantisek Kobzik" 
> > > > > > > Cc: "users" 
> > > > > > > Sent: Friday, June 14, 2013 4:08:09 PM
> > > > > > > Subject: Re: [Users] oVirt 3.3 does not start HTML5/noVNC
> viewer
> > > > > > >
> > > > > > >
> > > > > > > Oh!
> > > > > > > Sorry, wrong paste... it should be 'console/'
> > > > > > > Sorry.
> > > > > > >
> > > > > > > Frank,
> > > > > > > Can you please check that and also rename the link to
> > > > > > > ovirt-engine-console
> > > > > > > or
> > > > >