[ovirt-users] Re: 4.2 User Portal

2018-09-17 Thread Staniforth, Paul
Sorry, you can't actually expand disks only add or delete them.


Regards,

   Paul S.


From: Staniforth, Paul
Sent: 17 September 2018 14:30
To: Стаценко Константин Юрьевич; users
Subject: Re: 4.2 User Portal


Neither can I, but can if I go to Legacy View ( how recent does it qualify as 
Legacy)?


Another question can we default to Legacy View instead of the new Detailed View?


Thanks,

 Paul S.


From: Стаценко Константин Юрьевич 
Sent: 17 September 2018 14:06
To: users
Subject: [ovirt-users] 4.2 User Portal

Hello!
Users cannot edit and expand VM's disks from the User Portal after 4.2 upgrade 
anymore.
VM UI screenshot attached.
Users can press Edit icon, but only "Editing" appears and nothing more.
Same thing happens under admin's accounts on User Portal.
>From Admin Portal everything is fine.
How can we fix this issue, so users can edit they VM from the User Portal as it 
was in 4.1 ?
Thanks.

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
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ANX6HAUU3B4VODCBQCH227MIKRB5JFN2/


[ovirt-users] Re: Proxmox - oVirt Migration

2018-09-17 Thread Leo David
Thank you Andrei,
This would be fine in case of a few vms, but not so practical for many of
them to import.
I will try by using virt-p2v.iso to boot on source vm, and get it converted
to an existing oVirt nfs export domain. From where to import them in the
oVirt cluster.
Will let you know about results..
If any other procedure available, please let me know.
Thanks a lot,

Leo


On Tue, Sep 18, 2018, 00:21 Andrei Verovski  wrote:

> Hi,
>
> Try this:
>
> 1) Storage -> Disks -> Upload -> Start
> select your existing qcow image
>
> 2) Create new VM, and then General -> Instance Images, clock "+" and
> "Attach", select imported disk image.
>
> I think it should work.
>
> PS Someone from oVirt dev team please confirm, I didn't tried import
> existing qcow2.
>
>
> On 9/17/18 3:30 PM, Leo David wrote:
> > Hello everyone,
> > I have this situation where I need to migrate about 20 vms from
> > Proxmox to oVirt.
> > In this case,  its about qcow2 images running on Proxmox.
> > I there a recomended way and procedure for doing this ?
> > Thank you very much !
> >
> > --
> > Best regards, Leo David
> >
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/YV5CMHDZSXJ5FQ3QRYNL2QKGXGKYHS7L/
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SBW46XILAAVZIPN7Q6SP7ARJCFYO5GPG/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/N64QIEPXC7OGS6XBED4WIR5Y3XVL3VYN/


[ovirt-users] Re: Unable to mount NFS lun

2018-09-17 Thread Budur Nagaraju
Tried , but no luck.

Thanks,
Nagaraju

On Tue, Sep 18, 2018 at 12:25 AM Benedetto Vassallo <
benedetto.vassa...@unipa.it> wrote:

> Hi,
> You can try to edit /etc/nfsmount.conf on the ovirt nodes and set:
> DefaultVers=3
> NfsVers=3
>
> Then try to mount the share from the webUI.
>
>
>
> Inviato da smartphone Samsung Galaxy.
>
>  Messaggio originale 
> Da: Budur Nagaraju 
> Data: 17/09/18 17:23 (GMT+01:00)
> A: users@ovirt.org, froll...@redhat.com
> Oggetto: [ovirt-users] Re: Unable to mount NFS lun
>
> Hi
>
> Am stuck ,can someone help on this?
>
> Thanks,
> Nagarau
>
> On Mon, Sep 17, 2018 at 7:10 PM Budur Nagaraju  wrote:
>
>> Hi
>>
>> We have manually mounted the lun in the node and not seeing any issues
>> ,while mounting from the UI its failing , by the way one thing to update is
>> that nfs lun is created from the Dell unity NFS version3.
>>
>> Any help can we get ?
>>
>> Thanks,
>> Nagaraju
>> '
>>
>>
>>
>> On Mon, Sep 17, 2018 at 6:23 PM Fred Rolland  wrote:
>>
>>> Hi,
>>>
>>> Check this page for troubleshooting:
>>>
>>>
>>> https://www.ovirt.org/documentation/how-to/troubleshooting/troubleshooting-nfs-storage-issues/
>>>
>>> Regards,
>>> Freddy
>>>
>>> On Mon, Sep 17, 2018 at 1:08 PM, Budur Nagaraju 
>>> wrote:
>>>
 Hi

 When I do a NFS mount in the oVirt getting error , below are the logs.



 https://pastebin.com/T1ASaB4V

 Thanks,
 Nagaraju


 ___
 Users mailing list -- users@ovirt.org
 To unsubscribe send an email to users-le...@ovirt.org
 Privacy Statement: https://www.ovirt.org/site/privacy-policy/
 oVirt Code of Conduct:
 https://www.ovirt.org/community/about/community-guidelines/
 List Archives:
 https://lists.ovirt.org/archives/list/users@ovirt.org/message/EBK5VIEPTEDF3SRH3IQCFXZBTXHP5UTL/


>>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NKKQEUTGUPR5TS6XUHG5OIUTVKVYU6MR/


[ovirt-users] Re: The Engine API did not accept the administrator password you provided ovirt 4.2 site:lists.ovirt.org

2018-09-17 Thread Ariez Ahito
any update on this?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OPULYFSJUBTE7QQZAPA5OKXCBFGEOWYI/


[ovirt-users] Re: 4.2 User Portal

2018-09-17 Thread Greg Sheremeta
Sorry about this -- it was an oversight. If you pull the latest version
(ovirt-web-ui 1.4.3), this should be fixed.

Greg

On Mon, Sep 17, 2018 at 6:07 PM Staniforth, Paul <
p.stanifo...@leedsbeckett.ac.uk> wrote:

> Neither can I, but can if I go to Legacy View ( how recent does it qualify
> as Legacy)?
>
>
> Another question can we default to Legacy View instead of the new Detailed
> View?
>
>
> Thanks,
>
>  Paul S.
> --
> *From:* Стаценко Константин Юрьевич 
> *Sent:* 17 September 2018 14:06
> *To:* users
> *Subject:* [ovirt-users] 4.2 User Portal
>
>
> Hello!
>
> Users cannot edit and expand VM’s disks from the User Portal after 4.2
> upgrade anymore.
>
> VM UI screenshot attached.
>
> Users can press Edit icon, but only “Editing” appears and nothing more.
>
> Same thing happens under admin’s accounts on User Portal.
>
> From Admin Portal everything is fine.
>
> How can we fix this issue, so users can edit they VM from the User Portal
> as it was in 4.1 ?
>
> Thanks.
>
>
> 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
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IEGNOOVFT5HROC5HD2JSAGUONRPUEE4H/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7D7IQI6UAD3BMUZK5KWFKYUBPW5D2AT7/


[ovirt-users] Re: 4.2 User Portal

2018-09-17 Thread Staniforth, Paul
Neither can I, but can if I go to Legacy View ( how recent does it qualify as 
Legacy)?


Another question can we default to Legacy View instead of the new Detailed View?


Thanks,

 Paul S.


From: Стаценко Константин Юрьевич 
Sent: 17 September 2018 14:06
To: users
Subject: [ovirt-users] 4.2 User Portal

Hello!
Users cannot edit and expand VM's disks from the User Portal after 4.2 upgrade 
anymore.
VM UI screenshot attached.
Users can press Edit icon, but only "Editing" appears and nothing more.
Same thing happens under admin's accounts on User Portal.
>From Admin Portal everything is fine.
How can we fix this issue, so users can edit they VM from the User Portal as it 
was in 4.1 ?
Thanks.

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
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IEGNOOVFT5HROC5HD2JSAGUONRPUEE4H/


[ovirt-users] Re: Proxmox - oVirt Migration

2018-09-17 Thread Andrei Verovski

Hi,

Try this:

1) Storage -> Disks -> Upload -> Start
select your existing qcow image

2) Create new VM, and then General -> Instance Images, clock "+" and  
"Attach", select imported disk image.


I think it should work.

PS Someone from oVirt dev team please confirm, I didn't tried import 
existing qcow2.



On 9/17/18 3:30 PM, Leo David wrote:

Hello everyone,
I have this situation where I need to migrate about 20 vms from 
Proxmox to oVirt.

In this case,  its about qcow2 images running on Proxmox.
I there a recomended way and procedure for doing this ?
Thank you very much !

--
Best regards, Leo David

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YV5CMHDZSXJ5FQ3QRYNL2QKGXGKYHS7L/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SBW46XILAAVZIPN7Q6SP7ARJCFYO5GPG/


[ovirt-users] Re: Unable to upgrade ovirt-node from 4.2.3

2018-09-17 Thread Yuval Turgeman
Glad to hear, thanks for the update !

On Mon, Sep 17, 2018, 18:13 Benedetto Vassallo 
wrote:

> Thank you guys, it worked!
>
>
> Def. Quota Yuval Turgeman :
>
> Try to first remove the LV for /var/crash or mount it, then remove any
> base that is not used (imgbase base --remove ), then yum update
> again.
>
> Documented here (for other LVs):
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/recovering_from_failed_nist-800_upgrade
>
> On Mon, Sep 17, 2018 at 5:13 PM, Sandro Bonazzola 
> wrote:
>
>> Adding Yuval
>>
>>
>> Il giorno lun 17 set 2018 alle ore 15:16 
>> ha scritto:
>>
>>> Hi,
>>> I have installed some 4.2.2 ovirt nodes (fresh installation) and
>>> upgraded them to 4.2.3 from the ovirt-engine UI.
>>> All was right, but if I want to upgrade from 4.2.3 to any new version I
>>> got a failure in post script.
>>> In the /tmp/imgbased.log I have the following error:
>>>
>>> 2018-09-17 14:28:09,073 [DEBUG] (MainThread) Calling: (['rmdir',
>>> u'/tmp/mnt.POEYF'],) {'close_fds': True, 'stderr': -2}
>>> 2018-09-17 14:28:09,080 [DEBUG] (MainThread) Returned:
>>> 2018-09-17 14:28:09,081 [ERROR] (MainThread) Failed to migrate etc
>>> Traceback (most recent call last):
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
>>> line 118, in on_new_layer
>>> check_nist_layout(imgbase, new_lv)
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
>>> line 209, in check_nist_layout
>>> v.create(t, paths[t]["size"], paths[t]["attach"])
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/volume.py",
>>> line 48, in create
>>> "Path is already a volume: %s" % where
>>> AssertionError: Path is already a volume: /var/crash
>>> 2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling binary: (['umount',
>>> '-l', u'/tmp/mnt.gt3IE'],) {}
>>> 2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling: (['umount', '-l',
>>> u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
>>> 2018-09-17 14:28:09,181 [DEBUG] (MainThread) Returned:
>>> 2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling binary: (['rmdir',
>>> u'/tmp/mnt.gt3IE'],) {}
>>> 2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling: (['rmdir',
>>> u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
>>> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Returned:
>>> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling binary: (['umount',
>>> '-l', u'/tmp/mnt.2weYe'],) {}
>>> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling: (['umount', '-l',
>>> u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
>>> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Returned:
>>> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling binary: (['rmdir',
>>> u'/tmp/mnt.2weYe'],) {}
>>> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling: (['rmdir',
>>> u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
>>> 2018-09-17 14:28:09,397 [DEBUG] (MainThread) Returned:
>>> Traceback (most recent call last):
>>>   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
>>> "__main__", fname, loader, pkg_name)
>>>   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>>> exec code in run_globals
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__main__.py",
>>> line 53, in 
>>> CliApplication()
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__init__.py",
>>> line 82, in CliApplication
>>> app.hooks.emit("post-arg-parse", args)
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py",
>>> line 120, in emit
>>> cb(self.context, *args)
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
>>> line 56, in post_argparse
>>> base_lv, _ = LiveimgExtractor(app.imgbase).extract(args.FILENAME)
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
>>> line 118, in extract
>>> "%s" % size, nvr)
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
>>> line 99, in add_base_with_tree
>>> new_layer_lv = self.imgbase.add_layer(new_base)
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/imgbase.py",
>>> line 192, in add_layer
>>> self.hooks.emit("new-layer-added", prev_lv, new_lv)
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py",
>>> line 120, in emit
>>> cb(self.context, *args)
>>>   File
>>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
>>> line 132, in on_new_layer
>>> raise ConfigMigrationError()
>>> imgbased.plugins.osupdater.ConfigMigrationError
>>>
>>> I have this on all nodes.
>>> Today I tried to make a fresh 2.2 install on a test VM, execute "yum
>>> update", updated it to 2.3 and then I got tha same error again.
>>> I did a default installation from

[ovirt-users] Re: Unable to upgrade ovirt-node from 4.2.3

2018-09-17 Thread Staniforth, Paul
I've been told it's because /var/crash isn't mounted, but I've been using

lvremove /dev/onn/var_crash

then yum reinstall

then if it's fails remove the next LV until it works.

I suggest running nodectl info and nodectl check before rebooting.

Regards,
 Paul S.


From: benedetto.vassa...@unipa.it 
Sent: 17 September 2018 14:13
To: users@ovirt.org
Subject: [ovirt-users] Unable to upgrade ovirt-node from 4.2.3

Hi,
I have installed some 4.2.2 ovirt nodes (fresh installation) and upgraded them 
to 4.2.3 from the ovirt-engine UI.
All was right, but if I want to upgrade from 4.2.3 to any new version I got a 
failure in post script.
In the /tmp/imgbased.log I have the following error:

2018-09-17 14:28:09,073 [DEBUG] (MainThread) Calling: (['rmdir', 
u'/tmp/mnt.POEYF'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,080 [DEBUG] (MainThread) Returned:
2018-09-17 14:28:09,081 [ERROR] (MainThread) Failed to migrate etc
Traceback (most recent call last):
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 118, in on_new_layer
check_nist_layout(imgbase, new_lv)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 209, in check_nist_layout
v.create(t, paths[t]["size"], paths[t]["attach"])
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/volume.py", line 
48, in create
"Path is already a volume: %s" % where
AssertionError: Path is already a volume: /var/crash
2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling binary: (['umount', '-l', 
u'/tmp/mnt.gt3IE'],) {}
2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling: (['umount', '-l', 
u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,181 [DEBUG] (MainThread) Returned:
2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling binary: (['rmdir', 
u'/tmp/mnt.gt3IE'],) {}
2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling: (['rmdir', 
u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,190 [DEBUG] (MainThread) Returned:
2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling binary: (['umount', '-l', 
u'/tmp/mnt.2weYe'],) {}
2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling: (['umount', '-l', 
u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,389 [DEBUG] (MainThread) Returned:
2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling binary: (['rmdir', 
u'/tmp/mnt.2weYe'],) {}
2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling: (['rmdir', 
u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,397 [DEBUG] (MainThread) Returned:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__main__.py", 
line 53, in 
CliApplication()
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__init__.py", 
line 82, in CliApplication
app.hooks.emit("post-arg-parse", args)
  File "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py", 
line 120, in emit
cb(self.context, *args)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
 line 56, in post_argparse
base_lv, _ = LiveimgExtractor(app.imgbase).extract(args.FILENAME)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
 line 118, in extract
"%s" % size, nvr)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
 line 99, in add_base_with_tree
new_layer_lv = self.imgbase.add_layer(new_base)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 
192, in add_layer
self.hooks.emit("new-layer-added", prev_lv, new_lv)
  File "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py", 
line 120, in emit
cb(self.context, *args)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 132, in on_new_layer
raise ConfigMigrationError()
imgbased.plugins.osupdater.ConfigMigrationError

I have this on all nodes.
Today I tried to make a fresh 2.2 install on a test VM, execute "yum update", 
updated it to 2.3 and then I got tha same error again.
I did a default installation from 
ovirt-node-ng-installer-ovirt-4.2-2018040514.iso, automatic partitioning and 
nothing customized.
Is there anyone having the same issue or knowing how to solve it?
Thanks in advantage.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 

[ovirt-users] disk resize question

2018-09-17 Thread Dev Ops
Hey all, quick question regarding new VM instances in oVirt. Is there any way 
to grow the thin disk associated with a template on instantiation? This would 
allow facilities like cloud-init resizefs to actually be useful. Been searching 
around a bit and it seems like this is not a thing in oVirt. 

Thanks!!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/N6VX32H225U7DIQPUGGOH3ENQDFDQJ2K/


[ovirt-users] R: Re: Unable to mount NFS lun

2018-09-17 Thread Benedetto Vassallo
Hi,You can try to edit /etc/nfsmount.conf on the ovirt nodes and 
set:DefaultVers=3NfsVers=3
Then try to mount the share from the webUI.


Inviato da smartphone Samsung Galaxy.
 Messaggio originale Da: Budur Nagaraju  
Data: 17/09/18  17:23  (GMT+01:00) A: users@ovirt.org, froll...@redhat.com 
Oggetto: [ovirt-users] Re: Unable to mount NFS lun 
Hi 

Am stuck ,can someone help on this?
Thanks,Nagarau

On Mon, Sep 17, 2018 at 7:10 PM Budur Nagaraju  wrote:
Hi 

We have manually mounted the lun in the node and not seeing any issues ,while 
mounting from the UI its failing , by the way one thing to update is that nfs 
lun is created from the Dell unity NFS version3.
Any help can we get ?
Thanks,Nagaraju'



On Mon, Sep 17, 2018 at 6:23 PM Fred Rolland  wrote:
Hi,
Check this page for troubleshooting:
https://www.ovirt.org/documentation/how-to/troubleshooting/troubleshooting-nfs-storage-issues/
Regards,Freddy

On Mon, Sep 17, 2018 at 1:08 PM, Budur Nagaraju  wrote:
Hi 

When I do a NFS mount in the oVirt getting error , below are the logs.



https://pastebin.com/T1ASaB4V
Thanks,Nagaraju


___

Users mailing list -- users@ovirt.org

To unsubscribe send an email to users-le...@ovirt.org

Privacy Statement: https://www.ovirt.org/site/privacy-policy/

oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/

List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EBK5VIEPTEDF3SRH3IQCFXZBTXHP5UTL/








smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/L6ZGAMKSKESS4RRQSQAEGSJL74B56JMQ/


[ovirt-users] Re: clone snapshot of running vm

2018-09-17 Thread Staniforth, Paul
Hello,

  I just tried it as a normal user using the SDK which works,

e.g.

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


Regards,

   Paul S.




From: fsoyer 
Sent: 15 September 2018 10:53
To: Staniforth, Paul; users@ovirt.org
Subject: Re: [ovirt-users] clone snapshot of running vm

Hi guys,
I just have this issue on a fresh 4.2.6 install. The snapshot of a vm  Seems to 
be the same logs in the ui.log (I paste it here to be sure), and unable to 
clone the snapshot. VM on or off doesn't change things. This really seems to be 
a UI issue because when it appends, we can no more create or clone a snapshot 
on any VM : the buttons just do nothing (and no log in the ui.log when we hit 
them). We must reload the ui (F5 or Ctrl-R) to recover the functionnalities.
Please help us ? Thanks.

2018-09-15 11:37:50,589+02 ERROR 
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default 
task-17) [] Permutation name: 3F33631A4CFC71A7A5878CCA004CB97D
2018-09-15 11:37:50,589+02 ERROR 
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default 
task-17) [] Uncaught exception: com.google.gwt.event.shared.UmbrellaException: 
Exception caught: (TypeError) : Cannot read property 'K' of null
at java.lang.Throwable.Throwable(Throwable.java:70) [rt.jar:1.8.0_181]
at java.lang.RuntimeException.RuntimeException(RuntimeException.java:32) 
[rt.jar:1.8.0_181]
at 
com.google.web.bindery.event.shared.UmbrellaException.UmbrellaException(UmbrellaException.java:64)
 [gwt-servlet.jar:]
at Unknown.new C0(webadmin-0.js)
at 
com.google.gwt.event.shared.HandlerManager.$fireEvent(HandlerManager.java:117) 
[gwt-servlet.jar:]
at com.google.gwt.user.client.ui.Widget.$fireEvent(Widget.java:127) 
[gwt-servlet.jar:]
at com.google.gwt.user.client.ui.Widget.fireEvent(Widget.java:127) 
[gwt-servlet.jar:]
at 
com.google.gwt.event.dom.client.DomEvent.fireNativeEvent(DomEvent.java:110) 
[gwt-servlet.jar:]
at com.google.gwt.user.client.ui.Widget.$onBrowserEvent(Widget.java:163) 
[gwt-servlet.jar:]
at com.google.gwt.user.client.ui.Widget.onBrowserEvent(Widget.java:163) 
[gwt-servlet.jar:]
at com.google.gwt.user.client.DOM.dispatchEvent(DOM.java:1415) 
[gwt-servlet.jar:]
at 
com.google.gwt.user.client.impl.DOMImplStandard.dispatchEvent(DOMImplStandard.java:312)
 [gwt-servlet.jar:]
at com.google.gwt.core.client.impl.Impl.apply(Impl.java:236) 
[gwt-servlet.jar:]
at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:275) 
[gwt-servlet.jar:]
at Unknown.eval(webadmin-0.js)
Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot 
read property 'K' of null
at 
org.ovirt.engine.ui.uicommonweb.models.vms.ExistingVmModelBehavior.updateHaAvailability(ExistingVmModelBehavior.java:481)
at 
org.ovirt.engine.ui.uicommonweb.models.vms.UnitVmModel.eventRaised(UnitVmModel.java:1933)
at org.ovirt.engine.ui.uicompat.Event.$raise(Event.java:99)
at 
org.ovirt.engine.ui.uicommonweb.models.ListModel.$setSelectedItem(ListModel.java:82)
at 
org.ovirt.engine.ui.uicommonweb.models.ListModel.setSelectedItem(ListModel.java:78)
at 
org.ovirt.engine.ui.common.editor.UiCommonEditorVisitor.$updateListEditor(UiCommonEditorVisitor.java:193)
at 
org.ovirt.engine.ui.common.editor.UiCommonEditorVisitor.visit(UiCommonEditorVisitor.java:47)
at 
com.google.gwt.editor.client.impl.AbstractEditorContext.$traverse(AbstractEditorContext.java:127)
 [gwt-servlet.jar:]
at 
org.ovirt.engine.ui.common.widget.uicommon.popup.AbstractVmPopupWidget_UiCommonModelEditorDelegate.accept(AbstractVmPopupWidget_UiCommonModelEditorDelegate.java:502)
at 
com.google.gwt.editor.client.impl.AbstractEditorContext.$traverse(AbstractEditorContext.java:127)
 [gwt-servlet.jar:]
at 
org.ovirt.engine.ui.common.widget.uicommon.popup.AbstractVmPopupWidget_DriverImpl.accept(AbstractVmPopupWidget_DriverImpl.java:4)
at 
org.ovirt.engine.ui.common.editor.AbstractUiCommonModelEditorDriver.$edit(AbstractUiCommonModelEditorDriver.java:32)
at 
org.ovirt.engine.ui.common.widget.uicommon.popup.AbstractVmPopupWidget.$edit(AbstractVmPopupWidget.java:1518)
at 
org.ovirt.engine.ui.common.widget.uicommon.popup.AbstractVmPopupWidget.edit(AbstractVmPopupWidget.java:1518)
at 
org.ovirt.engine.ui.common.widget.uicommon.popup.AbstractVmPopupWidget.edit(AbstractVmPopupWidget.java:1518)
at 
org.ovirt.engine.ui.common.widget.uicommon.popup.AbstractModeSwitchingPopupWidget.edit(AbstractModeSwitchingPopupWidget.java:80)
at 
org.ovirt.engine.ui.common.view.popup.AbstractModelBoundWidgetPopupView.edit(AbstractModelBoundWidgetPopupView.java:37)
at 
org.ovirt.engine.ui.common.presenter.AbstractModelBoundPopupPresenterWidget.$init(AbstractModelBoundPopupPresenterWidget.java:105)
at 

[ovirt-users] Re: Unable to mount NFS lun

2018-09-17 Thread Budur Nagaraju
Hi

Am stuck ,can someone help on this?

Thanks,
Nagarau

On Mon, Sep 17, 2018 at 7:10 PM Budur Nagaraju  wrote:

> Hi
>
> We have manually mounted the lun in the node and not seeing any issues
> ,while mounting from the UI its failing , by the way one thing to update is
> that nfs lun is created from the Dell unity NFS version3.
>
> Any help can we get ?
>
> Thanks,
> Nagaraju
> '
>
>
>
> On Mon, Sep 17, 2018 at 6:23 PM Fred Rolland  wrote:
>
>> Hi,
>>
>> Check this page for troubleshooting:
>>
>>
>> https://www.ovirt.org/documentation/how-to/troubleshooting/troubleshooting-nfs-storage-issues/
>>
>> Regards,
>> Freddy
>>
>> On Mon, Sep 17, 2018 at 1:08 PM, Budur Nagaraju 
>> wrote:
>>
>>> Hi
>>>
>>> When I do a NFS mount in the oVirt getting error , below are the logs.
>>>
>>>
>>>
>>> https://pastebin.com/T1ASaB4V
>>>
>>> Thanks,
>>> Nagaraju
>>>
>>>
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/EBK5VIEPTEDF3SRH3IQCFXZBTXHP5UTL/
>>>
>>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EUQWULXEEG6MFSK7YLPPDKOJSW5PWEX5/


[ovirt-users] Re: Unable to upgrade ovirt-node from 4.2.3

2018-09-17 Thread Benedetto Vassallo

 Thank you guys, it worked!

Def. Quota Yuval Turgeman :

Try to first remove the LV for /var/crash or mount it, then remove  
any base that is not used (imgbase base --remove ), then  
yum update again.

 
Documented here (for other LVs):
 
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/recovering_from_failed_nist-800_upgrade



   On Mon, Sep 17, 2018 at 5:13 PM, Sandro Bonazzola  
 wrote:



Adding Yuval

 Il giorno lun 17 set 2018 alle ore 15:16  
 ha scritto:



Hi,
I have installed some 4.2.2 ovirt nodes (fresh installation) and  
upgraded them to 4.2.3 from the ovirt-engine UI.
All was right, but if I want to upgrade from 4.2.3 to any new  
version I got a failure in post script.

In the /tmp/imgbased.log I have the following error:

2018-09-17 14:28:09,073 [DEBUG] (MainThread) Calling: (['rmdir',  
u'/tmp/mnt.POEYF'],) {'close_fds': True, 'stderr': -2}

2018-09-17 14:28:09,080 [DEBUG] (MainThread) Returned:
2018-09-17 14:28:09,081 [ERROR] (MainThread) Failed to migrate etc
Traceback (most recent call last):
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py", line 118, in  
on_new_layer

    check_nist_layout(imgbase, new_lv)
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py", line 209, in  
check_nist_layout

    v.create(t, paths[t]["size"], paths[t]["attach"])
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/volume.py",  
line 48, in create

    "Path is already a volume: %s" % where
AssertionError: Path is already a volume: /var/crash
2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling binary:  
(['umount', '-l', u'/tmp/mnt.gt3IE'],) {}
2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling: (['umount',  
'-l', u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}

2018-09-17 14:28:09,181 [DEBUG] (MainThread) Returned:
2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling binary:  
(['rmdir', u'/tmp/mnt.gt3IE'],) {}
2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling: (['rmdir',  
u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}

2018-09-17 14:28:09,190 [DEBUG] (MainThread) Returned:
2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling binary:  
(['umount', '-l', u'/tmp/mnt.2weYe'],) {}
2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling: (['umount',  
'-l', u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}

2018-09-17 14:28:09,389 [DEBUG] (MainThread) Returned:
2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling binary:  
(['rmdir', u'/tmp/mnt.2weYe'],) {}
2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling: (['rmdir',  
u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}

2018-09-17 14:28:09,397 [DEBUG] (MainThread) Returned:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__main__.py", line 53, in  


    CliApplication()
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__init__.py", line 82, in  
CliApplication

    app.hooks.emit("post-arg-parse", args)
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py",  
line 120, in emit

    cb(self.context, *args)
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py", line 56, in  
post_argparse

    base_lv, _ = LiveimgExtractor(app.imgbase).extract(args.FILENAME)
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py", line 118, in  
extract

    "%s" % size, nvr)
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py", line 99, in  
add_base_with_tree

    new_layer_lv = self.imgbase.add_layer(new_base)
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/imgbase.py",  
line 192, in add_layer

    self.hooks.emit("new-layer-added", prev_lv, new_lv)
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py",  
line 120, in emit

    cb(self.context, *args)
  File  
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py", line 132, in  
on_new_layer

    raise ConfigMigrationError()
imgbased.plugins.osupdater.ConfigMigrationError

I have this on all nodes.
Today I tried to make a fresh 2.2 install on a test VM, execute  
"yum update", updated it to 2.3 and then I got tha same error again.
I did a default installation from  
ovirt-node-ng-installer-ovirt-4.2-2018040514.iso, automatic  
partitioning and nothing customized.

Is there anyone having the same issue or knowing how to solve it?
Thanks in advantage.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: 

[ovirt-users] Re: Unable to upgrade ovirt-node from 4.2.3

2018-09-17 Thread Yuval Turgeman
Try to first remove the LV for /var/crash or mount it, then remove any base
that is not used (imgbase base --remove ), then yum update again.

Documented here (for other LVs):
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/recovering_from_failed_nist-800_upgrade

On Mon, Sep 17, 2018 at 5:13 PM, Sandro Bonazzola 
wrote:

> Adding Yuval
>
>
> Il giorno lun 17 set 2018 alle ore 15:16  ha
> scritto:
>
>> Hi,
>> I have installed some 4.2.2 ovirt nodes (fresh installation) and upgraded
>> them to 4.2.3 from the ovirt-engine UI.
>> All was right, but if I want to upgrade from 4.2.3 to any new version I
>> got a failure in post script.
>> In the /tmp/imgbased.log I have the following error:
>>
>> 2018-09-17 14:28:09,073 [DEBUG] (MainThread) Calling: (['rmdir',
>> u'/tmp/mnt.POEYF'],) {'close_fds': True, 'stderr': -2}
>> 2018-09-17 14:28:09,080 [DEBUG] (MainThread) Returned:
>> 2018-09-17 14:28:09,081 [ERROR] (MainThread) Failed to migrate etc
>> Traceback (most recent call last):
>>   File "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/
>> imgbased/plugins/osupdater.py", line 118, in on_new_layer
>> check_nist_layout(imgbase, new_lv)
>>   File "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/
>> imgbased/plugins/osupdater.py", line 209, in check_nist_layout
>> v.create(t, paths[t]["size"], paths[t]["attach"])
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/volume.py",
>> line 48, in create
>> "Path is already a volume: %s" % where
>> AssertionError: Path is already a volume: /var/crash
>> 2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling binary: (['umount',
>> '-l', u'/tmp/mnt.gt3IE'],) {}
>> 2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling: (['umount', '-l',
>> u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
>> 2018-09-17 14:28:09,181 [DEBUG] (MainThread) Returned:
>> 2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling binary: (['rmdir',
>> u'/tmp/mnt.gt3IE'],) {}
>> 2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling: (['rmdir',
>> u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
>> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Returned:
>> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling binary: (['umount',
>> '-l', u'/tmp/mnt.2weYe'],) {}
>> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling: (['umount', '-l',
>> u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
>> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Returned:
>> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling binary: (['rmdir',
>> u'/tmp/mnt.2weYe'],) {}
>> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling: (['rmdir',
>> u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
>> 2018-09-17 14:28:09,397 [DEBUG] (MainThread) Returned:
>> Traceback (most recent call last):
>>   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
>> "__main__", fname, loader, pkg_name)
>>   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>> exec code in run_globals
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__main__.py",
>> line 53, in 
>> CliApplication()
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__init__.py",
>> line 82, in CliApplication
>> app.hooks.emit("post-arg-parse", args)
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py",
>> line 120, in emit
>> cb(self.context, *args)
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
>> line 56, in post_argparse
>> base_lv, _ = LiveimgExtractor(app.imgbase).extract(args.FILENAME)
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
>> line 118, in extract
>> "%s" % size, nvr)
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
>> line 99, in add_base_with_tree
>> new_layer_lv = self.imgbase.add_layer(new_base)
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/imgbase.py",
>> line 192, in add_layer
>> self.hooks.emit("new-layer-added", prev_lv, new_lv)
>>   File 
>> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py",
>> line 120, in emit
>> cb(self.context, *args)
>>   File "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/
>> imgbased/plugins/osupdater.py", line 132, in on_new_layer
>> raise ConfigMigrationError()
>> imgbased.plugins.osupdater.ConfigMigrationError
>>
>> I have this on all nodes.
>> Today I tried to make a fresh 2.2 install on a test VM, execute "yum
>> update", updated it to 2.3 and then I got tha same error again.
>> I did a default installation from 
>> ovirt-node-ng-installer-ovirt-4.2-2018040514.iso,
>> automatic partitioning and nothing customized.
>> Is there anyone having the same issue or knowing how to solve it?
>> Thanks in advantage.
>> ___
>> Users mailing list -- 

[ovirt-users] Re: Unable to upgrade ovirt-node from 4.2.3

2018-09-17 Thread Sandro Bonazzola
Adding Yuval

Il giorno lun 17 set 2018 alle ore 15:16  ha
scritto:

> Hi,
> I have installed some 4.2.2 ovirt nodes (fresh installation) and upgraded
> them to 4.2.3 from the ovirt-engine UI.
> All was right, but if I want to upgrade from 4.2.3 to any new version I
> got a failure in post script.
> In the /tmp/imgbased.log I have the following error:
>
> 2018-09-17 14:28:09,073 [DEBUG] (MainThread) Calling: (['rmdir',
> u'/tmp/mnt.POEYF'],) {'close_fds': True, 'stderr': -2}
> 2018-09-17 14:28:09,080 [DEBUG] (MainThread) Returned:
> 2018-09-17 14:28:09,081 [ERROR] (MainThread) Failed to migrate etc
> Traceback (most recent call last):
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
> line 118, in on_new_layer
> check_nist_layout(imgbase, new_lv)
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
> line 209, in check_nist_layout
> v.create(t, paths[t]["size"], paths[t]["attach"])
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/volume.py",
> line 48, in create
> "Path is already a volume: %s" % where
> AssertionError: Path is already a volume: /var/crash
> 2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling binary: (['umount',
> '-l', u'/tmp/mnt.gt3IE'],) {}
> 2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling: (['umount', '-l',
> u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
> 2018-09-17 14:28:09,181 [DEBUG] (MainThread) Returned:
> 2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling binary: (['rmdir',
> u'/tmp/mnt.gt3IE'],) {}
> 2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling: (['rmdir',
> u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Returned:
> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling binary: (['umount',
> '-l', u'/tmp/mnt.2weYe'],) {}
> 2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling: (['umount', '-l',
> u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Returned:
> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling binary: (['rmdir',
> u'/tmp/mnt.2weYe'],) {}
> 2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling: (['rmdir',
> u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
> 2018-09-17 14:28:09,397 [DEBUG] (MainThread) Returned:
> Traceback (most recent call last):
>   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
>   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
> exec code in run_globals
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__main__.py",
> line 53, in 
> CliApplication()
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__init__.py",
> line 82, in CliApplication
> app.hooks.emit("post-arg-parse", args)
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py",
> line 120, in emit
> cb(self.context, *args)
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
> line 56, in post_argparse
> base_lv, _ = LiveimgExtractor(app.imgbase).extract(args.FILENAME)
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
> line 118, in extract
> "%s" % size, nvr)
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
> line 99, in add_base_with_tree
> new_layer_lv = self.imgbase.add_layer(new_base)
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/imgbase.py",
> line 192, in add_layer
> self.hooks.emit("new-layer-added", prev_lv, new_lv)
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py",
> line 120, in emit
> cb(self.context, *args)
>   File
> "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
> line 132, in on_new_layer
> raise ConfigMigrationError()
> imgbased.plugins.osupdater.ConfigMigrationError
>
> I have this on all nodes.
> Today I tried to make a fresh 2.2 install on a test VM, execute "yum
> update", updated it to 2.3 and then I got tha same error again.
> I did a default installation from
> ovirt-node-ng-installer-ovirt-4.2-2018040514.iso, automatic partitioning
> and nothing customized.
> Is there anyone having the same issue or knowing how to solve it?
> Thanks in advantage.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/KT4JDVGJKTXXPLBK7LHH42E3DDOKKCOL/
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

[ovirt-users] Re: [ANN] oVirt Engine 4.2.6 async update is now available

2018-09-17 Thread Staniforth, Paul
Hi Yuval,

   this wasn't manual but using yum update or yum reinstall. The 
node producing most trouble had been updated to 4.2.5-1 but I had to remove 
some of the LV's to get it to work. The only LV with a abrt process hanging was 
/dev/onn/var_log I believe but I suppose it could have been running while the 
fallback was trying to remove /dev/onn/ovirt-node-ng-4.2.6.1-0.20180913.0+1


We had 3 nodes that have been upgraded from 4.1.9 - 4.2.4 - 4.2.6-1 (one via 
4.2.5-1)


Regards,

   Paul S.


From: Yuval Turgeman 
Sent: 16 September 2018 08:24
To: Staniforth, Paul
Cc: users
Subject: Re: [ovirt-users] Re: [ANN] oVirt Engine 4.2.6 async update is now 
available

The failure was caused because you had /var/log LV that was not mounted for 
some reason (was that manual by any chance?).  onn/var_crash was created during 
the update and removed successfully because of the var_log issue.  The only 
question is why it didn't clean up the onn/ovirt-node-ng-4.2.6, it failed 
to clean it up for some reason.  Was the abrt process hanging this LV ?

Thanks,
Yuval

On Fri, Sep 14, 2018 at 11:53 AM, 
mailto:p.stanifo...@leedsbeckett.ac.uk>> wrote:
I've managed to upgrade them now by removing logical volumes, usually it's just 
/dev/onn/home but one I had to keep reinstalling see were it failed so had to

lvremove /dev/onn/ovirt-node-ng-4.2.6.1-0.20180913.0+1
lvremove /dev/onn/var_crash
lvremove   /dev/onn/var_log
lvremove   /dev/onn/var_log_audit

I had trouble removing because failed because it was in use since there was an 
abrt process holding onto the mount.

Thanks,
 Paul S.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to 
users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LAS4IEPE2IF53QJVPMJEFLU2Q76AWQRD/

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
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GLLPQLNSK6G6HAVGRN4POB34ZXMUDWYT/


[ovirt-users] 4.2 User Portal

2018-09-17 Thread Стаценко Константин Юрьевич
Hello!
Users cannot edit and expand VM’s disks from the User Portal after 4.2 upgrade 
anymore.
VM UI screenshot attached.
Users can press Edit icon, but only “Editing” appears and nothing more.
Same thing happens under admin’s accounts on User Portal.
From Admin Portal everything is fine.
How can we fix this issue, so users can edit they VM from the User Portal as it 
was in 4.1 ?
Thanks.

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UP6HCCE5OIC3ITWDI24SRZ52S5WFNV2P/


[ovirt-users] Unable to upgrade ovirt-node from 4.2.3

2018-09-17 Thread benedetto . vassallo
Hi,
I have installed some 4.2.2 ovirt nodes (fresh installation) and upgraded them 
to 4.2.3 from the ovirt-engine UI.
All was right, but if I want to upgrade from 4.2.3 to any new version I got a 
failure in post script.
In the /tmp/imgbased.log I have the following error:

2018-09-17 14:28:09,073 [DEBUG] (MainThread) Calling: (['rmdir', 
u'/tmp/mnt.POEYF'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,080 [DEBUG] (MainThread) Returned: 
2018-09-17 14:28:09,081 [ERROR] (MainThread) Failed to migrate etc
Traceback (most recent call last):
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 118, in on_new_layer
check_nist_layout(imgbase, new_lv)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 209, in check_nist_layout
v.create(t, paths[t]["size"], paths[t]["attach"])
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/volume.py", line 
48, in create
"Path is already a volume: %s" % where
AssertionError: Path is already a volume: /var/crash
2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling binary: (['umount', '-l', 
u'/tmp/mnt.gt3IE'],) {}
2018-09-17 14:28:09,092 [DEBUG] (MainThread) Calling: (['umount', '-l', 
u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,181 [DEBUG] (MainThread) Returned: 
2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling binary: (['rmdir', 
u'/tmp/mnt.gt3IE'],) {}
2018-09-17 14:28:09,182 [DEBUG] (MainThread) Calling: (['rmdir', 
u'/tmp/mnt.gt3IE'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,190 [DEBUG] (MainThread) Returned: 
2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling binary: (['umount', '-l', 
u'/tmp/mnt.2weYe'],) {}
2018-09-17 14:28:09,190 [DEBUG] (MainThread) Calling: (['umount', '-l', 
u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,389 [DEBUG] (MainThread) Returned: 
2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling binary: (['rmdir', 
u'/tmp/mnt.2weYe'],) {}
2018-09-17 14:28:09,389 [DEBUG] (MainThread) Calling: (['rmdir', 
u'/tmp/mnt.2weYe'],) {'close_fds': True, 'stderr': -2}
2018-09-17 14:28:09,397 [DEBUG] (MainThread) Returned: 
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__main__.py", 
line 53, in 
CliApplication()
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/__init__.py", 
line 82, in CliApplication
app.hooks.emit("post-arg-parse", args)
  File "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py", 
line 120, in emit
cb(self.context, *args)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
 line 56, in post_argparse
base_lv, _ = LiveimgExtractor(app.imgbase).extract(args.FILENAME)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
 line 118, in extract
"%s" % size, nvr)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/update.py",
 line 99, in add_base_with_tree
new_layer_lv = self.imgbase.add_layer(new_base)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 
192, in add_layer
self.hooks.emit("new-layer-added", prev_lv, new_lv)
  File "/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/hooks.py", 
line 120, in emit
cb(self.context, *args)
  File 
"/tmp/tmp.s2GHHNumuT/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 132, in on_new_layer
raise ConfigMigrationError()
imgbased.plugins.osupdater.ConfigMigrationError

I have this on all nodes.
Today I tried to make a fresh 2.2 install on a test VM, execute "yum update", 
updated it to 2.3 and then I got tha same error again.
I did a default installation from 
ovirt-node-ng-installer-ovirt-4.2-2018040514.iso, automatic partitioning and 
nothing customized.
Is there anyone having the same issue or knowing how to solve it?
Thanks in advantage.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KT4JDVGJKTXXPLBK7LHH42E3DDOKKCOL/


[ovirt-users] Re: Unable to mount NFS lun

2018-09-17 Thread Fred Rolland
Hi,

Check this page for troubleshooting:

https://www.ovirt.org/documentation/how-to/troubleshooting/troubleshooting-nfs-storage-issues/

Regards,
Freddy

On Mon, Sep 17, 2018 at 1:08 PM, Budur Nagaraju  wrote:

> Hi
>
> When I do a NFS mount in the oVirt getting error , below are the logs.
>
>
>
> https://pastebin.com/T1ASaB4V
>
> Thanks,
> Nagaraju
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
> guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
> message/EBK5VIEPTEDF3SRH3IQCFXZBTXHP5UTL/
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UXXHRMSQWLKGEURU7Y3LXZ5SGSH7I6GM/


[ovirt-users] Proxmox - oVirt Migration

2018-09-17 Thread Leo David
Hello everyone,
I have this situation where I need to migrate about 20 vms from Proxmox to
oVirt.
In this case,  its about qcow2 images running on Proxmox.
I there a recomended way and procedure for doing this ?
Thank you very much !

-- 
Best regards, Leo David
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YV5CMHDZSXJ5FQ3QRYNL2QKGXGKYHS7L/


[ovirt-users] Unable to mount NFS lun

2018-09-17 Thread Budur Nagaraju
Hi

When I do a NFS mount in the oVirt getting error , below are the logs.



https://pastebin.com/T1ASaB4V

Thanks,
Nagaraju
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EBK5VIEPTEDF3SRH3IQCFXZBTXHP5UTL/


[ovirt-users] disk locked after export as OVA

2018-09-17 Thread adam...@adagene.com.cn
Hello, everyone. I tried to export a vm as OVA. I got a error in webui:
VDSM ovirt1.ntbaobei.com command HSMGetAllTasksStatusesVDS failed: Volume Group 
not big enough: (u'Not enough free extents for extending LV 
d9f2378f-92f0-4bc1-96a8-20a0f2c575cb/c515a3f9-0590-4ebe-81c5-9d0993f1fec9 
(free=848, needed=872)',)

seems no enough space in the storage domain.
I deleted the vm which i wanted to export as OVA before, but I saw a disk with 
id 8140d2e7-6908-438e-a646-23e58a33913e left in the storage and the status is 
locked. 

here's some log in the engine.log:
2018-09-17 14:27:03,467+08 INFO  
[org.ovirt.engine.core.vdsbroker.irsbroker.CopyImageVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-107849) 
[a407f6a9-445d-4ccc-b998-f9dfc6dc67ec] START, CopyImageVDSCommand( 
CopyImageVDSCommandParameters:{storagePoolId='79432500-ad45-11e8-98f3-00163e188641',
 ignoreFailoverLimit='false', 
storageDomainId='d9f2378f-92f0-4bc1-96a8-20a0f2c575cb', 
imageGroupId='ee55bbe7-8001-4c82-b1a6-0cac7710704b', 
imageId='701a7472-8c00-4b9f-aa87-4837eb128695', 
dstImageGroupId='8140d2e7-6908-438e-a646-23e58a33913e', 
vmId='b3aa623e-3072-430e-87d6-b81a3b07f466', 
dstImageId='c515a3f9-0590-4ebe-81c5-9d0993f1fec9', imageDescription='', 
dstStorageDomainId='d9f2378f-92f0-4bc1-96a8-20a0f2c575cb', 
copyVolumeType='LeafVol', volumeFormat='COW', preallocate='Sparse', 
postZero='false', discard='false', force='true'}), log id: 164e3046
2018-09-17 14:27:03,467+08 INFO  
[org.ovirt.engine.core.vdsbroker.irsbroker.CopyImageVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-107849) 
[a407f6a9-445d-4ccc-b998-f9dfc6dc67ec] ++ 
dstImageGUID=8140d2e7-6908-438e-a646-23e58a33913e

I think maybe some command did not been excuted after I export the vm as OVA. I 
can find the similar case here:
https://access.redhat.com/solutions/1298893 

I have used the tool  unlock_entity.sh but cannot find any disk that is locked.
So what should I do to delete the disk that is been locked?





yours Adam
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BCB7FFCGA5CTTC44K3V766N4OSXEGBGE/


[ovirt-users] Re: Best way to update dns config of ovirt node

2018-09-17 Thread Gianluca Cecchi
On Sun, Sep 16, 2018 at 7:56 AM Edward Haas  wrote:

>
>
> On Fri, Sep 14, 2018 at 9:43 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Thu, Sep 13, 2018 at 7:53 AM Edward Haas  wrote:
>>
>>>
>>>
>>> On Mon, Sep 10, 2018 at 5:53 PM, Gianluca Cecchi <
>>> gianluca.cec...@gmail.com> wrote:
>>>
 Hello,
 supposing to have ovirt-ng node 4.2.6 and that ovirtmgmt config
 regarding DNS servers has to be updated, what is the correct way to 
 proceed?

>>>
>>> DNS should be editable from the network attachment window.
>>>
>>
>> Thanks for your answer Edward.
>> What do you mean with "network attachment window"?
>> a) Network > Networks, then select ovirtmgmt line and edit, putting DNS
>> info (that is empty right now)
>> or
>> b) Compute > Hosts, then select host1 line, click on host1 name, then
>> Network Interfaces and Setup Host Networks. then edit ovirtmgmt > DNS
>> Configuration (that is empty right now)
>> or what?
>>
>
> I meant (b). Option (a) is there to apply the same DNS entries over all
> hosts for that specific network.
> I do not see a problem of using both.
>

OK.
What is it expected to happen if for example I have 4 active nodes and use
a)?
Possibly all of them loosing ovirtmgmt connection with possibly dangerous
effects?



> If you add a new host, Engine will read the existing DNS entries from the
> host and persist them. (you will see them in the setup-networks window (b)).
>

The strange thing is that apparently it made what you say (from a files
content point of view) but there is no match if you go into configuration
inside web admin gui pages, neither at cluster level, nor at host level.
This was what seemed strange to me.
Please notice that these hosts were installed in 4.1.x and then update
several times up to 4.2.6.
So it could be the case of some sort of bug in previous versions and not if
I plain install right now in 4.2.6 (not tested)



> Upgraded systems (hosts have been added before DNS configuration was
> available) will have it empty and you will need to explicitly set it.
>
It is not my case.



>>
>>> The values are added through ifcfg, therefore its logic of adding it to
>>> resolv.conf is used.
>>>
>>
>> I have also opened a case for another environment where I'm using RHV-H
>> hosts, that should be quite similar to ovirt-node-ng
>> In that environment one of the original M$ based dns server was changed
>> (that was the one I had as primary) creating some latency problems.
>> Using setup host networks generated big problems, especially if doing on
>> the host where hosted engine was running.
>> I verified that a safe way to modify DNS config is:
>> - evacuate VMs from host
>> - put host into maintenance
>> - change dns settings in setup host networks
>> - reboot the host
>> - activate the host
>>
>> I do not see a reason to pass all these steps unless we have a bug.
> The DNS entry are supposed to be applied immediately through ifcfg,
> rebooting is an precaution to make sure it has been correctly persisted.
> And if the management network is not serving VM/s, then no VM evacuation
> is needed.
>

If host is not reachable through ovirtmgmt doesn't fencing take place? And
so indirect consequence a move of the VMs it had in charge?

>
> I guess the risk here is the management network editing, which is
> sensitive (Engine looses connectivity and unexpected behaviour may occur).
> If there is a problem with this scenario, I would consider it a bug.
>
>
>> This way the "persistent" files are initially updated and then at the
>> reboot the ifcfg and resolv.conf files are correctly updated
>> If you are interested my case is 02179117
>>
>
> I could not find such a BZ.
>

This is a Red Hat case number, not a bugzilla entry. Because I had the same
kind of problems on oVirt based environments and RHV based ones that are
present.
So for RHV  I opened a case.
As a consequence of the case, it was created this solution that I have not
tested yet:
https://access.redhat.com/solutions/3613731

Please note that it requires RH account, but in my opinion should be of
public domain or similar information put inside oVirt documentation pages.
It could happen having to change DNS and it can be useful to know the
recommended workflow for that

>
>> As far as I remember, when adding a host (that reports the nameservers),
> the DNS entries learned are added to the Engine config and used when
> sending the first setup-networks to VDSM.
> But there were several iterations of this flow, perhaps it changed (will
> check).
>
>
>>
Note also my comments regarding environment installed in 4.1 and then
updated to 4.2

Thanks
Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 

[ovirt-users] Re: Slow vm transfer speed from vmware esxi 5

2018-09-17 Thread Richard W.M. Jones
On Sun, Sep 16, 2018 at 07:30:09PM +0300, Nir Soffer wrote:
> I used to disable the limit enforcing "sparse" in libguestfs upstream
> source, but lately the simple check at the python plugin level was moved to
> to the ocaml code, and I did not have time to understand it yet.
>
> If you want to remove the limit, try to look here:
> https://github.com/libguestfs/libguestfs/blob/51a9c874d3f0a9c4780f2cd3ee7072180446e685/v2v/output_rhv_upload.ml#L163
> 
> On RHEL, there is no such limit, and you can import vms to any kind of
> storage.
> 
> Richard, can we remove the limit on sparse format? I don't see how this
> limit
> helps anyone.

We already remove it downstream in all RHEL and LP builds.  Here is
the commit which does that:

https://github.com/libguestfs/libguestfs/commit/aa5608a922bd35db28f555e53aea2308361991dd

We could remove it upstream, but AIUI it causes conversions to break
with no easy way for users to understand what -oa modes are supported
by what backends.  To fix it properly we need a way for oVirt /
imageio / whatever to describe what modes are possible for the current
backend.

> oVirt support several combinations:
> 
> file:
> - raw sparse
> - raw preallocated
> - qcow2 sparse (unsupported in v2v)
> 
> block:
> - raw preallocated
> - qcow2 sparse (unsupported in v2v)
> 
> It seems that oVirt SDK is does not have a good way to select the format
> yet, so
> virt-v2v cannot select the format for the user. This means the user need to
> select
> the format.

Right.

There are two open bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1600547
https://bugzilla.redhat.com/show_bug.cgi?id=1574734

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TP6JXLNGSI7KUKGPUZS3RXMA5MMPV4UZ/