Re: [ovirt-users] Maximum time node can be offline.

2018-02-08 Thread Gianluca Cecchi
On Fri, Feb 9, 2018 at 2:30 AM, Thomas Letherby  wrote:

> Thanks, that answers my follow up question! :)
>
> My concern is that I could have a host off-line for a month say, is that
> going to cause any issues?
>
> Thanks,
>
> Thomas
>
>
I think that if in the mean time you don't make any configuration changes
and you don't update anything, there is no reason to have problems.
In case of changes done, it could depend on what they are: are you thinking
about any particular scenario?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] IndexError python-sdk

2018-02-08 Thread David David
Hi all.

python-ovirt-engine-sdk4-4.2.2-2.el7.centos.x86_64


Issue is that I cant upload a snapshot I get IndexError when do
upload_disk_snapshots.py
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk_snapshots.py

Output:

Traceback (most recent call last):
  File "snapshot_upload.py", line 298, in 
images_chain = get_images_chain(disk_path)
  File "snapshot_upload.py", line 263, in get_images_chain
base_volume = [v for v in volumes_info.values() if
'full-backing-filename' not in v ][0]
IndexError: list index out of range
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Maximum time node can be offline.

2018-02-08 Thread Thomas Letherby
Thanks, that answers my follow up question! :)

My concern is that I could have a host off-line for a month say, is that
going to cause any issues?

Thanks,

Thomas

On Thu, Feb 8, 2018 at 3:12 AM Staniforth, Paul <
p.stanifo...@leedsbeckett.ac.uk> wrote:

> Hello,
>
>you should be able to use the power saving cluster scheduling
> policy.
>
>
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html/administration_guide/sect-Scheduling_Policies
>
>
> Regards,
>
>   Paul S.
> --
> *From:* users-boun...@ovirt.org  on behalf of
> Thomas Letherby 
> *Sent:* 08 February 2018 05:51
> *To:* users@ovirt.org
> *Subject:* [ovirt-users] Maximum time node can be offline.
>
> Hello all,
>
> Is there a maximum length of time an Ovirt Node 4.2 based host can be
> offline in a cluster before it would have issues when powered back on?
>
> The reason I ask is in my lab I currently have a three node cluster that
> works really well, however a lot of the time I only actually need the
> resources of one host, so to save power I'd like to keep the other two
> offline until needed.
>
> I can always script them to boot once a week or so if I need to.
>
> Thanks,
>
> Thomas
> To view the terms under which this email is distributed, please go to:-
> http://disclaimer.leedsbeckett.ac.uk/disclaimer/disclaimer.html
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Cannot Remove Disk

2018-02-08 Thread Donny Davis
So now when I create a new disk on the same domain with quota disabled, I
get

   - Cannot edit Virtual Disk. Quota is not valid.


This is a new machine, created after the above issue was solved

On Thu, Feb 8, 2018 at 11:56 AM, Donny Davis  wrote:

> Disabling the quota for that DC did the trick. The funny part is it was
> never enabled. I put it in audit mode, tried a delete, got the error... and
> then disabled it.
>
> Worked, I am a happy camper... Thanks guys.
>
> On Thu, Feb 8, 2018 at 11:51 AM, Andrej Krejcir 
> wrote:
>
>> Or, it should be enough to disable the quota in the data center, then
>> change it for the disk and reenable it again.
>>
>> On 8 February 2018 at 17:42, Andrej Krejcir  wrote:
>>
>>> Do the operations work in the UI?
>>> If not, then the DB has to be changed manually:
>>>
>>> $ psql engine
>>>
>>> UPDATE image_storage_domain_map sd_map
>>> SET quota_id = NULL
>>> FROM images
>>> WHERE sd_map.image_id = images.image_guid
>>>   AND images.image_group_id = 'ID_OF_THE_DISK';
>>>
>>>
>>> On 8 February 2018 at 17:06, Donny Davis  wrote:
>>>
 Any operation on the disk throws this error, to include changing the
 quota.

 On Thu, Feb 8, 2018 at 11:03 AM, Andrej Krejcir 
 wrote:

> The error message means that the data center (storage pool) where the
> quota is defined is different from the data center where the disk is.
>
> It seems like a bug, as it should not be possible to assign a quota to
> a disk from a different data center.
>
> To fix it, try setting the quota of the disk to any quota from the
> same data center.
>
> ​Regards,
> Andrej​
>
>
> On 8 February 2018 at 16:37, Martin Sivak  wrote:
>
>> Andrej, this might be related to the recent fixes of yours in that
>> area. Can you take a look please?
>>
>> Best regards
>>
>> Martin Sivak
>>
>> On Thu, Feb 8, 2018 at 4:18 PM, Donny Davis 
>> wrote:
>> > Ovirt 4.2 has been humming away quite nicely for me in the last few
>> months,
>> > and now I am hitting an issue when try to touch any api call that
>> has to do
>> > with a specific disk. This disk resides on a hyperconverged DC, and
>> none of
>> > the other disks seem to be affected. Here is the error thrown.
>> >
>> > 2018-02-08 10:13:20,005-05 ERROR
>> > [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand]
>> (default task-22)
>> > [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during
>> ValidateFailure.:
>> > org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException:
>> Quota
>> > 6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
>> > 5a497956-0380-021e-0025-035e
>> >
>> >
>> >
>> > Any ideas what can be done to fix this?
>> >
>> > ___
>> > 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: [ovirt-users] Cannot Remove Disk

2018-02-08 Thread Donny Davis
Disabling the quota for that DC did the trick. The funny part is it was
never enabled. I put it in audit mode, tried a delete, got the error... and
then disabled it.

Worked, I am a happy camper... Thanks guys.

On Thu, Feb 8, 2018 at 11:51 AM, Andrej Krejcir  wrote:

> Or, it should be enough to disable the quota in the data center, then
> change it for the disk and reenable it again.
>
> On 8 February 2018 at 17:42, Andrej Krejcir  wrote:
>
>> Do the operations work in the UI?
>> If not, then the DB has to be changed manually:
>>
>> $ psql engine
>>
>> UPDATE image_storage_domain_map sd_map
>> SET quota_id = NULL
>> FROM images
>> WHERE sd_map.image_id = images.image_guid
>>   AND images.image_group_id = 'ID_OF_THE_DISK';
>>
>>
>> On 8 February 2018 at 17:06, Donny Davis  wrote:
>>
>>> Any operation on the disk throws this error, to include changing the
>>> quota.
>>>
>>> On Thu, Feb 8, 2018 at 11:03 AM, Andrej Krejcir 
>>> wrote:
>>>
 The error message means that the data center (storage pool) where the
 quota is defined is different from the data center where the disk is.

 It seems like a bug, as it should not be possible to assign a quota to
 a disk from a different data center.

 To fix it, try setting the quota of the disk to any quota from the same
 data center.

 ​Regards,
 Andrej​


 On 8 February 2018 at 16:37, Martin Sivak  wrote:

> Andrej, this might be related to the recent fixes of yours in that
> area. Can you take a look please?
>
> Best regards
>
> Martin Sivak
>
> On Thu, Feb 8, 2018 at 4:18 PM, Donny Davis 
> wrote:
> > Ovirt 4.2 has been humming away quite nicely for me in the last few
> months,
> > and now I am hitting an issue when try to touch any api call that
> has to do
> > with a specific disk. This disk resides on a hyperconverged DC, and
> none of
> > the other disks seem to be affected. Here is the error thrown.
> >
> > 2018-02-08 10:13:20,005-05 ERROR
> > [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (default
> task-22)
> > [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during
> ValidateFailure.:
> > org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException:
> Quota
> > 6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
> > 5a497956-0380-021e-0025-035e
> >
> >
> >
> > Any ideas what can be done to fix this?
> >
> > ___
> > 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: [ovirt-users] Cannot Remove Disk

2018-02-08 Thread Andrej Krejcir
Or, it should be enough to disable the quota in the data center, then
change it for the disk and reenable it again.

On 8 February 2018 at 17:42, Andrej Krejcir  wrote:

> Do the operations work in the UI?
> If not, then the DB has to be changed manually:
>
> $ psql engine
>
> UPDATE image_storage_domain_map sd_map
> SET quota_id = NULL
> FROM images
> WHERE sd_map.image_id = images.image_guid
>   AND images.image_group_id = 'ID_OF_THE_DISK';
>
>
> On 8 February 2018 at 17:06, Donny Davis  wrote:
>
>> Any operation on the disk throws this error, to include changing the
>> quota.
>>
>> On Thu, Feb 8, 2018 at 11:03 AM, Andrej Krejcir 
>> wrote:
>>
>>> The error message means that the data center (storage pool) where the
>>> quota is defined is different from the data center where the disk is.
>>>
>>> It seems like a bug, as it should not be possible to assign a quota to a
>>> disk from a different data center.
>>>
>>> To fix it, try setting the quota of the disk to any quota from the same
>>> data center.
>>>
>>> ​Regards,
>>> Andrej​
>>>
>>>
>>> On 8 February 2018 at 16:37, Martin Sivak  wrote:
>>>
 Andrej, this might be related to the recent fixes of yours in that
 area. Can you take a look please?

 Best regards

 Martin Sivak

 On Thu, Feb 8, 2018 at 4:18 PM, Donny Davis 
 wrote:
 > Ovirt 4.2 has been humming away quite nicely for me in the last few
 months,
 > and now I am hitting an issue when try to touch any api call that has
 to do
 > with a specific disk. This disk resides on a hyperconverged DC, and
 none of
 > the other disks seem to be affected. Here is the error thrown.
 >
 > 2018-02-08 10:13:20,005-05 ERROR
 > [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (default
 task-22)
 > [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during ValidateFailure.:
 > org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException:
 Quota
 > 6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
 > 5a497956-0380-021e-0025-035e
 >
 >
 >
 > Any ideas what can be done to fix this?
 >
 > ___
 > 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: [ovirt-users] Cannot Remove Disk

2018-02-08 Thread Donny Davis
Again, any operation on the disk throws the error. The UI, API both throw
the exception

On Thu, Feb 8, 2018 at 11:42 AM, Andrej Krejcir  wrote:

> Do the operations work in the UI?
> If not, then the DB has to be changed manually:
>
> $ psql engine
>
> UPDATE image_storage_domain_map sd_map
> SET quota_id = NULL
> FROM images
> WHERE sd_map.image_id = images.image_guid
>   AND images.image_group_id = 'ID_OF_THE_DISK';
>
>
> On 8 February 2018 at 17:06, Donny Davis  wrote:
>
>> Any operation on the disk throws this error, to include changing the
>> quota.
>>
>> On Thu, Feb 8, 2018 at 11:03 AM, Andrej Krejcir 
>> wrote:
>>
>>> The error message means that the data center (storage pool) where the
>>> quota is defined is different from the data center where the disk is.
>>>
>>> It seems like a bug, as it should not be possible to assign a quota to a
>>> disk from a different data center.
>>>
>>> To fix it, try setting the quota of the disk to any quota from the same
>>> data center.
>>>
>>> ​Regards,
>>> Andrej​
>>>
>>>
>>> On 8 February 2018 at 16:37, Martin Sivak  wrote:
>>>
 Andrej, this might be related to the recent fixes of yours in that
 area. Can you take a look please?

 Best regards

 Martin Sivak

 On Thu, Feb 8, 2018 at 4:18 PM, Donny Davis 
 wrote:
 > Ovirt 4.2 has been humming away quite nicely for me in the last few
 months,
 > and now I am hitting an issue when try to touch any api call that has
 to do
 > with a specific disk. This disk resides on a hyperconverged DC, and
 none of
 > the other disks seem to be affected. Here is the error thrown.
 >
 > 2018-02-08 10:13:20,005-05 ERROR
 > [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (default
 task-22)
 > [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during ValidateFailure.:
 > org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException:
 Quota
 > 6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
 > 5a497956-0380-021e-0025-035e
 >
 >
 >
 > Any ideas what can be done to fix this?
 >
 > ___
 > 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: [ovirt-users] Cannot Remove Disk

2018-02-08 Thread Andrej Krejcir
Do the operations work in the UI?
If not, then the DB has to be changed manually:

$ psql engine

UPDATE image_storage_domain_map sd_map
SET quota_id = NULL
FROM images
WHERE sd_map.image_id = images.image_guid
  AND images.image_group_id = 'ID_OF_THE_DISK';


On 8 February 2018 at 17:06, Donny Davis  wrote:

> Any operation on the disk throws this error, to include changing the quota.
>
> On Thu, Feb 8, 2018 at 11:03 AM, Andrej Krejcir 
> wrote:
>
>> The error message means that the data center (storage pool) where the
>> quota is defined is different from the data center where the disk is.
>>
>> It seems like a bug, as it should not be possible to assign a quota to a
>> disk from a different data center.
>>
>> To fix it, try setting the quota of the disk to any quota from the same
>> data center.
>>
>> ​Regards,
>> Andrej​
>>
>>
>> On 8 February 2018 at 16:37, Martin Sivak  wrote:
>>
>>> Andrej, this might be related to the recent fixes of yours in that
>>> area. Can you take a look please?
>>>
>>> Best regards
>>>
>>> Martin Sivak
>>>
>>> On Thu, Feb 8, 2018 at 4:18 PM, Donny Davis 
>>> wrote:
>>> > Ovirt 4.2 has been humming away quite nicely for me in the last few
>>> months,
>>> > and now I am hitting an issue when try to touch any api call that has
>>> to do
>>> > with a specific disk. This disk resides on a hyperconverged DC, and
>>> none of
>>> > the other disks seem to be affected. Here is the error thrown.
>>> >
>>> > 2018-02-08 10:13:20,005-05 ERROR
>>> > [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (default
>>> task-22)
>>> > [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during ValidateFailure.:
>>> > org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException: Quota
>>> > 6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
>>> > 5a497956-0380-021e-0025-035e
>>> >
>>> >
>>> >
>>> > Any ideas what can be done to fix this?
>>> >
>>> > ___
>>> > 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: [ovirt-users] Cannot Remove Disk

2018-02-08 Thread Donny Davis
Any operation on the disk throws this error, to include changing the quota.

On Thu, Feb 8, 2018 at 11:03 AM, Andrej Krejcir  wrote:

> The error message means that the data center (storage pool) where the
> quota is defined is different from the data center where the disk is.
>
> It seems like a bug, as it should not be possible to assign a quota to a
> disk from a different data center.
>
> To fix it, try setting the quota of the disk to any quota from the same
> data center.
>
> ​Regards,
> Andrej​
>
>
> On 8 February 2018 at 16:37, Martin Sivak  wrote:
>
>> Andrej, this might be related to the recent fixes of yours in that
>> area. Can you take a look please?
>>
>> Best regards
>>
>> Martin Sivak
>>
>> On Thu, Feb 8, 2018 at 4:18 PM, Donny Davis  wrote:
>> > Ovirt 4.2 has been humming away quite nicely for me in the last few
>> months,
>> > and now I am hitting an issue when try to touch any api call that has
>> to do
>> > with a specific disk. This disk resides on a hyperconverged DC, and
>> none of
>> > the other disks seem to be affected. Here is the error thrown.
>> >
>> > 2018-02-08 10:13:20,005-05 ERROR
>> > [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (default
>> task-22)
>> > [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during ValidateFailure.:
>> > org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException: Quota
>> > 6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
>> > 5a497956-0380-021e-0025-035e
>> >
>> >
>> >
>> > Any ideas what can be done to fix this?
>> >
>> > ___
>> > 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: [ovirt-users] Cannot Remove Disk

2018-02-08 Thread Andrej Krejcir
The error message means that the data center (storage pool) where the quota
is defined is different from the data center where the disk is.

It seems like a bug, as it should not be possible to assign a quota to a
disk from a different data center.

To fix it, try setting the quota of the disk to any quota from the same
data center.

​Regards,
Andrej​


On 8 February 2018 at 16:37, Martin Sivak  wrote:

> Andrej, this might be related to the recent fixes of yours in that
> area. Can you take a look please?
>
> Best regards
>
> Martin Sivak
>
> On Thu, Feb 8, 2018 at 4:18 PM, Donny Davis  wrote:
> > Ovirt 4.2 has been humming away quite nicely for me in the last few
> months,
> > and now I am hitting an issue when try to touch any api call that has to
> do
> > with a specific disk. This disk resides on a hyperconverged DC, and none
> of
> > the other disks seem to be affected. Here is the error thrown.
> >
> > 2018-02-08 10:13:20,005-05 ERROR
> > [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (default
> task-22)
> > [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during ValidateFailure.:
> > org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException: Quota
> > 6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
> > 5a497956-0380-021e-0025-035e
> >
> >
> >
> > Any ideas what can be done to fix this?
> >
> > ___
> > 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: [ovirt-users] Info about exporting from vSphere

2018-02-08 Thread Luca 'remix_tj' Lorenzetto
On Thu, Feb 8, 2018 at 4:34 PM, Gianluca Cecchi
 wrote:
>
> Thanks Luca.
> I asked because I see this inside the gui.
> https://drive.google.com/file/d/12vI9RUq9t4J--jlkqSxvG2jqylGfD2sP/view?usp=sharing
>
> Probably you do it via api and you don't need to provide ESXi credentials?
> Did you try also from web admin gui leaving empty the fields related to
> ESXi?
>

If you're not used to libvirt connection to vmware, all that fields
could scare. Anyway you need to fill out all the values, because are
needed to locate the vm you want to migrate.
When using that function you'll point to a specific host connected to
the given vcenter, in the given datacenter, inside a given cluster.
Import function will contact vcenter and ask for all vms in shutdown
status on that host, then allows you to continue with the wizard.

Luca



-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Cannot Remove Disk

2018-02-08 Thread Martin Sivak
Andrej, this might be related to the recent fixes of yours in that
area. Can you take a look please?

Best regards

Martin Sivak

On Thu, Feb 8, 2018 at 4:18 PM, Donny Davis  wrote:
> Ovirt 4.2 has been humming away quite nicely for me in the last few months,
> and now I am hitting an issue when try to touch any api call that has to do
> with a specific disk. This disk resides on a hyperconverged DC, and none of
> the other disks seem to be affected. Here is the error thrown.
>
> 2018-02-08 10:13:20,005-05 ERROR
> [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (default task-22)
> [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during ValidateFailure.:
> org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException: Quota
> 6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
> 5a497956-0380-021e-0025-035e
>
>
>
> Any ideas what can be done to fix this?
>
> ___
> 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: [ovirt-users] Info about exporting from vSphere

2018-02-08 Thread Gianluca Cecchi
On Thu, Feb 8, 2018 at 4:28 PM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

> On Thu, Feb 8, 2018 at 4:20 PM, Gianluca Cecchi
>  wrote:
> > Hello,
> > I have this ind of situation.
> [cut]
> > I see in my oVirt 4.1.9 that I can import from:
> >
> > 1) VMware
> >
> > 2) VMware Virtual Appliance
> [cut]
> > - what is the best between the 2 methods if I can chose? Their Pros?
> >
>
> Mode 1 imports directly from the vcenter, method 2 required you to
> export vm to OVA and then copy to some path and import to RHV
>
> Mode 1 requires an user on vcenter only. Any operation you'll do will
> go through vcenter.
>

Thanks Luca.
I asked because I see this inside the gui.
https://drive.google.com/file/d/12vI9RUq9t4J--jlkqSxvG2jqylGfD2sP/view?usp=sharing

Probably you do it via api and you don't need to provide ESXi credentials?
Did you try also from web admin gui leaving empty the fields related to
ESXi?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Info about exporting from vSphere

2018-02-08 Thread Gianluca Cecchi
Hello,
I have this ind of situation.

Source env:
It is vSphere 6.5 (both vCenter Server appliance and ESXi hosts) where I
have an admin account to connect to, but currently only to vCenter and not
to the ESXi hosts

The VM to be migrated is Windows 2008 R2 SP1 with virtual hw version 8
(ESXi 5.0 and later) and has one boot disk 35Gb and one data disk 250Gb.
The SCSI controller is LSI logic sas and network vmxnet3
It has no snapshots at the moment

I see in my oVirt 4.1.9 that I can import from:

1) VMware

2) VMware Virtual Appliance

and found also related documentations in RHEV 4.1 Virtual Machine
Management pdf
Some doubts:

- what is the best between the 2 methods if I can chose? Their Pros?

- Does 1) imply that I also need the ESXi account? Currently my windows
domain account that gives me access to vcenter doesn't work connecting to
ESXi hosts

- also it seems that 1) is more intrusive, while for 2) I only need to put
the ova file into some nfs share...

Thanks in advance,

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


[ovirt-users] Cannot Remove Disk

2018-02-08 Thread Donny Davis
Ovirt 4.2 has been humming away quite nicely for me in the last few months,
and now I am hitting an issue when try to touch any api call that has to do
with a specific disk. This disk resides on a hyperconverged DC, and none of
the other disks seem to be affected. Here is the error thrown.

2018-02-08 10:13:20,005-05 ERROR
[org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (default
task-22) [7b48d1ec-53a7-497a-af8e-938f30a321cf] Error during
ValidateFailure.:
org.ovirt.engine.core.bll.quota.InvalidQuotaParametersException: Quota
6156b8dd-50c9-4e8f-b1f3-4a6449b02c7b does not match storage pool
5a497956-0380-021e-0025-035e



Any ideas what can be done to fix this?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

2018-02-08 Thread Frank Rothenstein
Thanks Thomas,

it seems you were right. I followed the instructions to enable
hugepages via kernel command line and after reboot vdsmd starts
correctly.
(I went back to 4.1.9 in between, added the kernel command line and
upgraded to 4.2)

The docs/release notes should mention it - or did I miss it?

Am Dienstag, den 06.02.2018, 17:17 -0800 schrieb Thomas Davis:
> sorry, make that:
> 
> hugeadm --pool-list
>   Size  Minimum  Current  Maximum  Default
>   2097152 1024 1024 1024*
> 1073741824   4   4   4 
> 
> 
> On Tue, Feb 6, 2018 at 5:16 PM, Thomas Davis  wrote:
> > I found that you now need hugepage1g support.  The error messages
> > are wrong - it's not truly a libvirt problem, it's hugepages1g are
> > missing for libvirt.
> > 
> > add something like:
> > 
> > default_hugepagesz=1G hugepagesz=1G hugepages=4 hugepagesz=2M
> > hugepages=1024 to the kernel command line.
> > 
> > You can also do a 'yum install libhugetlbfs-utils', then do:
> > 
> > hugeadm --list
> > Mount Point  Options
> > /dev/hugepages   rw,seclabel,relatime
> > /dev/hugepages1G rw,seclabel,relatime,pagesize=1G
> > 
> > if you do not see the /dev/hugepages1G listed, then vdsmd/libvirt
> > will not start.
> > 
> > 
> > 
> > 
> > 
> > 
> > On Mon, Feb 5, 2018 at 5:49 AM, Frank Rothenstein  > dden-kliniken.de> wrote:
> > > Hi, 
> > > 
> > > I'm currently stuck - after upgrading 4.1 to 4.2 I cannot start
> > > the 
> > > host-processes. 
> > > systemctl start vdsmd fails with following lines in journalctl: 
> > > 
> > >  
> > > 
> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: vdsm: Running wait_for_network 
> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: vdsm: Running run_init_hooks 
> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: vdsm: Running check_is_configured 
> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net 
> > > sasldblistusers2[10440]: DIGEST-MD5 common mech free 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: Error: 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: One of the modules is not configured
> > > to 
> > > work with VDSM. 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: To configure the module use the
> > > following: 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: 'vdsm-tool configure [--module
> > > module- 
> > > name]'. 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: If all modules are not configured
> > > try to 
> > > use: 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: 'vdsm-tool configure --force' 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: (The force flag will stop the
> > > module's 
> > > service and start it 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: afterwards automatically to load the
> > > new 
> > > configuration.) 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: abrt is already configured for vdsm 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: lvm is configured for vdsm 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: libvirt is not configured for vdsm
> > > yet 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: Current revision of multipath.conf 
> > > detected, preserving 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: Modules libvirt are not configured 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: vdsm: stopped during execute 
> > > check_is_configured task (task returned with error code 1). 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]: 
> > > vdsmd.service: control process exited, code=exited status=1 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]:
> > > Failed to 
> > > start Virtual Desktop Server Manager. 
> > > -- Subject: Unit vdsmd.service has failed 
> > > -- Defined-By: systemd 
> > > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd
> > > -devel 
> > > -- 
> > > -- Unit vdsmd.service has failed. 



Frank Rothenstein 

Systemadministrator
Fon: +49 3821 700 125
Fax: +49 3821 700 190Internet: www.bodden-kliniken.de
E-Mail: f.rothenst...@bodden-kliniken.de


_
BODDEN-KLINIKEN Ribnitz-Damgarten GmbH
Sandhufe 2
18311 Ribnitz-Damgarten

Telefon: 03821-700-0
Telefax: 03821-700-240

E-Mail: i...@bodden-kliniken.de 
Internet: 

Re: [ovirt-users] ovn problem - Failed to communicate with the external provider, see log for additional details.

2018-02-08 Thread Marcin Mirecki
Hello George,

Probably your engine and provider certs do not match.
The engine pki should be in:
/etc/pki/ovirt-engine/certs/
The provider keys are defined in the SSL section of the config file
(/etc/ovirt-provider-ovn/conf.d/...):
[SSL]
https-enabled=true
ssl-key-file=...
ssl-cert-file=...
ssl-cacert-file=...
You can compare the keys/certs using openssl.

Was the provider created using egine-setup?

For testing purposes you can change the "https-enabled" to false and try
connecting using http.

Thanks,
Marcin

On Thu, Feb 8, 2018 at 12:58 PM, Ilya Fedotov  wrote:

> Hello, Georgy
>
>  Maybe, the problem have the different domain name and name your node
> name(local domain), and certificate note valid.
>
>
>
> with br, Ilya
>
> 2018-02-05 22:36 GMT+03:00 George Sitov :
>
>> Hello!
>>
>> I have a problem  wiith configure  external provider.
>>
>> Edit config file - ovirt-provider-ovn.conf, set ssl parameters.
>> systemctl start ovirt-provider-ovn start without problem.
>> In external  proveder in web gui i set:
>> Provider URL:  https://ovirt.mydomain.com:9696
>> Username: admin@internal
>> Authentication URL: https://ovirt.mydomain.com:35357/v2.0/
>> But after i press test  button i see error -  Failed to communicate with
>> the external provider, see log for additional details.
>>
>> /var/log/ovirt-engine/engine.log:
>> 2018-02-05 21:33:55,517+02 ERROR [org.ovirt.engine.core.bll.pro
>> vider.network.openstack.BaseNetworkProviderProxy] (default task-29)
>> [69fa312e-6e2e-4925-b081-385beba18a6a] Bad Gateway (OpenStack response
>> error code: 502)
>> 2018-02-05 21:33:55,517+02 ERROR [org.ovirt.engine.core.bll.pro
>> vider.TestProviderConnectivityCommand] (default task-29)
>> [69fa312e-6e2e-4925-b081-385beba18a6a] Command '
>> org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand'
>> failed: EngineException: (Failed with error PROVIDER_FAILURE and code 5050)
>>
>> In /var/log/ovirt-provider-ovn.log:
>>
>> 2018-02-05 21:33:55,510   Starting new HTTPS connection (1):
>> ovirt.astrecdata.com
>> 2018-02-05 21:33:55,516   [SSL: CERTIFICATE_VERIFY_FAILED] certificate
>> verify failed (_ssl.c:579)
>> Traceback (most recent call last):
>>   File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line
>> 126, in _handle_request
>> method, path_parts, content)
>>   File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py",
>> line 176, in handle_request
>> return self.call_response_handler(handler, content, parameters)
>>   File "/usr/share/ovirt-provider-ovn/handlers/keystone.py", line 33, in
>> call_response_handler
>> return response_handler(content, parameters)
>>   File "/usr/share/ovirt-provider-ovn/handlers/keystone_responses.py",
>> line 60, in post_tokens
>> user_password=user_password)
>>   File "/usr/share/ovirt-provider-ovn/auth/plugin_facade.py", line 26,
>> in create_token
>> return auth.core.plugin.create_token(user_at_domain, user_password)
>>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/plugin.py",
>> line 48, in create_token
>> timeout=self._timeout())
>>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line
>> 62, in create_token
>> username, password, engine_url, ca_file, timeout)
>>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line
>> 53, in wrapper
>> response = func(*args, **kwargs)
>>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line
>> 46, in wrapper
>> raise BadGateway(e)
>> BadGateway: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
>> (_ssl.c:579)
>>
>> Whan i do wrong ?
>> Please help.
>>
>> 
>> With best regards  Georgii.
>>
>> ___
>> 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 mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Importing Libvirt Kvm Vms to oVirt Status: Released in oVirt 4.2 using ssh - Failed to communicate with the external provider

2018-02-08 Thread Petr Kotas
You can generate one :). There are different guides for different platforms.

The link I sent is the good start on where to put the keys and how to set
it up.

Petr

On Thu, Feb 8, 2018 at 3:09 PM, maoz zadok  wrote:

> Using the command line on the engine machine (as root) works fine. I
> don't use ssh key from the agent GUI but the authentication section (with
> root user and password),
> I think that it's a bug, I manage to migrate with TCP but I just want to
> let you know.
>
> is it possible to use ssh-key from the agent GUI? how can I get the key?
>
> On Thu, Feb 8, 2018 at 2:51 PM, Petr Kotas  wrote:
>
>> Hi Maoz,
>>
>> it looks like cannot connect due to wrong setup of ssh keys. Which linux
>> are you using?
>> The guide for setting the ssh connection to  libvirt is here:
>> https://wiki.libvirt.org/page/SSHSetup
>>
>> May it helps?
>>
>> Petr
>>
>> On Wed, Feb 7, 2018 at 10:53 PM, maoz zadok  wrote:
>>
>>> Hello there,
>>>
>>> I'm following https://www.ovirt.org/develop/
>>> release-management/features/virt/KvmToOvirt/ guide in order to import
>>> VMS from Libvirt to oVirt using ssh.
>>>  URL:  "qemu+ssh://host1.example.org/system"
>>>
>>> and get the following error:
>>> Failed to communicate with the external provider, see log for additional
>>> details.
>>>
>>>
>>> *oVirt agent log:*
>>>
>>> *- Failed to retrieve VMs information from external server
>>> qemu+ssh://XXX.XXX.XXX.XXX/system*
>>> *- VDSM XXX command GetVmsNamesFromExternalProviderVDS failed: Cannot
>>> recv data: Host key verification failed.: Connection reset by peer*
>>>
>>>
>>>
>>> *remote host sshd DEBUG log:*
>>> *Feb  7 16:38:29 XXX sshd[110005]: Connection from XXX.XXX.XXX.147 port
>>> 48148 on XXX.XXX.XXX.123 port 22*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Client protocol version 2.0;
>>> client software version OpenSSH_7.4*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: match: OpenSSH_7.4 pat
>>> OpenSSH* compat 0x0400*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Local version string
>>> SSH-2.0-OpenSSH_7.4*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Enabling compatibility mode
>>> for protocol 2.0*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SELinux support disabled
>>> [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: permanently_set_uid: 74/74
>>> [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: list_hostkey_types:
>>> ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_KEXINIT sent
>>> [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_KEXINIT received
>>> [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: algorithm:
>>> curve25519-sha256 [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: host key algorithm:
>>> ecdsa-sha2-nistp256 [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: client->server cipher:
>>> chacha20-poly1...@openssh.com  MAC:
>>>  compression: none [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: server->client cipher:
>>> chacha20-poly1...@openssh.com  MAC:
>>>  compression: none [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: curve25519-sha256
>>> need=64 dh_need=64 [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: curve25519-sha256
>>> need=64 dh_need=64 [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: expecting
>>> SSH2_MSG_KEX_ECDH_INIT [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: rekey after 134217728 blocks
>>> [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_NEWKEYS sent
>>> [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: expecting SSH2_MSG_NEWKEYS
>>> [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: Connection closed by XXX.XXX.XXX.147
>>> port 48148 [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: do_cleanup [preauth]*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: do_cleanup*
>>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Killing privsep child 110006*
>>> *Feb  7 16:38:29 XXX sshd[109922]: debug1: Forked child 110007.*
>>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Set /proc/self/oom_score_adj
>>> to 0*
>>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: rexec start in 5 out 5
>>> newsock 5 pipe 7 sock 8*
>>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: inetd sockets after dupping:
>>> 3, 3*
>>> *Feb  7 16:38:29 XXX sshd[110007]: Connection from XXX.XXX.XXX.147 port
>>> 48150 on XXX.XXX.XXX.123 port 22*
>>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Client protocol version 2.0;
>>> client software version OpenSSH_7.4*
>>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: match: OpenSSH_7.4 pat
>>> OpenSSH* compat 0x0400*
>>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Local version string
>>> SSH-2.0-OpenSSH_7.4*
>>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Enabling compatibility mode
>>> for protocol 2.0*
>>> *Feb  

Re: [ovirt-users] Importing Libvirt Kvm Vms to oVirt Status: Released in oVirt 4.2 using ssh - Failed to communicate with the external provider

2018-02-08 Thread maoz zadok
Using the command line on the engine machine (as root) works fine. I
don't use ssh key from the agent GUI but the authentication section (with
root user and password),
I think that it's a bug, I manage to migrate with TCP but I just want to
let you know.

is it possible to use ssh-key from the agent GUI? how can I get the key?

On Thu, Feb 8, 2018 at 2:51 PM, Petr Kotas  wrote:

> Hi Maoz,
>
> it looks like cannot connect due to wrong setup of ssh keys. Which linux
> are you using?
> The guide for setting the ssh connection to  libvirt is here:
> https://wiki.libvirt.org/page/SSHSetup
>
> May it helps?
>
> Petr
>
> On Wed, Feb 7, 2018 at 10:53 PM, maoz zadok  wrote:
>
>> Hello there,
>>
>> I'm following https://www.ovirt.org/develop/
>> release-management/features/virt/KvmToOvirt/ guide in order to import
>> VMS from Libvirt to oVirt using ssh.
>>  URL:  "qemu+ssh://host1.example.org/system"
>>
>> and get the following error:
>> Failed to communicate with the external provider, see log for additional
>> details.
>>
>>
>> *oVirt agent log:*
>>
>> *- Failed to retrieve VMs information from external server
>> qemu+ssh://XXX.XXX.XXX.XXX/system*
>> *- VDSM XXX command GetVmsNamesFromExternalProviderVDS failed: Cannot
>> recv data: Host key verification failed.: Connection reset by peer*
>>
>>
>>
>> *remote host sshd DEBUG log:*
>> *Feb  7 16:38:29 XXX sshd[110005]: Connection from XXX.XXX.XXX.147 port
>> 48148 on XXX.XXX.XXX.123 port 22*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Client protocol version 2.0;
>> client software version OpenSSH_7.4*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: match: OpenSSH_7.4 pat
>> OpenSSH* compat 0x0400*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Local version string
>> SSH-2.0-OpenSSH_7.4*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Enabling compatibility mode
>> for protocol 2.0*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SELinux support disabled
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: permanently_set_uid: 74/74
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: list_hostkey_types:
>> ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_KEXINIT sent
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_KEXINIT received
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: algorithm:
>> curve25519-sha256 [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: host key algorithm:
>> ecdsa-sha2-nistp256 [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: client->server cipher:
>> chacha20-poly1...@openssh.com  MAC:
>>  compression: none [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: server->client cipher:
>> chacha20-poly1...@openssh.com  MAC:
>>  compression: none [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: curve25519-sha256 need=64
>> dh_need=64 [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: curve25519-sha256 need=64
>> dh_need=64 [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: expecting
>> SSH2_MSG_KEX_ECDH_INIT [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: rekey after 134217728 blocks
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_NEWKEYS sent
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: expecting SSH2_MSG_NEWKEYS
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: Connection closed by XXX.XXX.XXX.147
>> port 48148 [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: do_cleanup [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: do_cleanup*
>> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Killing privsep child 110006*
>> *Feb  7 16:38:29 XXX sshd[109922]: debug1: Forked child 110007.*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Set /proc/self/oom_score_adj
>> to 0*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: rexec start in 5 out 5 newsock
>> 5 pipe 7 sock 8*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: inetd sockets after dupping:
>> 3, 3*
>> *Feb  7 16:38:29 XXX sshd[110007]: Connection from XXX.XXX.XXX.147 port
>> 48150 on XXX.XXX.XXX.123 port 22*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Client protocol version 2.0;
>> client software version OpenSSH_7.4*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: match: OpenSSH_7.4 pat
>> OpenSSH* compat 0x0400*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Local version string
>> SSH-2.0-OpenSSH_7.4*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Enabling compatibility mode
>> for protocol 2.0*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: SELinux support disabled
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: permanently_set_uid: 74/74
>> [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110007]: debug1: list_hostkey_types:
>> ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]*
>> *Feb  7 16:38:29 XXX sshd[110007]: 

Re: [ovirt-users] qcow2 images corruption

2018-02-08 Thread Nicolas Ecarnot

Le 08/02/2018 à 13:59, Yaniv Kaul a écrit :



On Feb 7, 2018 7:08 PM, "Nicolas Ecarnot" > wrote:


Hello,

TL; DR : qcow2 images keep getting corrupted. Any workaround?

Long version:
This discussion has already been launched by me on the oVirt and
on qemu-block mailing list, under similar circumstances but I
learned further things since months and here are some informations :

- We are using 2 oVirt 3.6.7.5-1.el7.centos datacenters, using
CentOS 7.{2,3} hosts
- Hosts :
  - CentOS 7.2 1511 :
    - Kernel = 3.10.0 327
    - KVM : 2.3.0-31
    - libvirt : 1.2.17
    - vdsm : 4.17.32-1
  - CentOS 7.3 1611 :
    - Kernel 3.10.0 514
    - KVM : 2.3.0-31
    - libvirt 2.0.0-10
    - vdsm : 4.17.32-1


All are somewhat old releases. I suggest upgrading to the latest RHEL 
and qemu-kvm bits.


Later on, upgrade oVirt.
Y.

Hello Yaniv,

We could discuss for hours about the fact that CentOS 7.3 was released 
in January 2017, thus not that old.
And also discuss for hours explaining the gap between developers' will 
to push their freshest releases and the curb we - industry users - put 
on adopting such new versions. In my case, the virtualization 
infrastructure is just one of the +30 domains I have to master everyday, 
and the more stable the better.
In the setup described previously, the qemu qcow2 images were correct, 
then not. We did not change anything. We have to find a workaround and 
we need your expertise.


Not understanding the cause of the corruption threatens us to the same 
situation in oVirt 4.2.


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


Re: [ovirt-users] Issue with 4.2.1 RC and SSL

2018-02-08 Thread Yedidyah Bar David
On Thu, Feb 8, 2018 at 2:42 PM, Petr Kotas  wrote:
> Hi Stack,
>
> have you tried it on other linux distributions? Scientific is not officially
> supported.
>
> My guess based on your log is there are somewhere missing certificates,
> maybe different path?.
> You can check the paths by the documentation:
> https://www.ovirt.org/develop/release-management/features/infra/pki/#vdsm
>
> Hope this helps.
>
> Petr
>
>
>
> On Thu, Feb 8, 2018 at 1:13 AM, ~Stack~  wrote:
>>
>> Greetings,
>>
>> I was having a lot of issues with 4.2 and 95% of them are in the change
>> logs for 4.2.1. Since this is a new build, I just blew everything away
>> and started from scratch with the RC release.
>>
>> The very first thing that I did after the engine-config was to set up my
>> SSL cert. I followed the directions from here:
>> https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL/
>>
>> Logged in the first time to the web interface and everything worked!
>> Great.
>>
>> Install my hosts (also completely fresh installs - Scientific Linux 7
>> fully updated) and none would finish the install...
>>
>>
>> I can send the full host debug log if you want, however, I'm pretty sure
>> that the problem is because of the SSL somewhere. I've cut/pasted the
>> relevant part.

Please check/share also engine.log of the relevant time frame. Thanks.

>>
>> Any advice/help, please?
>>
>> Thanks!
>> ~Stack~
>>
>>
>> 2018-02-07 16:56:21,697-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   **%EventEnd STAGE misc METHOD
>> otopi.plugins.ovirt_host_deploy.tune.tuned.Plugin._misc (None)
>> 2018-02-07 16:56:21,698-0600 DEBUG otopi.context
>> context._executeMethod:128 Stage misc METHOD
>> otopi.plugins.ovirt_host_deploy.vdsm.vdsmid.Plugin._store_id
>> 2018-02-07 16:56:21,698-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   **%EventStart STAGE misc METHOD
>> otopi.plugins.ovirt_host_deploy.vdsm.vdsmid.Plugin._store_id (None)
>> 2018-02-07 16:56:21,699-0600 DEBUG otopi.transaction
>> transaction._prepare:61 preparing 'File transaction for
>> '/etc/vdsm/vdsm.id''
>> 2018-02-07 16:56:21,699-0600 DEBUG otopi.filetransaction
>> filetransaction.prepare:183 file '/etc/vdsm/vdsm.id' missing
>> 2018-02-07 16:56:21,705-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   **%EventEnd STAGE misc METHOD
>> otopi.plugins.ovirt_host_deploy.vdsm.vdsmid.Plugin._store_id (None)
>> 2018-02-07 16:56:21,706-0600 DEBUG otopi.context
>> context._executeMethod:128 Stage misc METHOD
>> otopi.plugins.ovirt_host_deploy.vdsmhooks.hooks.Plugin._hooks
>> 2018-02-07 16:56:21,706-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   **%EventStart STAGE misc METHOD
>> otopi.plugins.ovirt_host_deploy.vdsmhooks.hooks.Plugin._hooks (None)
>> 2018-02-07 16:56:21,707-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   **%EventEnd STAGE misc METHOD
>> otopi.plugins.ovirt_host_deploy.vdsmhooks.hooks.Plugin._hooks (None)
>> 2018-02-07 16:56:21,707-0600 DEBUG otopi.context
>> context._executeMethod:128 Stage misc METHOD
>> otopi.plugins.ovirt_host_common.vdsm.pki.Plugin._misc
>> 2018-02-07 16:56:21,708-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   **%EventStart STAGE misc METHOD
>> otopi.plugins.ovirt_host_common.vdsm.pki.Plugin._misc (None)
>> 2018-02-07 16:56:21,708-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ### Setting up PKI
>> 2018-02-07 16:56:21,709-0600 DEBUG
>> otopi.plugins.ovirt_host_common.vdsm.pki plugin.executeRaw:813 execute:
>> ('/usr/bin/openssl', 'req', '-new', '-newkey', 'rsa:2048', '-nodes',
>> '-subj', '/', '-keyout', '/tmp/tmpQkrIuV.tmp'), executable='None',
>> cwd='None', env=None
>> 2018-02-07 16:56:21,756-0600 DEBUG
>> otopi.plugins.ovirt_host_common.vdsm.pki plugin.executeRaw:863
>> execute-result: ('/usr/bin/openssl', 'req', '-new', '-newkey',
>> 'rsa:2048', '-nodes', '-subj', '/', '-keyout', '/tmp/tmpQkrIuV.tmp'), rc=0
>> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ###
>> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ###
>> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ### Please issue VDSM
>> certificate based on this certificate request
>> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ###
>> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ***D:MULTI-STRING
>> VDSM_CERTIFICATE_REQUEST --=451b80dc-996f-432e-9e4f-2b29ef6d1141=--
>> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine

Re: [ovirt-users] Engine AAA LDAP startTLS Protocol Issue

2018-02-08 Thread Alan Griffiths
That works. Thanks.

On 8 February 2018 at 12:56, Ondra Machacek  wrote:
> On 02/08/2018 11:04 AM, Alan Griffiths wrote:
>>
>> Hi,
>>
>> Trying to configure Engine to authenticate against OpenLDAP and I seem
>> to be hitting a protocol bug.
>>
>> Attempts to test the login during the setup fail with
>>
>> 2018-02-07 12:27:37,872Z WARNING Exception: The connection reader was
>> unable to successfully complete TLS negotiation:
>> SSLException(message='Received fatal alert: protocol_version',
>> trace='getSSLException(Alerts.java:208) /
>> getSSLException(Alerts.java:154) / recvAlert(SSLSocketImpl.java:2033)
>> / readRecord(SSLSocketImpl.java:1135) /
>> performInitialHandshake(SSLSocketImpl.java:1385) /
>> startHandshake(SSLSocketImpl.java:1413) /
>> startHandshake(SSLSocketImpl.java:1397) /
>> run(LDAPConnectionReader.java:301)', revision=0)
>>
>> Running a packet trace I see that it's trying to negotiate with TLS
>> 1.0, but my LDAP server only support TLS 1.2.
>
>
> I've sent a fix:
>
>  https://gerrit.ovirt.org/87327
>
> To workaround it just please add to you profile properties file:
>
>  pool.default.ssl.startTLSProtocol = TLSv1.2
>
>>
>> This looks like a regression as it works fine in 4.0.
>>
>> I see the issue in both 4.1 and 4.2
>>
>> 4.1.9.1
>> 4.2.0.2
>>
>> Should I submit a bug?
>>
>> Thanks,
>>
>> Alan
>> ___
>> 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: [ovirt-users] qcow2 images corruption

2018-02-08 Thread Yaniv Kaul
On Feb 7, 2018 7:08 PM, "Nicolas Ecarnot"  wrote:

Hello,

TL; DR : qcow2 images keep getting corrupted. Any workaround?

Long version:
This discussion has already been launched by me on the oVirt and on
qemu-block mailing list, under similar circumstances but I learned further
things since months and here are some informations :

- We are using 2 oVirt 3.6.7.5-1.el7.centos datacenters, using CentOS
7.{2,3} hosts
- Hosts :
  - CentOS 7.2 1511 :
- Kernel = 3.10.0 327
- KVM : 2.3.0-31
- libvirt : 1.2.17
- vdsm : 4.17.32-1
  - CentOS 7.3 1611 :
- Kernel 3.10.0 514
- KVM : 2.3.0-31
- libvirt 2.0.0-10
- vdsm : 4.17.32-1


All are somewhat old releases. I suggest upgrading to the latest RHEL and
qemu-kvm bits.

Later on, upgrade oVirt.
Y.

- Our storage is 2 Equallogic SANs connected via iSCSI on a dedicated
network
- Depends on weeks, but all in all, there are around 32 hosts, 8 storage
domains and for various reasons, very few VMs (less than 200).
- One peculiar point is that most of our VMs are provided an additional
dedicated network interface that is iSCSI-connected to some volumes of our
SAN - these volumes not being part of the oVirt setup. That could lead to a
lot of additional iSCSI traffic.

>From times to times, a random VM appears paused by oVirt.
Digging into the oVirt engine logs, then into the host vdsm logs, it
appears that the host considers the qcow2 image as corrupted.
Along what I consider as a conservative behavior, vdsm stops any
interaction with this image and marks it as paused.
Any try to unpause it leads to the same conservative pause.

After having found (https://access.redhat.com/solutions/1173623) the right
logical volume hosting the qcow2 image, I can run qemu-img check on it.
- On 80% of my VMs, I find no errors.
- On 15% of them, I find Leaked cluster errors that I can correct using
"qemu-img check -r all"
- On 5% of them, I find Leaked clusters errors and further fatal errors,
which can not be corrected with qemu-img.
In rare cases, qemu-img can correct them, but destroys large parts of the
image (becomes unusable), and on other cases it can not correct them at all.

Months ago, I already sent a similar message but the error message was
about No space left on device (https://www.mail-archive.com/
qemu-bl...@gnu.org/msg00110.html).

This time, I don't have this message about space, but only corruption.

I kept reading and found a similar discussion in the Proxmox group :
https://lists.ovirt.org/pipermail/users/2018-February/086750.html

https://forum.proxmox.com/threads/qcow2-corruption-after-
snapshot-or-heavy-disk-i-o.32865/page-2

What I read similar to my case is :
- usage of qcow2
- heavy disk I/O
- using the virtio-blk driver

In the proxmox thread, they tend to say that using virtio-scsi is the
solution. Having asked this question to oVirt experts (
https://lists.ovirt.org/pipermail/users/2018-February/086753.html) but it's
not clear the driver is to blame.

I agree with the answer Yaniv Kaul gave to me, saying I have to properly
report the issue, so I'm longing to know which peculiar information I can
give you now.

As you can imagine, all this setup is in production, and for most of the
VMs, I can not "play" with them. Moreover, we launched a campaign of
nightly stopping every VM, qemu-img check them one by one, then boot.
So it might take some time before I find another corrupted image.
(which I'll preciously store for debug)

Other informations : We very rarely do snapshots, but I'm close to imagine
that automated migrations of VMs could trigger similar behaviors on qcow2
images.

Last point about the versions we use : yes that's old, yes we're planning
to upgrade, but we don't know when.

Regards,

-- 
Nicolas ECARNOT
___
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: [ovirt-users] Engine AAA LDAP startTLS Protocol Issue

2018-02-08 Thread Ondra Machacek

On 02/08/2018 11:04 AM, Alan Griffiths wrote:

Hi,

Trying to configure Engine to authenticate against OpenLDAP and I seem
to be hitting a protocol bug.

Attempts to test the login during the setup fail with

2018-02-07 12:27:37,872Z WARNING Exception: The connection reader was
unable to successfully complete TLS negotiation:
SSLException(message='Received fatal alert: protocol_version',
trace='getSSLException(Alerts.java:208) /
getSSLException(Alerts.java:154) / recvAlert(SSLSocketImpl.java:2033)
/ readRecord(SSLSocketImpl.java:1135) /
performInitialHandshake(SSLSocketImpl.java:1385) /
startHandshake(SSLSocketImpl.java:1413) /
startHandshake(SSLSocketImpl.java:1397) /
run(LDAPConnectionReader.java:301)', revision=0)

Running a packet trace I see that it's trying to negotiate with TLS
1.0, but my LDAP server only support TLS 1.2.


I've sent a fix:

 https://gerrit.ovirt.org/87327

To workaround it just please add to you profile properties file:

 pool.default.ssl.startTLSProtocol = TLSv1.2



This looks like a regression as it works fine in 4.0.

I see the issue in both 4.1 and 4.2

4.1.9.1
4.2.0.2

Should I submit a bug?

Thanks,

Alan
___
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: [ovirt-users] Importing Libvirt Kvm Vms to oVirt Status: Released in oVirt 4.2 using ssh - Failed to communicate with the external provider

2018-02-08 Thread Petr Kotas
Hi Maoz,

it looks like cannot connect due to wrong setup of ssh keys. Which linux
are you using?
The guide for setting the ssh connection to  libvirt is here:
https://wiki.libvirt.org/page/SSHSetup

May it helps?

Petr

On Wed, Feb 7, 2018 at 10:53 PM, maoz zadok  wrote:

> Hello there,
>
> I'm following https://www.ovirt.org/develop/release-management/features/
> virt/KvmToOvirt/ guide in order to import VMS from Libvirt to oVirt using
> ssh.
>  URL:  "qemu+ssh://host1.example.org/system"
>
> and get the following error:
> Failed to communicate with the external provider, see log for additional
> details.
>
>
> *oVirt agent log:*
>
> *- Failed to retrieve VMs information from external server
> qemu+ssh://XXX.XXX.XXX.XXX/system*
> *- VDSM XXX command GetVmsNamesFromExternalProviderVDS failed: Cannot recv
> data: Host key verification failed.: Connection reset by peer*
>
>
>
> *remote host sshd DEBUG log:*
> *Feb  7 16:38:29 XXX sshd[110005]: Connection from XXX.XXX.XXX.147 port
> 48148 on XXX.XXX.XXX.123 port 22*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Client protocol version 2.0;
> client software version OpenSSH_7.4*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: match: OpenSSH_7.4 pat OpenSSH*
> compat 0x0400*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Local version string
> SSH-2.0-OpenSSH_7.4*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Enabling compatibility mode for
> protocol 2.0*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SELinux support disabled
> [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: permanently_set_uid: 74/74
> [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: list_hostkey_types:
> ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_KEXINIT sent [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_KEXINIT received
> [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: algorithm:
> curve25519-sha256 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: host key algorithm:
> ecdsa-sha2-nistp256 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: client->server cipher:
> chacha20-poly1...@openssh.com  MAC:
>  compression: none [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: server->client cipher:
> chacha20-poly1...@openssh.com  MAC:
>  compression: none [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: curve25519-sha256 need=64
> dh_need=64 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: kex: curve25519-sha256 need=64
> dh_need=64 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: expecting
> SSH2_MSG_KEX_ECDH_INIT [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: rekey after 134217728 blocks
> [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: SSH2_MSG_NEWKEYS sent [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: expecting SSH2_MSG_NEWKEYS
> [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: Connection closed by XXX.XXX.XXX.147
> port 48148 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: do_cleanup [preauth]*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: do_cleanup*
> *Feb  7 16:38:29 XXX sshd[110005]: debug1: Killing privsep child 110006*
> *Feb  7 16:38:29 XXX sshd[109922]: debug1: Forked child 110007.*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Set /proc/self/oom_score_adj to
> 0*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: rexec start in 5 out 5 newsock
> 5 pipe 7 sock 8*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: inetd sockets after dupping: 3,
> 3*
> *Feb  7 16:38:29 XXX sshd[110007]: Connection from XXX.XXX.XXX.147 port
> 48150 on XXX.XXX.XXX.123 port 22*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Client protocol version 2.0;
> client software version OpenSSH_7.4*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: match: OpenSSH_7.4 pat OpenSSH*
> compat 0x0400*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Local version string
> SSH-2.0-OpenSSH_7.4*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: Enabling compatibility mode for
> protocol 2.0*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: SELinux support disabled
> [preauth]*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: permanently_set_uid: 74/74
> [preauth]*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: list_hostkey_types:
> ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: SSH2_MSG_KEXINIT sent [preauth]*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: SSH2_MSG_KEXINIT received
> [preauth]*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: kex: algorithm:
> curve25519-sha256 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: kex: host key algorithm:
> ecdsa-sha2-nistp256 [preauth]*
> *Feb  7 16:38:29 XXX sshd[110007]: debug1: kex: client->server cipher:
> chacha20-poly1...@openssh.com  MAC:
>  compression: none [preauth]*
> *Feb  7 16:38:29 XXX 

Re: [ovirt-users] Issue with 4.2.1 RC and SSL

2018-02-08 Thread Petr Kotas
Hi Stack,

have you tried it on other linux distributions? Scientific is not
officially supported.

My guess based on your log is there are somewhere missing certificates,
maybe different path?.
You can check the paths by the documentation:
https://www.ovirt.org/develop/release-management/features/infra/pki/#vdsm

Hope this helps.

Petr



On Thu, Feb 8, 2018 at 1:13 AM, ~Stack~  wrote:

> Greetings,
>
> I was having a lot of issues with 4.2 and 95% of them are in the change
> logs for 4.2.1. Since this is a new build, I just blew everything away
> and started from scratch with the RC release.
>
> The very first thing that I did after the engine-config was to set up my
> SSL cert. I followed the directions from here:
> https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL/
>
> Logged in the first time to the web interface and everything worked! Great.
>
> Install my hosts (also completely fresh installs - Scientific Linux 7
> fully updated) and none would finish the install...
>
>
> I can send the full host debug log if you want, however, I'm pretty sure
> that the problem is because of the SSL somewhere. I've cut/pasted the
> relevant part.
>
> Any advice/help, please?
>
> Thanks!
> ~Stack~
>
>
> 2018-02-07 16:56:21,697-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   **%EventEnd STAGE misc METHOD
> otopi.plugins.ovirt_host_deploy.tune.tuned.Plugin._misc (None)
> 2018-02-07 16:56:21,698-0600 DEBUG otopi.context
> context._executeMethod:128 Stage misc METHOD
> otopi.plugins.ovirt_host_deploy.vdsm.vdsmid.Plugin._store_id
> 2018-02-07 16:56:21,698-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   **%EventStart STAGE misc METHOD
> otopi.plugins.ovirt_host_deploy.vdsm.vdsmid.Plugin._store_id (None)
> 2018-02-07 16:56:21,699-0600 DEBUG otopi.transaction
> transaction._prepare:61 preparing 'File transaction for '/etc/vdsm/vdsm.id
> ''
> 2018-02-07 16:56:21,699-0600 DEBUG otopi.filetransaction
> filetransaction.prepare:183 file '/etc/vdsm/vdsm.id' missing
> 2018-02-07 16:56:21,705-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   **%EventEnd STAGE misc METHOD
> otopi.plugins.ovirt_host_deploy.vdsm.vdsmid.Plugin._store_id (None)
> 2018-02-07 16:56:21,706-0600 DEBUG otopi.context
> context._executeMethod:128 Stage misc METHOD
> otopi.plugins.ovirt_host_deploy.vdsmhooks.hooks.Plugin._hooks
> 2018-02-07 16:56:21,706-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   **%EventStart STAGE misc METHOD
> otopi.plugins.ovirt_host_deploy.vdsmhooks.hooks.Plugin._hooks (None)
> 2018-02-07 16:56:21,707-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   **%EventEnd STAGE misc METHOD
> otopi.plugins.ovirt_host_deploy.vdsmhooks.hooks.Plugin._hooks (None)
> 2018-02-07 16:56:21,707-0600 DEBUG otopi.context
> context._executeMethod:128 Stage misc METHOD
> otopi.plugins.ovirt_host_common.vdsm.pki.Plugin._misc
> 2018-02-07 16:56:21,708-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   **%EventStart STAGE misc METHOD
> otopi.plugins.ovirt_host_common.vdsm.pki.Plugin._misc (None)
> 2018-02-07 16:56:21,708-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ### Setting up PKI
> 2018-02-07 16:56:21,709-0600 DEBUG
> otopi.plugins.ovirt_host_common.vdsm.pki plugin.executeRaw:813 execute:
> ('/usr/bin/openssl', 'req', '-new', '-newkey', 'rsa:2048', '-nodes',
> '-subj', '/', '-keyout', '/tmp/tmpQkrIuV.tmp'), executable='None',
> cwd='None', env=None
> 2018-02-07 16:56:21,756-0600 DEBUG
> otopi.plugins.ovirt_host_common.vdsm.pki plugin.executeRaw:863
> execute-result: ('/usr/bin/openssl', 'req', '-new', '-newkey',
> 'rsa:2048', '-nodes', '-subj', '/', '-keyout', '/tmp/tmpQkrIuV.tmp'), rc=0
> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ###
> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ###
> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ### Please issue VDSM
> certificate based on this certificate request
> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ###
> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ***D:MULTI-STRING
> VDSM_CERTIFICATE_REQUEST --=451b80dc-996f-432e-9e4f-2b29ef6d1141=--
> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   -BEGIN CERTIFICATE
> REQUEST-
> 2018-02-07 16:56:21,757-0600 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND
> MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMZm

[ovirt-users] effectiveness of "discard=unmap"

2018-02-08 Thread Matthias Leopold

Hi,

i'm sorry to bother you again with my ignorance of the DISCARD feature 
for block devices in general.


after finding several ways to enable "discard=unmap" for oVirt disks 
(via standard GUI option for iSCSI disks or via "diskunmap" custom 
property for Cinder disks) i wanted to check in the guest for the 
effectiveness of this feature. to my surprise i couldn't find a 
difference between Linux guests with and without "discard=unmap" enabled 
in the VM. "lsblk -D" reports the same in both cases and also 
fstrim/blkdiscard commands appear to work with no difference. Why is 
this? Do i have to look at the underlying storage to find out what 
really happens? Shouldn't this be visible in the guest OS?


thx
matthias

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


Re: [ovirt-users] ovn problem - Failed to communicate with the external provider, see log for additional details.

2018-02-08 Thread Ilya Fedotov
Hello, Georgy

 Maybe, the problem have the different domain name and name your node
name(local domain), and certificate note valid.



with br, Ilya

2018-02-05 22:36 GMT+03:00 George Sitov :

> Hello!
>
> I have a problem  wiith configure  external provider.
>
> Edit config file - ovirt-provider-ovn.conf, set ssl parameters.
> systemctl start ovirt-provider-ovn start without problem.
> In external  proveder in web gui i set:
> Provider URL:  https://ovirt.mydomain.com:9696
> Username: admin@internal
> Authentication URL: https://ovirt.mydomain.com:35357/v2.0/
> But after i press test  button i see error -  Failed to communicate with
> the external provider, see log for additional details.
>
> /var/log/ovirt-engine/engine.log:
> 2018-02-05 21:33:55,517+02 ERROR [org.ovirt.engine.core.bll.
> provider.network.openstack.BaseNetworkProviderProxy] (default task-29)
> [69fa312e-6e2e-4925-b081-385beba18a6a] Bad Gateway (OpenStack response
> error code: 502)
> 2018-02-05 21:33:55,517+02 ERROR [org.ovirt.engine.core.bll.provider.
> TestProviderConnectivityCommand] (default task-29)
> [69fa312e-6e2e-4925-b081-385beba18a6a] Command 'org.ovirt.engine.core.bll.
> provider.TestProviderConnectivityCommand' failed: EngineException:
> (Failed with error PROVIDER_FAILURE and code 5050)
>
> In /var/log/ovirt-provider-ovn.log:
>
> 2018-02-05 21:33:55,510   Starting new HTTPS connection (1):
> ovirt.astrecdata.com
> 2018-02-05 21:33:55,516   [SSL: CERTIFICATE_VERIFY_FAILED] certificate
> verify failed (_ssl.c:579)
> Traceback (most recent call last):
>   File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line
> 126, in _handle_request
> method, path_parts, content)
>   File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py",
> line 176, in handle_request
> return self.call_response_handler(handler, content, parameters)
>   File "/usr/share/ovirt-provider-ovn/handlers/keystone.py", line 33, in
> call_response_handler
> return response_handler(content, parameters)
>   File "/usr/share/ovirt-provider-ovn/handlers/keystone_responses.py",
> line 60, in post_tokens
> user_password=user_password)
>   File "/usr/share/ovirt-provider-ovn/auth/plugin_facade.py", line 26, in
> create_token
> return auth.core.plugin.create_token(user_at_domain, user_password)
>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/plugin.py", line
> 48, in create_token
> timeout=self._timeout())
>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line
> 62, in create_token
> username, password, engine_url, ca_file, timeout)
>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line
> 53, in wrapper
> response = func(*args, **kwargs)
>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line
> 46, in wrapper
> raise BadGateway(e)
> BadGateway: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
> (_ssl.c:579)
>
> Whan i do wrong ?
> Please help.
>
> 
> With best regards  Georgii.
>
> ___
> 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: [ovirt-users] oVirt DR: ansible with 4.1, only a subset of storage domain replicated

2018-02-08 Thread Maor Lipchuk
On Thu, Feb 8, 2018 at 10:34 AM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

> On Tue, Feb 6, 2018 at 9:33 PM, Maor Lipchuk  wrote:
> [cut]
> >> What i need is that informations about vms is replicated to the remote
> >> site with disk.
> >> In an older test i had the issue that disks were replicated to remote
> >> site, but vm configuration not!
> >> I've found disks in the "Disk"  tab of storage domain, but nothing on VM
> >> Import.
> >
> >
> >
> > Can you reproduce it and attach the logs of the setup before the disaster
> > and after the recovery?
> > That could happen in case of new created VMs and Templates which were not
> > yet updated in the OVF_STORE disk, since the OVF_STORE update process was
> > not running yet before the disaster.
> > Since the time of a disaster can't be anticipated, gaps like this might
> > happen.
> >
>
> I haven't tried the recovery yet using ansible. It was an experiment
> of possible procedure to be performed manually and was on 4.0.
> I asked about this unexpected behavior and Yaniv returned me that was
> due to OVF_STORE not updated and that in 4.1 there is an api call that
> updates OVF_STORE on demand.
>
> I'm creating a new setup today and i'll test again and check if i
> still hit the issue. Anyway if the problem persist i think that
> engine, for DR purposes, should upgrade the OVF_STORE as soon as
> possible when a new vm is created or has disks added.
>


If engine will update the OVF_STORE on any VM change that could reflect the
oVirt performance since it is a heavy operation,
although we do have some ideas to change that design so every VM change
will only change the VM OVF instead of the whole OVF_STORE disk.


> [cut]
> >>
> >> Ok, but if i keep master storage domain on a non replicate volume, do
> >> i require this function?
> >
> >
> > Basically it should also fail on VM/Template registration in oVirt 4.1
> since
> > there are also other functionalities like mapping of OVF attributes which
> > was added on VM/Templates registeration.
> >
>
> What do you mean? That i could fail to import any VM/Template? In what
> case?
>


If using the fail-over in ovirt-ansible-disaster-recovery, the VM/Template
registration process is being done automatically through the ovirt-ansible
tasks and it is based on the oVirt 4.2 API.
The task which registers the VMs and the Templates is being done there
without indicating the target cluster id, since in oVirt 4.2 we already
added the cluster name in the VM's/Template's OVF.
If your engine is oVirt 4.1 the registration will fail since in oVirt 4.1
the cluster id is mandatory.


>
> Another question:
>
> we have 2 DCs in main site, do we require to have also 2 DCs in
> recovery site o we can import all the storage domains in a single DC
> on recovery site? There could be uuid collisions or similar?
>


I think it could work, although I suggest that the clusters should be
compatible with those configurd in the primary setup
otherwise you might encounter problems when you will try to fail back (and
also to avoid any collisions of affinity groups/labels or networks).
For example if in your primary site you had DC1 with cluster1 and DC2 with
cluster2 then your secondary setup should be DC_Secondary with cluster_A
and cluster_B.
cluster1 will be mapped to cluster_A and cluster2 will be mapped to
cluster_B.

Another thing that might be troubling is with the master domain attribute
in the mapping var file.
That attribute indicates which storage domain is master or not.
Here is an example how it is being configured in the mapping file:
- dr_domain_type: nfs
  dr_primary_dc_name: Prod
  dr_primary_name: data_number
  dr_master_domain: True
  dr_secondary_dc_name: Recovery
  dr_secondary_address:
...


In your primary site you have two master storage domains, and in your
secondary site what will probably happen is that on import of storage
domains only one of those two storage domains will be master.
Now that I think of it, it might be better to configure the master
attribute for each of the setups, like so:
  dr_primary_master_domain: True
  dr_secondary_master_domain: False


>
> Thank you so much for your replies,
>
> Luca
> --
> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
> calcoli che potrebbero essere affidati a chiunque se si usassero delle
> macchine"
> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>
> "Internet è la più grande biblioteca del mondo.
> Ma il problema è che i libri sono tutti sparsi sul pavimento"
> John Allen Paulos, Matematico (1945-vivente)
>
> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
> lorenzetto.l...@gmail.com>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Maximum time node can be offline.

2018-02-08 Thread Staniforth, Paul
Hello,

   you should be able to use the power saving cluster scheduling policy.


https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html/administration_guide/sect-Scheduling_Policies


Regards,

  Paul S.


From: users-boun...@ovirt.org  on behalf of Thomas 
Letherby 
Sent: 08 February 2018 05:51
To: users@ovirt.org
Subject: [ovirt-users] Maximum time node can be offline.

Hello all,

Is there a maximum length of time an Ovirt Node 4.2 based host can be offline 
in a cluster before it would have issues when powered back on?

The reason I ask is in my lab I currently have a three node cluster that works 
really well, however a lot of the time I only actually need the resources of 
one host, so to save power I'd like to keep the other two offline until needed.

I can always script them to boot once a week or so if I need to.

Thanks,

Thomas
To view the terms under which this email is distributed, please go to:-
http://disclaimer.leedsbeckett.ac.uk/disclaimer/disclaimer.html
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Network configuration validation error

2018-02-08 Thread spfma . tech
In fact I don't know what flow should be followed. I have found several 
documentations, but most deal with older version so I am not sure I am doing 
right.
 Is there a working documented procedure somewhere ? 

 Le 08-Feb-2018 11:17:06 +0100, mbur...@redhat.com a crit: 
  Thanks, I'm not so familiar with the hosted-engine --upgrade-appliance flow, 
can someone from the list that is familiar with such flow assist?  
 On Thu, Feb 8, 2018 at 12:10 PM,  wrote:

 Hi,   I installed my nodes with the latest packages available in repositories. 
Then I installed the self-hosted engine on one of them, created the cluster and 
added the second node.   When I encountered these network config problems and 
saw your answer, I thougt it was time to update some packages to get 
corrections.   So I just runned a "yum update" on the nodes and rebooted them.  
 Then I put the engine in global maintenance mode and tried "hosted-engine 
--upgrade-appliance" on the node hosting it.   But it failed returning me this 
cluster version error.   The engine's about windows says "Software 
Version:4.2.0.2-1.el7.centos"   And for the hosts :OS Version:RHEL - 7 
- 4.1708.el7.centos OS Description:CentOS Linux 7 (Core) Kernel 
Version:3.10.0 - 693.17.1.el7.x86_64 KVM Version:2.9.0 - 16.el7_4.13.1  
   LIBVIRT Version:libvirt-3.2.0-14.el7_4.7 VDSM 
Version:vdsm-4.20.9.3-1.el7.centos SPICE Version:0.12.8 - 2.el7.1   
  GlusterFS Version:[N/A] CEPH Version:librbd1-0.94.5-2.el7  
Regards 

 Le 08-Feb-2018 09:59:32 +0100, mbur...@redhat.com a crit: 
   Not sure i understand from which version you trying to upgrade and what is 
the exact upgrade flow, if i got it correctly, it is seems that you upgraded 
the hosts to 4.2, but engine still 4.1? What exactly the upgrade steps, please 
explain the flow., what have you done after upgrading the hosts? to what 
version?

 Cheers) 
 On Wed, Feb 7, 2018 at 3:00 PM,  wrote:

 Hi, Thanks a lot for your answer.I applied some updates at node level, but 
I forgot to upgrade the engine !   When I try to do so I get a strange error : 
"Cluster PROD is at version 4.2 which is not supported by this upgrade flow. 
Please fix it before upgrading."   Here are the installed packets on my nodes : 
python-ovirt-engine-sdk4-4.2.2-2.el7.centos.x86_64
ovirt-imageio-common-1.2.0-1.el7.centos.noarch
ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch
ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch
ovirt-setup-lib-1.1.4-1.el7.centos.noarch
ovirt-release42-4.2.0-1.el7.centos.noarch
ovirt-imageio-daemon-1.2.0-1.el7.centos.noarch
ovirt-host-dependencies-4.2.0-1.el7.centos.x86_64
ovirt-host-4.2.0-1.el7.centos.x86_64
ovirt-host-deploy-1.7.0-1.el7.centos.noarch
ovirt-hosted-engine-ha-2.2.2-1.el7.centos.noarch
ovirt-provider-ovn-driver-1.2.2-1.el7.centos.noarch
ovirt-engine-appliance-4.2-20171219.1.el7.centos.noarch
ovirt-vmconsole-host-1.0.4-1.el7.noarch
cockpit-ovirt-dashboard-0.11.3-0.1.el7.centos.noarch
ovirt-vmconsole-1.0.4-1.el7.noarch   What I am supposed to do ? I see no newer 
packages available.   Regards   

 Le 07-Feb-2018 13:23:43 +0100, mbur...@redhat.com a crit: 
Hi

 This is a bug and it was already fixed in 4.2.1.1-0.1.el7 - 
https://bugzilla.redhat.com/show_bug.cgi?id=1528906

 The no default route bug was fixed in - 
https://bugzilla.redhat.com/show_bug.cgi?id=1477589

 Thanks, 
 On Wed, Feb 7, 2018 at 1:15 PM,  wrote:

   Hi, I am experiencing a new problem : when I try to modify something in the 
network setup on the second node (added to the cluster after installing the 
engine on the other one) using the Engine GUI, I get the following error when 
validating :must match 
"^\b((25[0-5]|2[0-4]\d|[01]\d\d|\d?\d)\_){3}(25[0-5]|2[0-4]\d|[01]\d\d|\d?\d)"
 Attribut : ipConfiguration.iPv4Addresses[0].gateway   Moreover, on the general 
status of ther server, I have a "Host has no default route" alert.   The 
ovirtmgmt network has a defined gateway of course, and the storage network has 
none because it is not required. Both server have the same setup, with 
different addresses of course :-)   I have not been able to find anything 
useful in the logs.   Is this a bug or am I doing something wrong ?   Regards 

-
FreeMail powered by mail.fr 
___
 Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

-- 

Michael Burman 

Senior Quality engineer - rhv network - redhat israel 

Red Hat 

 mbur...@redhat.com  M: 0545355725 IM: mburman 

-
FreeMail powered by mail.fr  
___
 Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

-- 

Michael Burman 

Senior Quality engineer - rhv network - redhat israel 


Re: [ovirt-users] Network configuration validation error

2018-02-08 Thread Michael Burman
Thanks,
I'm not so familiar with the hosted-engine --upgrade-appliance flow, can
someone from the list that is familiar with such flow assist?

On Thu, Feb 8, 2018 at 12:10 PM,  wrote:

> Hi,
>
> I installed my nodes with the latest packages available in repositories.
> Then I installed the self-hosted engine on one of them, created the cluster
> and added the second node.
>
> When I encountered these network config problems and saw your answer, I
> thougt it was time to update some packages to get corrections.
>
> So I just runned a "yum update" on the nodes and rebooted them.
>
> Then I put the  engine in global maintenance mode and tried "hosted-engine
> --upgrade-appliance" on the node hosting it.
>
> But it failed returning me this cluster version error.
>
> The engine's about windows says "Software Version:4.2.0.2-1.el7.centos"
>
> And for the hosts :
> OS Version:RHEL - 7 - 4.1708.el7.centos
> OS Description:CentOS Linux 7 (Core)
> Kernel Version:3.10.0 - 693.17.1.el7.x86_64
> KVM Version:2.9.0 - 16.el7_4.13.1
> LIBVIRT Version:libvirt-3.2.0-14.el7_4.7
> VDSM Version:vdsm-4.20.9.3-1.el7.centos
> SPICE Version:0.12.8 - 2.el7.1
> GlusterFS Version:[N/A]
> CEPH Version:librbd1-0.94.5-2.el7
>
> Regards
>
>
>
>
> Le 08-Feb-2018 09:59:32 +0100, mbur...@redhat.com a écrit:
>
> Not sure i understand from which version you trying to upgrade and what is
> the exact upgrade flow, if i got it correctly, it is seems that you
> upgraded the hosts to 4.2, but engine still 4.1?
> What exactly the upgrade steps, please explain the flow., what have you
> done after upgrading the hosts? to what version?
>
> Cheers)
>
> On Wed, Feb 7, 2018 at 3:00 PM,  wrote:
>
>> Hi,
>> Thanks a lot for your answer.
>>
>> I applied some updates at node level, but I forgot to upgrade the engine !
>>
>> When I try to do so I get a strange error : "Cluster PROD is at version
>> 4.2 which is not supported by this upgrade flow. Please fix it before
>> upgrading."
>>
>> Here are the installed packets on my nodes :
>> python-ovirt-engine-sdk4-4.2.2-2.el7.centos.x86_64
>> ovirt-imageio-common-1.2.0-1.el7.centos.noarch
>> ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch
>> ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch
>> ovirt-setup-lib-1.1.4-1.el7.centos.noarch
>> ovirt-release42-4.2.0-1.el7.centos.noarch
>> ovirt-imageio-daemon-1.2.0-1.el7.centos.noarch
>> ovirt-host-dependencies-4.2.0-1.el7.centos.x86_64
>> ovirt-host-4.2.0-1.el7.centos.x86_64
>> ovirt-host-deploy-1.7.0-1.el7.centos.noarch
>> ovirt-hosted-engine-ha-2.2.2-1.el7.centos.noarch
>> ovirt-provider-ovn-driver-1.2.2-1.el7.centos.noarch
>> ovirt-engine-appliance-4.2-20171219.1.el7.centos.noarch
>> ovirt-vmconsole-host-1.0.4-1.el7.noarch
>> cockpit-ovirt-dashboard-0.11.3-0.1.el7.centos.noarch
>> ovirt-vmconsole-1.0.4-1.el7.noarch
>>
>> What I am supposed to do ? I see no newer packages available.
>>
>> Regards
>>
>>
>>
>> Le 07-Feb-2018 13:23:43 +0100, mbur...@redhat.com a écrit:
>>
>> Hi
>>
>> This is a bug and it was already fixed in 4.2.1.1-0.1.el7 -
>> https://bugzilla.redhat.com/show_bug.cgi?id=1528906
>>
>> The no default route bug was fixed in - https://bugzilla.redhat.com/
>> show_bug.cgi?id=1477589
>>
>> Thanks,
>>
>> On Wed, Feb 7, 2018 at 1:15 PM,  wrote:
>>
>>>
>>> Hi,
>>> I am experiencing a new problem : when I try to modify something in the
>>> network setup on the second node (added to the cluster after installing the
>>> engine on the other one) using the Engine GUI, I get the following error
>>> when validating :
>>>
>>> must match "^\b((25[0-5]|2[0-4]\d|[01]\d\
>>> d|\d?\d)\_){3}(25[0-5]|2[0-4]\d|[01]\d\d|\d?\d)"
>>> Attribut : ipConfiguration.iPv4Addresses[0].gateway
>>>
>>> Moreover, on the general status of ther server, I have a "Host has no
>>> default route" alert.
>>>
>>> The ovirtmgmt network has a defined gateway of course, and the storage
>>> network has none because it is not required. Both server have the same
>>> setup, with different addresses of course :-)
>>>
>>> I have not been able to find anything useful in the logs.
>>>
>>> Is this a bug or am I doing something wrong ?
>>>
>>> Regards
>>>
>>> --
>>> FreeMail powered by mail.fr
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>>
>> --
>>
>> Michael Burman
>>
>> Senior Quality engineer - rhv network - redhat israel
>>
>> Red Hat
>>
>> 
>>
>> mbur...@redhat.comM: 0545355725 IM: mburman
>>
>>
>>
>> --
>> FreeMail powered by mail.fr
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
>
> Michael Burman
>
> Senior Quality engineer - rhv network - redhat israel
>
> Red Hat
>
> 
>
> mbur...@redhat.comM: 

Re: [ovirt-users] Network configuration validation error

2018-02-08 Thread spfma . tech
Hi,   I installed my nodes with the latest packages available in repositories. 
Then I installed the self-hosted engine on one of them, created the cluster and 
added the second node.   When I encountered these network config problems and 
saw your answer, I thougt it was time to update some packages to get 
corrections.   So I just runned a "yum update" on the nodes and rebooted them.  
 Then I put the engine in global maintenance mode and tried "hosted-engine 
--upgrade-appliance" on the node hosting it.   But it failed returning me this 
cluster version error.   The engine's about windows says "Software 
Version:4.2.0.2-1.el7.centos"   And for the hosts :OS Version:RHEL - 7 
- 4.1708.el7.centos OS Description:CentOS Linux 7 (Core) Kernel 
Version:3.10.0 - 693.17.1.el7.x86_64 KVM Version:2.9.0 - 16.el7_4.13.1  
   LIBVIRT Version:libvirt-3.2.0-14.el7_4.7 VDSM 
Version:vdsm-4.20.9.3-1.el7.centos SPICE Version:0.12.8 - 2.el7.1   
  GlusterFS Version:[N/A] CEPH Version:librbd1-0.94.5-2.el7  
Regards   

 Le 08-Feb-2018 09:59:32 +0100, mbur...@redhat.com a crit: 
   Not sure i understand from which version you trying to upgrade and what is 
the exact upgrade flow, if i got it correctly, it is seems that you upgraded 
the hosts to 4.2, but engine still 4.1?  What exactly the upgrade steps, please 
explain the flow., what have you done after upgrading the hosts? to what 
version?

 Cheers) 
 On Wed, Feb 7, 2018 at 3:00 PM,  wrote:

 Hi, Thanks a lot for your answer.I applied some updates at node level, but 
I forgot to upgrade the engine !   When I try to do so I get a strange error : 
"Cluster PROD is at version 4.2 which is not supported by this upgrade flow. 
Please fix it before upgrading."   Here are the installed packets on my nodes : 
python-ovirt-engine-sdk4-4.2.2-2.el7.centos.x86_64
ovirt-imageio-common-1.2.0-1.el7.centos.noarch
ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch
ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch
ovirt-setup-lib-1.1.4-1.el7.centos.noarch
ovirt-release42-4.2.0-1.el7.centos.noarch
ovirt-imageio-daemon-1.2.0-1.el7.centos.noarch
ovirt-host-dependencies-4.2.0-1.el7.centos.x86_64
ovirt-host-4.2.0-1.el7.centos.x86_64
ovirt-host-deploy-1.7.0-1.el7.centos.noarch
ovirt-hosted-engine-ha-2.2.2-1.el7.centos.noarch
ovirt-provider-ovn-driver-1.2.2-1.el7.centos.noarch
ovirt-engine-appliance-4.2-20171219.1.el7.centos.noarch
ovirt-vmconsole-host-1.0.4-1.el7.noarch
cockpit-ovirt-dashboard-0.11.3-0.1.el7.centos.noarch
ovirt-vmconsole-1.0.4-1.el7.noarch   What I am supposed to do ? I see no newer 
packages available.   Regards   

 Le 07-Feb-2018 13:23:43 +0100, mbur...@redhat.com a crit: 
Hi

 This is a bug and it was already fixed in 4.2.1.1-0.1.el7 - 
https://bugzilla.redhat.com/show_bug.cgi?id=1528906

 The no default route bug was fixed in - 
https://bugzilla.redhat.com/show_bug.cgi?id=1477589

 Thanks, 
 On Wed, Feb 7, 2018 at 1:15 PM,  wrote:

   Hi, I am experiencing a new problem : when I try to modify something in the 
network setup on the second node (added to the cluster after installing the 
engine on the other one) using the Engine GUI, I get the following error when 
validating :must match 
"^\b((25[0-5]|2[0-4]\d|[01]\d\d|\d?\d)\_){3}(25[0-5]|2[0-4]\d|[01]\d\d|\d?\d)"
 Attribut : ipConfiguration.iPv4Addresses[0].gateway   Moreover, on the general 
status of ther server, I have a "Host has no default route" alert.   The 
ovirtmgmt network has a defined gateway of course, and the storage network has 
none because it is not required. Both server have the same setup, with 
different addresses of course :-)   I have not been able to find anything 
useful in the logs.   Is this a bug or am I doing something wrong ?   Regards 

-
FreeMail powered by mail.fr 
___
 Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

-- 

Michael Burman 

Senior Quality engineer - rhv network - redhat israel 

Red Hat 

 mbur...@redhat.com  M: 0545355725 IM: mburman 

-
FreeMail powered by mail.fr  
___
 Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

-- 

Michael Burman 

Senior Quality engineer - rhv network - redhat israel 

Red Hat 

 mbur...@redhat.com  M: 0545355725 IM: mburman 

-
FreeMail powered by mail.fr
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Engine AAA LDAP startTLS Protocol Issue

2018-02-08 Thread Alan Griffiths
Hi,

Trying to configure Engine to authenticate against OpenLDAP and I seem
to be hitting a protocol bug.

Attempts to test the login during the setup fail with

2018-02-07 12:27:37,872Z WARNING Exception: The connection reader was
unable to successfully complete TLS negotiation:
SSLException(message='Received fatal alert: protocol_version',
trace='getSSLException(Alerts.java:208) /
getSSLException(Alerts.java:154) / recvAlert(SSLSocketImpl.java:2033)
/ readRecord(SSLSocketImpl.java:1135) /
performInitialHandshake(SSLSocketImpl.java:1385) /
startHandshake(SSLSocketImpl.java:1413) /
startHandshake(SSLSocketImpl.java:1397) /
run(LDAPConnectionReader.java:301)', revision=0)

Running a packet trace I see that it's trying to negotiate with TLS
1.0, but my LDAP server only support TLS 1.2.

This looks like a regression as it works fine in 4.0.

I see the issue in both 4.1 and 4.2

4.1.9.1
4.2.0.2

Should I submit a bug?

Thanks,

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


Re: [ovirt-users] Spice Newb

2018-02-08 Thread Gianluca Cecchi
On Wed, Feb 7, 2018 at 4:16 AM, Marshall Mitchell <
marsh...@marshallholdingco.com> wrote:

> I’m attempting to get my first install of oVirt going in full swing.  I
> have all the hosts installed and an engine running. All is smooth. I’m not
> trying to connect to the Spice console with my Remote Viewer and I have no
> clue how to figure out what port I should be connecting too. I’ve been all
> over the web via google looking for a process to install / configure /
> verify spice is operational, but I’ve not been lucky. How do I go about
> connecting / finding the port numbers for my VM’s? I did open the firewall
> range required. I appreciate the help.
>
>
>
> -Marshall
>
>
I don't know if I correctly understand your question.
It is the web admin gui or the portal gui that takes care of using the
correct host ip (that is where the VM is running at that moment) and the
correct port on it to connect to the vnc/spice console.

At host side the qemu-kvm process for a particular VM will have this snip
in its command line (in my case it is a VM with console configured as
Spice+VNC):

. . . -vnc 192.168.50.21:0,password -k en-us -spice
tls-port=5901,addr=192.168.50.21,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
. . .

Take in consideration that if you live migrate this VM, it will seamlessly
change the host ip in the new qemu-kvm process on destination host and also
the port, if the previous one is already taken.
In recent releases of oVirt your spice client window will remain up and the
same both during and after the live migration of the vm, even if the
material host to which it connects changes.
HIH,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Clear name_server table entries

2018-02-08 Thread Carlos Rodrigues
Hi,

Many thanks.

Cheers


On Thu, 2018-02-08 at 10:54 +0200, Michael Burman wrote:
> Hi
> 
> Yes you may delete the entries, make sure you are not deleting
> name_server of hosts that already running in your engine(if you have
> such).
> Deleting the multiple entries in the DB + removing the duplicated
> name servers in /etc/resolv.conf should work around this bug, which
> was decided to close as WONTFIX. Just re-add the the server to
> engine. 
> 
> Cheers)
> 
> On Wed, Feb 7, 2018 at 7:24 PM, Carlos Rodrigues 
> wrote:
> > Hi,
> > 
> > I'm getting the following problem:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1530944#c3
> > 
> > and after fix DNS entries no /etc/resolv.conf on host, i have to
> > many
> > entries on name_server table:
> > 
> > engine=# select count(*) from name_server;
> >  count
> > ---
> >  31401
> > (1 row)
> > 
> > I would like to know if may i delete this entries?
> > 
> > Best regards,
> > 
> > --
> > Carlos Rodrigues
> > 
> > Engenheiro de Software Sénior
> > 
> > Eurotux Informática, S.A. | www.eurotux.com
> > (t) +351 253 680 300 (m) +351 911 926 110
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> 
-- 
Carlos Rodrigues

Engenheiro de Software Sénior

Eurotux Informática, S.A. | www.eurotux.com
(t) +351 253 680 300 (m) +351 911 926 110
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Spice Newb

2018-02-08 Thread Marshall Mitchell
I'm attempting to get my first install of oVirt going in full swing.  I have 
all the hosts installed and an engine running. All is smooth. I'm not trying to 
connect to the Spice console with my Remote Viewer and I have no clue how to 
figure out what port I should be connecting too. I've been all over the web via 
google looking for a process to install / configure / verify spice is 
operational, but I've not been lucky. How do I go about connecting / finding 
the port numbers for my VM's? I did open the firewall range required. I 
appreciate the help.

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


[ovirt-users] ovn problem - Failed to communicate with the external provider, see log for additional details.

2018-02-08 Thread George Sitov
Hello!

I have a problem  wiith configure  external provider.

Edit config file - ovirt-provider-ovn.conf, set ssl parameters.
systemctl start ovirt-provider-ovn start without problem.
In external  proveder in web gui i set:
Provider URL:  https://ovirt.mydomain.com:9696
Username: admin@internal
Authentication URL: https://ovirt.mydomain.com:35357/v2.0/
But after i press test  button i see error -  Failed to communicate with
the external provider, see log for additional details.

/var/log/ovirt-engine/engine.log:
2018-02-05 21:33:55,517+02 ERROR
[org.ovirt.engine.core.bll.provider.network.openstack.BaseNetworkProviderProxy]
(default task-29) [69fa312e-6e2e-4925-b081-385beba18a6a] Bad Gateway
(OpenStack response error code: 502)
2018-02-05 21:33:55,517+02 ERROR
[org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand]
(default task-29) [69fa312e-6e2e-4925-b081-385beba18a6a] Command
'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand'
failed: EngineException: (Failed with error PROVIDER_FAILURE and code 5050)

In /var/log/ovirt-provider-ovn.log:

2018-02-05 21:33:55,510   Starting new HTTPS connection (1):
ovirt.astrecdata.com
2018-02-05 21:33:55,516   [SSL: CERTIFICATE_VERIFY_FAILED] certificate
verify failed (_ssl.c:579)
Traceback (most recent call last):
  File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line 126,
in _handle_request
method, path_parts, content)
  File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", line
176, in handle_request
return self.call_response_handler(handler, content, parameters)
  File "/usr/share/ovirt-provider-ovn/handlers/keystone.py", line 33, in
call_response_handler
return response_handler(content, parameters)
  File "/usr/share/ovirt-provider-ovn/handlers/keystone_responses.py", line
60, in post_tokens
user_password=user_password)
  File "/usr/share/ovirt-provider-ovn/auth/plugin_facade.py", line 26, in
create_token
return auth.core.plugin.create_token(user_at_domain, user_password)
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/plugin.py", line
48, in create_token
timeout=self._timeout())
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 62,
in create_token
username, password, engine_url, ca_file, timeout)
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 53,
in wrapper
response = func(*args, **kwargs)
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 46,
in wrapper
raise BadGateway(e)
BadGateway: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
(_ssl.c:579)

Whan i do wrong ?
Please help.


With best regards  Georgii.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Power management - oVirt 4,2

2018-02-08 Thread Terry hey
Dear Martin,

Thank you for helping me. To answer your question,
1. Does the Test in Edit fence agent dialog work​?
Ans: it shows that "Test failed: Internal JSON-RPC error"

Regardless the fail result, i press "OK" to enable power management. There
are four event log appear in "Events"
The follwing are the log in
"Event""
Host host01 configuration was updated by admin@internal-authz.
Kdump integration is enabled for host hostv01, but kdump is not configured
properly on host.
Health check on Host host01 indicates that future attempts to Stop this
host using Power-Management are expected to fail.
Health check on Host host01 indicates that future attempts to Start this
host using Power-Management are expected to fail.

2. If not could you please try to install fence-agents-all package on
different host and execute?
Ans: It just shows "Connection timed out".

So, does it means that it is not support iLo5 now or i configure wrongly?

Regards,
Terry

2018-02-02 15:46 GMT+08:00 Martin Perina :

>
>
> On Fri, Feb 2, 2018 at 5:40 AM, Terry hey  wrote:
>
>> Dear Martin,
>>
>> Um..Since i am going to use HPE ProLiant DL360 Gen10 Server to setup
>> oVirt Node(Hypervisor). HP G10 is using ilo5 rather than ilo4. Therefore, i
>> would like to ask whether oVirt power management support iLO5 or not.
>>
>
> ​We don't have any hardware with iLO5 available, but there is a good
> chance that it will be compatible with iLO4. Have you tried to setup your
> server with iLO4? Does the Test in Edit fence agent dialog work​? If not
> could you please try to install fence-agents-all package on different host
> and execute following:
>
> fence_ilo4 -a  -l  -p  -v -o status
>
> and share the output?
>
> Thanks
>
> Martin
>
>
>> If not, do you have any idea to setup power management with HP G10?
>>
>> Regards,
>> Terry
>>
>> 2018-02-01 16:21 GMT+08:00 Martin Perina :
>>
>>>
>>>
>>> On Wed, Jan 31, 2018 at 11:19 PM, Luca 'remix_tj' Lorenzetto <
>>> lorenzetto.l...@gmail.com> wrote:
>>>
 Hi,

 From ilo3 and up, ilo fencing agents are an alias for fence_ipmi. Try
 using the standard ipmi.

>>>
>>> ​It's not just an alias, ilo3/ilo4 also have different defaults than
>>> ipmilan. For example if you use ilo4, then by default following is used:
>>>
>>> ​
>>>
>>> ​lanplus=1
>>>  power_wait=4
>>>
>>> ​So I recommend to start with ilo4 and add any necessary custom options
>>> into Options field. If you need some custom
>>> options, could you please share them with us? It would be very helpful
>>> for us, if needed we could introduce ilo5 with
>>> different defaults then ilo4
>>>
>>> Thanks
>>>
>>> Martin
>>>
>>>
 Luca



 Il 31 gen 2018 11:14 PM, "Terry hey"  ha
 scritto:

> Dear all,
> Did oVirt 4.2 Power management support iLO5 as i could not see iLO5
> option in Power Management.
>
> Regards
> Terry
>
> ___
> 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


>>>
>>>
>>> --
>>> Martin Perina
>>> Associate Manager, Software Engineering
>>> Red Hat Czech s.r.o.
>>>
>>
>>
>
>
> --
> Martin Perina
> Associate Manager, Software Engineering
> Red Hat Czech s.r.o.
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Network configuration validation error

2018-02-08 Thread Michael Burman
Not sure i understand from which version you trying to upgrade and what is
the exact upgrade flow, if i got it correctly, it is seems that you
upgraded the hosts to 4.2, but engine still 4.1?
What exactly the upgrade steps, please explain the flow., what have you
done after upgrading the hosts? to what version?

Cheers)

On Wed, Feb 7, 2018 at 3:00 PM,  wrote:

> Hi,
> Thanks a lot for your answer.
>
> I applied some updates at node level, but I forgot to upgrade the engine !
>
> When I try to do so I get a strange error : "Cluster PROD is at version
> 4.2 which is not supported by this upgrade flow. Please fix it before
> upgrading."
>
> Here are the installed packets on my nodes :
> python-ovirt-engine-sdk4-4.2.2-2.el7.centos.x86_64
> ovirt-imageio-common-1.2.0-1.el7.centos.noarch
> ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch
> ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch
> ovirt-setup-lib-1.1.4-1.el7.centos.noarch
> ovirt-release42-4.2.0-1.el7.centos.noarch
> ovirt-imageio-daemon-1.2.0-1.el7.centos.noarch
> ovirt-host-dependencies-4.2.0-1.el7.centos.x86_64
> ovirt-host-4.2.0-1.el7.centos.x86_64
> ovirt-host-deploy-1.7.0-1.el7.centos.noarch
> ovirt-hosted-engine-ha-2.2.2-1.el7.centos.noarch
> ovirt-provider-ovn-driver-1.2.2-1.el7.centos.noarch
> ovirt-engine-appliance-4.2-20171219.1.el7.centos.noarch
> ovirt-vmconsole-host-1.0.4-1.el7.noarch
> cockpit-ovirt-dashboard-0.11.3-0.1.el7.centos.noarch
> ovirt-vmconsole-1.0.4-1.el7.noarch
>
> What I am supposed to do ? I see no newer packages available.
>
> Regards
>
>
>
> Le 07-Feb-2018 13:23:43 +0100, mbur...@redhat.com a écrit:
>
> Hi
>
> This is a bug and it was already fixed in 4.2.1.1-0.1.el7 -
> https://bugzilla.redhat.com/show_bug.cgi?id=1528906
>
> The no default route bug was fixed in - https://bugzilla.redhat.com/
> show_bug.cgi?id=1477589
>
> Thanks,
>
> On Wed, Feb 7, 2018 at 1:15 PM,  wrote:
>
>>
>> Hi,
>> I am experiencing a new problem : when I try to modify something in the
>> network setup on the second node (added to the cluster after installing the
>> engine on the other one) using the Engine GUI, I get the following error
>> when validating :
>>
>> must match "^\b((25[0-5]|2[0-4]\d|[01]\d\
>> d|\d?\d)\_){3}(25[0-5]|2[0-4]\d|[01]\d\d|\d?\d)"
>> Attribut : ipConfiguration.iPv4Addresses[0].gateway
>>
>> Moreover, on the general status of ther server, I have a "Host has no
>> default route" alert.
>>
>> The ovirtmgmt network has a defined gateway of course, and the storage
>> network has none because it is not required. Both server have the same
>> setup, with different addresses of course :-)
>>
>> I have not been able to find anything useful in the logs.
>>
>> Is this a bug or am I doing something wrong ?
>>
>> Regards
>>
>> --
>> FreeMail powered by mail.fr
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
>
> Michael Burman
>
> Senior Quality engineer - rhv network - redhat israel
>
> Red Hat
>
> 
>
> mbur...@redhat.comM: 0545355725 IM: mburman
>
>
>
> --
> FreeMail powered by mail.fr
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

Michael Burman

Senior Quality engineer - rhv network - redhat israel

Red Hat



mbur...@redhat.comM: 0545355725 IM: mburman

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


Re: [ovirt-users] Clear name_server table entries

2018-02-08 Thread Michael Burman
Hi

Yes you may delete the entries, make sure you are not deleting name_server
of hosts that already running in your engine(if you have such).
Deleting the multiple entries in the DB + removing the duplicated name
servers in /etc/resolv.conf should work around this bug, which was decided
to close as WONTFIX. Just re-add the the server to engine.

Cheers)

On Wed, Feb 7, 2018 at 7:24 PM, Carlos Rodrigues  wrote:

> Hi,
>
> I'm getting the following problem:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1530944#c3
>
> and after fix DNS entries no /etc/resolv.conf on host, i have to many
> entries on name_server table:
>
> engine=# select count(*) from name_server;
>  count
> ---
>  31401
> (1 row)
>
> I would like to know if may i delete this entries?
>
> Best regards,
>
> --
> Carlos Rodrigues
>
> Engenheiro de Software Sénior
>
> Eurotux Informática, S.A. | www.eurotux.com
> (t) +351 253 680 300 (m) +351 911 926 110
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 

Michael Burman

Senior Quality engineer - rhv network - redhat israel

Red Hat



mbur...@redhat.comM: 0545355725 IM: mburman

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


Re: [ovirt-users] oVirt CLI Question

2018-02-08 Thread Ondra Machacek

On 02/07/2018 11:28 PM, Andrei V wrote:

Hi,

How to force power off, and then launch (after timeout e.g. 20sec)
particular VM from bash or Python script?


Please check the following Python script:


https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/stop_vm.py

It stops the VM and wait until it's in DOWN state.

Then there is a script to start the VM:


https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/start_vm.py



Is 20sec is enough to get oVirt engine updated after forced power off  >
What happened with this wiki? Seems like it is deleted or moved.
http://wiki.ovirt.org/wiki/CLI#Usage


CLI was deprecated, and is not available anymore, since 4.0 I think.
You can use Ansible modules or Python SDK.



Is this project part of oVirt distro? It looks like in state of active
development with last updates 2 months ago.
https://github.com/fbacchella/ovirtcmd


No, it isn't part of oVirt distribution.



Thanks !
___
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: [ovirt-users] After realizing HA migration, the virtual machine can still get the virtual machine information by using the "vdsm-client host getVMList" instruction on the host before the migration

2018-02-08 Thread Petr Kotas
Hi Pym,

the feature is know in testing. I am not sure when it will be released, but
I hope for sooner date.

Petr

On Tue, Feb 6, 2018 at 12:36 PM, Pym  wrote:

> Thank you very much for your help, so is this patch released now? Where
> can I get this patch?
>
>
>
>
>
>
> At 2018-02-05 20:52:04, "Petr Kotas"  wrote:
>
> Hi,
>
> I have experimented on the issue and figured out the reason for the
> original issue.
>
> You are right, that the vm1 is not properly stopped. This is due to the
> known issue in the graceful shutdown introduced in the ovirt 4.2.
> The vm on the host in shutdown are killed, but are not marked as stopped.
> This results in the behavior you have observed.
>
> Luckily, the patch is already done and present in the latest ovirt.
> However, be ware that gracefully shutting down the host, will result in
> graceful shutdown of
> the VMs. This result in engine not migrating them, since they have been
> terminated gracefully.
>
> Hope this helps.
>
> Best,
> Petr
>
>
> On Fri, Feb 2, 2018 at 6:00 PM, Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Thu, Feb 1, 2018 at 1:06 PM, Pym  wrote:
>>
>>> The environment on my side may be different from the link. My VM1 can be
>>> used normally after it is started on host2, but there is still information
>>> left on host1 that is not cleaned up.
>>>
>>> Only the interface and background can still get the information of vm1
>>> on host1, but the vm2 has been successfully started on host2, with the HA
>>> function.
>>>
>>> I would like to ask a question, whether the UUID of the virtual machine
>>> is stored in the database or where is it maintained? Is it not successfully
>>> deleted after using the HA function?
>>>
>>>
>> I just encounter a similar behavior:
>> after a reboot of the host 'vdsm-client Host getVMFullList' is still
>> reporting an old VM that is not visible with 'virsh -r list --all'.
>>
>> I filed a bug to track it:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1541479
>>
>>
>>
>>>
>>>
>>>
>>>
>>>  2018-02-01 16:12:16,"Simone Tiraboschi"  :
>>>
>>>
>>>
>>> On Thu, Feb 1, 2018 at 2:21 AM, Pym  wrote:
>>>

 I checked the vm1, he is keep up state, and can be used, but on host1
 has after shutdown is a suspended vm1, this cannot be used, this is the
 problem now.

 In host1, you can get the information of vm1 using the "vdsm-client
 Host getVMList", but you can't get the vm1 information using the "virsh
 list".


>>> Maybe a side effect of https://bugzilla.redhat.com
>>> /show_bug.cgi?id=1505399
>>>
>>> Arik?
>>>
>>>
>>>



  2018-02-01 07:16:37,"Simone Tiraboschi"  :



 On Wed, Jan 31, 2018 at 12:46 PM, Pym  wrote:

> Hi:
>
> The current environment is as follows:
>
> Ovirt-engine version 4.2.0 is the source code compilation and
> installation. Add two hosts, host1 and host2, respectively. At host1, a
> virtual machine is created on vm1, and a vm2 is created on host2 and HA is
> configured.
>
> Operation steps:
>
> Use the shutdown -r command on host1. Vm1 successfully migrated to
> host2.
> When host1 is restarted, the following situation occurs:
>
> The state of the vm2 will be shown in two images, switching from up
> and pause.
>
> When I perform the "vdsm-client Host getVMList" in host1, I will get
> the information of vm1. When I execute the "vdsm-client Host getVMList" in
> host2, I will get the information of vm1 and vm2.
> When I do "virsh list" in host1, there is no virtual machine
> information. When I execute "virsh list" at host2, I will get information
> of vm1 and vm2.
>
> How to solve this problem?
>
> Is it the case that vm1 did not remove the information on host1 during
> the migration, or any other reason?
>

 Did you also check if your vms always remained up?
 In 4.2 we have libvirt-guests service on the hosts which tries to
 properly shutdown the running VMs on host shutdown.


>
> Thank you.
>
>
>
>
> ___
> 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 mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt DR: ansible with 4.1, only a subset of storage domain replicated

2018-02-08 Thread Luca 'remix_tj' Lorenzetto
On Tue, Feb 6, 2018 at 9:33 PM, Maor Lipchuk  wrote:
[cut]
>> What i need is that informations about vms is replicated to the remote
>> site with disk.
>> In an older test i had the issue that disks were replicated to remote
>> site, but vm configuration not!
>> I've found disks in the "Disk"  tab of storage domain, but nothing on VM
>> Import.
>
>
>
> Can you reproduce it and attach the logs of the setup before the disaster
> and after the recovery?
> That could happen in case of new created VMs and Templates which were not
> yet updated in the OVF_STORE disk, since the OVF_STORE update process was
> not running yet before the disaster.
> Since the time of a disaster can't be anticipated, gaps like this might
> happen.
>

I haven't tried the recovery yet using ansible. It was an experiment
of possible procedure to be performed manually and was on 4.0.
I asked about this unexpected behavior and Yaniv returned me that was
due to OVF_STORE not updated and that in 4.1 there is an api call that
updates OVF_STORE on demand.

I'm creating a new setup today and i'll test again and check if i
still hit the issue. Anyway if the problem persist i think that
engine, for DR purposes, should upgrade the OVF_STORE as soon as
possible when a new vm is created or has disks added.

[cut]
>>
>> Ok, but if i keep master storage domain on a non replicate volume, do
>> i require this function?
>
>
> Basically it should also fail on VM/Template registration in oVirt 4.1 since
> there are also other functionalities like mapping of OVF attributes which
> was added on VM/Templates registeration.
>

What do you mean? That i could fail to import any VM/Template? In what case?


Another question:

we have 2 DCs in main site, do we require to have also 2 DCs in
recovery site o we can import all the storage domains in a single DC
on recovery site? There could be uuid collisions or similar?

Thank you so much for your replies,

Luca
-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Power management - oVirt 4,2

2018-02-08 Thread Martin Perina
Hi Terry,

from the error message below I'd say that you are either not using correct
IP address of iLO5 interface or you haven't enabled remote access to your
iLO5 interface.
According to [1] iLO5 should fully IPMI compatible. So are you sure that
you enabled the remote access to your iLO5 address in iLO5 management?
Please consult [1] how to enable everything and use a user with at least
Operator privileges.

Regards

Martin

[1] https://support.hpe.com/hpsc/doc/public/display?docId=a00018324en_us


On Thu, Feb 8, 2018 at 7:57 AM, Terry hey  wrote:

> Dear Martin,
>
> Thank you for helping me. To answer your question,
> 1. Does the Test in Edit fence agent dialog work​?
> Ans: it shows that "Test failed: Internal JSON-RPC error"
>
> Regardless the fail result, i press "OK" to enable power management. There
> are four event log appear in "Events"
> The follwing are the log in
> "Event""
> Host host01 configuration was updated by admin@internal-authz.
> Kdump integration is enabled for host hostv01, but kdump is not configured
> properly on host.
> Health check on Host host01 indicates that future attempts to Stop this
> host using Power-Management are expected to fail.
> Health check on Host host01 indicates that future attempts to Start this
> host using Power-Management are expected to fail.
>
> 2. If not could you please try to install fence-agents-all package on
> different host and execute?
> Ans: It just shows "Connection timed out".
>
> So, does it means that it is not support iLo5 now or i configure wrongly?
>
> Regards,
> Terry
>
> 2018-02-02 15:46 GMT+08:00 Martin Perina :
>
>>
>>
>> On Fri, Feb 2, 2018 at 5:40 AM, Terry hey  wrote:
>>
>>> Dear Martin,
>>>
>>> Um..Since i am going to use HPE ProLiant DL360 Gen10 Server to setup
>>> oVirt Node(Hypervisor). HP G10 is using ilo5 rather than ilo4. Therefore, i
>>> would like to ask whether oVirt power management support iLO5 or not.
>>>
>>
>> ​We don't have any hardware with iLO5 available, but there is a good
>> chance that it will be compatible with iLO4. Have you tried to setup your
>> server with iLO4? Does the Test in Edit fence agent dialog work​? If not
>> could you please try to install fence-agents-all package on different host
>> and execute following:
>>
>> fence_ilo4 -a  -l  -p  -v -o status
>>
>> and share the output?
>>
>> Thanks
>>
>> Martin
>>
>>
>>> If not, do you have any idea to setup power management with HP G10?
>>>
>>> Regards,
>>> Terry
>>>
>>> 2018-02-01 16:21 GMT+08:00 Martin Perina :
>>>


 On Wed, Jan 31, 2018 at 11:19 PM, Luca 'remix_tj' Lorenzetto <
 lorenzetto.l...@gmail.com> wrote:

> Hi,
>
> From ilo3 and up, ilo fencing agents are an alias for fence_ipmi. Try
> using the standard ipmi.
>

 ​It's not just an alias, ilo3/ilo4 also have different defaults than
 ipmilan. For example if you use ilo4, then by default following is used:

 ​

 ​lanplus=1
  power_wait=4

 ​So I recommend to start with ilo4 and add any necessary custom options
 into Options field. If you need some custom
 options, could you please share them with us? It would be very helpful
 for us, if needed we could introduce ilo5 with
 different defaults then ilo4

 Thanks

 Martin


> Luca
>
>
>
> Il 31 gen 2018 11:14 PM, "Terry hey"  ha
> scritto:
>
>> Dear all,
>> Did oVirt 4.2 Power management support iLO5 as i could not see iLO5
>> option in Power Management.
>>
>> Regards
>> Terry
>>
>> ___
>> 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
>
>


 --
 Martin Perina
 Associate Manager, Software Engineering
 Red Hat Czech s.r.o.

>>>
>>>
>>
>>
>> --
>> Martin Perina
>> Associate Manager, Software Engineering
>> Red Hat Czech s.r.o.
>>
>
>


-- 
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users