date:20190813

[ovirt-users] Re: oVirt 4.3.5 potential issue with NFS storage

2019-08-13 Thread Vrgotic, Marko

Hey Shanii,

Correct, this is exactly what I do/did.
I did “umount /mnt/rhevstore” but I mentioned NFS storage path in order to be 
precise in description.

Thing is that I am able to mount it, as well as oVirt during Host provisioning. 
I was even able to create VMs on it from same Hypervisor.
As far as I remember, I was able to write to the storage and create a random 
file.

I will give it second attempt.


— — —
Met vriendelijke groet / Kind regards,

Marko Vrgotic




From: Shani Leviim 
Date: Monday, 12 August 2019 at 09:32
To: "Vrgotic, Marko" 
Cc: "users@ovirt.org" 
Subject: Re: [ovirt-users] Re: oVirt 4.3.5 potential issue with NFS storage

Basically, I meant to verify the access by ssh, but I want to verify something 
following your detailed reply:

According to [1], in order to set a NetApp NFS server, the required steps 
should look like this:

# mount NetApp_NFS:/path/to/export /mnt

# chown -R 36.36 /mnt

# chmod -R 755 /mnt

# umount /mnt
Which is quite similar to the steps you've mentioned, except the last step of 
unmounting:
Unmount the 10.214.13.64:/ovirt_production


I think that you had to unmount /mnt/rhevstore instead.


Can you please verify?


[1] https://access.redhat.com/solutions/660143

Regards,
Shani Leviim


On Sun, Aug 11, 2019 at 10:57 PM Vrgotic, Marko 
mailto:m.vrgo...@activevideo.com>> wrote:
Hi Shani,

Thank you for your reply, but
How do I do that?
Reason why I am asking is following:
Hosts 2,3,4 do not have that issue. Host 1 and 5 do.
What I learned previously is that when using Netapp based NFS, which we are, 
it’s required to before provisioning SHE and/or just adding a Host to a pool, 
it’s required to execute following steps:

Create random dir on a host:
- mkdir /mnt/rhevstore
Mount netapp volume to the dir
- mount -o sec=sys -t nfs 10.214.13.64:/ovirt_production /mnt/rhevstore
Set ownership to vdsm:kvm (36:36):
- chown -R vdsm:kvm /mnt/rhevstore/*
Unmount the 10.214.13.64:/ovirt_production

I do not expect the above ownership actions need to be done initially on each 
host, before starting the deployment, otherwise it would be practically 
impossible to expand the Host pool.

All 5 hosts are provisioned in same way. How? I am using foreman to provision 
these servers, so they are built of same kickstart hostgroup template.


I even installed ovirt-hosted-engine-setup package to make sure all required 
packages, users and groups are in place before adding host to oVirt via UI or 
Ansible.


Is it possible that we if I am already using or heavily using the mentioned 
volume via Hosts already added to oVirt pool, that ownership actions 
executed,on host about to be added to the pool, will fail to complete setting 
ownership on all required files on the volume?

To repeat the question above: How do I make sure Host can read metadata file of 
the storage volume?

Kindly awaiting your reply.

All best,
Marko Vrgotic
Sent from my iPhone

On 11 Aug 2019, at 01:19, Shani Leviim 
mailto:slev...@redhat.com>> wrote:
Hi Marko,
Is seems that there's a connectivity problem with host 10.210.13.64.
Can you please make sure the metadata under 
/rhev/data-center/mnt/10.210.13.64:_ovirt__production/6effda5e-1a0d-4312-bf93-d97fa9eb5aee/dom_md/metadata
 is accessible?

Regards,
Shani Leviim


On Sat, Aug 10, 2019 at 2:57 AM Vrgotic, Marko 
mailto:m.vrgo...@activevideo.com>> wrote:
Log files from ovirt engine and ovirt-sj-05 vdsm  attached.

Its related to host named: ovirt-sj-05.ictv.com

Kindly awaiting your reply.


— — —
Met vriendelijke groet / Kind regards,

Marko Vrgotic



From: "Vrgotic, Marko" 
mailto:m.vrgo...@activevideo.com>>
Date: Thursday, 8 August 2019 at 17:02
To: Shani Leviim mailto:slev...@redhat.com>>
Cc: "users@ovirt.org" 
mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Re: oVirt 4.3.5 potential issue with NFS storage

Hey Shanii,

Thank you for the reply.
Sure, I will attach the full logs asap.
What do you mean by “flow you are doing”?

Kindly awaiting your reply.

Marko Vrgotic

From: Shani Leviim mailto:slev...@redhat.com>>
Date: Thursday, 8 August 2019 at 00:01
To: "Vrgotic, Marko" 
mailto:m.vrgo...@activevideo.com>>
Cc: "users@ovirt.org" 
mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Re: oVirt 4.3.5 potential issue with NFS storage

Hi,
Can you please clarify the flow you're doing?
Also, can you please attach full vdsm and engine logs?

Regards,
Shani Leviim


On Thu, Aug 8, 2019 at 6:25 AM Vrgotic, Marko 
mailto:m.vrgo...@activevideo.com>> wrote:
Log line form VDSM:

“[root@ovirt-sj-05 ~]# tail -f /var/log/vdsm/vdsm.log | grep WARN
2019-08-07 09:40:03,556-0700 WARN  (check/loop) [storage.check] Checker 
u'/rhev/data-center/mnt/10.210.13.64:_ovirt__production/bda97276-a399-448f-9113-017972f6b55a/dom_md/metadata'
 is blocked for 20.00 seconds (check:282)
2019-08-07 09:40:47,132-0700 WARN  (monitor/bda9727) [storage.Monitor] Host id 
for domain

[ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

2019-08-13 Thread Staniforth, Paul

Hello Mathias,
I also had this problem, the flood of warning messages 
was most notably generated when showing all the VMs running from the admin 
portal dashboard as we had 70 VMs running this generated the following but for 
all 70 VMs. I was able to restart most of the VMs otherwise the admin portal 
became unusable.
I don't recall this being a problem upgrading from 4.1 to 4.2

Regards
Paul S.

2019-08-13 11:44:36,771+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'customCompatibilityVersion' can 
not be updated when status is 'Up'
2019-08-13 11:44:36,771+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'exportDate' can not be updated 
when status is 'Up'
2019-08-13 11:44:36,771+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'managedDeviceMap' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,771+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'ovfVersion' can not be updated 
when status is 'Up'
2019-08-13 11:44:36,772+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'balloonEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,772+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'watchdog' can not be updated when 
status is 'Up'
2019-08-13 11:44:36,773+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'rngDevice' can not be updated 
when status is 'Up'
2019-08-13 11:44:36,774+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'soundDeviceEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,774+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'consoleEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,775+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'virtioScsiEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,776+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'graphicsDevices' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'customCompatibilityVersion' can 
not be updated when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'exportDate' can not be updated 
when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'managedDeviceMap' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'ovfVersion' can not be updated 
when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'balloonEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,491+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'watchdog' can not be updated when 
status is 'Up'
2019-08-13 11:44:39,492+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'rngDevice' can not be updated 
when status is 'Up'
2019-08-13 11:44:39,493+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'soundDeviceEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,493+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'consoleEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,494+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'virtioScsiEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,495+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'graphicsDevices' can not be

[ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

2019-08-13 Thread Sharon Gratch

Hi,
We checked that issue and found out that you are right and this extra
logging lines problem is caused by "next run configuration" improvements
added to oVirt 4.3.5.

The current behaviour is that for each running VM with next run
configuration existed, a warning line of "Field 'xxx' can not be
updated when status is 'Up'" appears in log, per each vm device and
whenever the vms list is refreshed.
This definitely may flood the engine log if there are few such VMs.

Can you please file a bug on that?

Thanks,
Sharon



On Tue, Aug 13, 2019 at 5:01 PM Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:

> Thanks for the feedback, I think my description was a bit clumsy, but at
> least someone confirms that he has seen this...
> I still hope it's linked to unfinished VM "Custom Compatibility Version"
> updates, tomorrow I'll know, when I finally can do the last VM reboots.
> My "Administration Portal" is still usable, but nevertheless I think
> this is something the upstream developers should look into.
>
> Regards
> Matthias
>
> Am 13.08.19 um 12:48 schrieb Staniforth, Paul:
> > Hello Mathias,
> >  I also had this problem, the flood of warning
> messages was most notably generated when showing all the VMs running from
> the admin portal dashboard as we had 70 VMs running this generated the
> following but for all 70 VMs. I was able to restart most of the VMs
> otherwise the admin portal became unusable.
> > I don't recall this being a problem upgrading from 4.1 to 4.2
> >
> > Regards
> >  Paul S.
> >
> > 2019-08-13 11:44:36,771+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'customCompatibilityVersion'
> can not be updated when status is 'Up'
> > 2019-08-13 11:44:36,771+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'exportDate' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:36,771+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'managedDeviceMap' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:36,771+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'ovfVersion' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:36,772+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'balloonEnabled' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:36,772+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'watchdog' can not be updated
> when status is 'Up'
> > 2019-08-13 11:44:36,773+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'rngDevice' can not be updated
> when status is 'Up'
> > 2019-08-13 11:44:36,774+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'soundDeviceEnabled' can not
> be updated when status is 'Up'
> > 2019-08-13 11:44:36,774+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'consoleEnabled' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:36,775+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'virtioScsiEnabled' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:36,776+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'graphicsDevices' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:39,490+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [0b246c13-223f-4728-b988-5da34139aeb2] Field 'customCompatibilityVersion'
> can not be updated when status is 'Up'
> > 2019-08-13 11:44:39,490+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [0b246c13-223f-4728-b988-5da34139aeb2] Field 'exportDate' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:39,490+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [0b246c13-223f-4728-b988-5da34139aeb2] Field 'managedDeviceMap' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:39,490+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [0b246c13-223f-4728-b988-5da34139aeb2] Field 'ovfVersion' can not be
> updated when status is 'Up'
> > 2019-08-13 11:44:39,490+01 WARN
> [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)
> [0b246c13-223f-4728-b988-5da34139aeb2] Field 'balloonEnabled' can not be
> updated when

[ovirt-users] ovirt node install

2019-08-13 Thread Staniforth, Paul

Hello,

on the latest version of the oVirt-node install running nodectl 
info gives the error



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 "/usr/lib/python2.7/site-packages/nodectl/__main__.py", line 42, in 

CliApplication()
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line 200, in 
CliApplication
return cmdmap.command(args)
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line 118, in 
command
return self.commands[command](**kwargs)
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line 76, in info
Info(self.imgbased, self.machine).write()
  File "/usr/lib/python2.7/site-packages/nodectl/info.py", line 46, in __init__
self._fetch_information()
  File "/usr/lib/python2.7/site-packages/nodectl/info.py", line 49, in 
_fetch_information
self._get_bootloader_info()
  File "/usr/lib/python2.7/site-packages/nodectl/info.py", line 62, in 
_get_bootloader_info
bootinfo["entries"][k] = v.__dict__
AttributeError: 'list' object has no attribute '__dict__'



Also what is the correct way to update from ovirt node 4.2 to 4.3?

I used

yum install 
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.4-1.el7.noarch.rpm

I then did yum erase ovirt-release42 and rm  /etc/yum.repos.d/ovirt-4.2*

Regards,
   Paul S.
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
___
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/GNXDVTU66ZUFIRTHTNB2RPBGVYIFYLF5/

[ovirt-users] Re: Either allow 2 CD-ROM's or selectable *.vfd Floppy Images from Storage via Run Once other than from deprcated ISO-Storage

2019-08-13 Thread Staniforth, Paul

You should be able to use DISM to create a slipstream ISO then you could add 
updates and drivers to this install media.


https://www.tenforums.com/tutorials/95008-dism-add-remove-drivers-offline-image.html


or use something like


https://www.ntlite.com/


Regards,

 Paul S.


From: Michal Skrivanek 
Sent: 13 August 2019 13:34
To: Vinícius Ferrão
Cc: users
Subject: [ovirt-users] Re: Either allow 2 CD-ROM's or selectable *.vfd Floppy 
Images from Storage via Run Once other than from deprcated ISO-Storage



On 12 Aug 2019, at 15:05, Vinícius Ferrão 
mailto:fer...@versatushpc.com.br>> wrote:

Ralf, you can change CD on the Load Drivers section.

Change for the oVirt Tools Disc, load the drivers and then change back to 
Windows.

you can also use emulate drivers during installation, e.g. in Run Once dialog 
instead of virtio drivers


It's a bad workflow, I know. But it's how I'm doing here. I agree that the 
Windows Tools is not really friendly with oVirt.

go ahead and complain to Microsoft that they don't include virtio drivers in 
their installation images. Without that we can't really do much...they're just 
not there out of the box.

Thanks,
michal


Sent from my iPhone

On 12 Aug 2019, at 08:03, Ralf Schenk mailto:r...@databay.de>> 
wrote:


Hello,

when Installing Windows VM's on Ovirt we need either 2 CD-ROM's attached as ISO 
Files (Installer ISO and Virtio-Win-ISO) to be able to install to 
Virtio-(SCSI)-Disks.

In Ovirt 4.3.4 it is not possible to attach 2 CD-ROM's to a VM. So we have to 
use Floppy Images (virtio-win-*.vfd) attached to install drivers within 
Installer.

We need to use "Run Once" to attach flopppy disks. There are only *.vfd 
selectable which are located on ISO-Storage.Domain, which will be deprecated 
now or then.

-> We won't be able to install Windows VM's from unmodified ISO Installer-CD's 
without ISO Storage Domain or making *.vfd Files selectable via "Run Once"

When will that be available... ?

Bye

--



Ralf Schenk
fon +49 (0) 24 05 / 40 83 70
fax +49 (0) 24 05 / 40 83 759
mail r...@databay.de

Databay AG
Jens-Otto-Krag-Straße 11
D-52146 Würselen
www.databay.de

Sitz/Amtsgericht Aachen * HRB:8437 * USt-IdNr.: DE 210844202
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp 
Hermanns
Aufsichtsratsvorsitzender: Wilhelm Dohmen

___
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/3G5BEWATSBZCUKLPS5ZNOAFDHIVNAYQV/
___
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:

[ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

2019-08-13 Thread Matthias Leopold

Thanks for the feedback, I think my description was a bit clumsy, but at 
least someone confirms that he has seen this...
I still hope it's linked to unfinished VM "Custom Compatibility Version" 
updates, tomorrow I'll know, when I finally can do the last VM reboots.
My "Administration Portal" is still usable, but nevertheless I think 
this is something the upstream developers should look into.


Regards
Matthias

Am 13.08.19 um 12:48 schrieb Staniforth, Paul:

Hello Mathias,
 I also had this problem, the flood of warning messages 
was most notably generated when showing all the VMs running from the admin 
portal dashboard as we had 70 VMs running this generated the following but for 
all 70 VMs. I was able to restart most of the VMs otherwise the admin portal 
became unusable.
I don't recall this being a problem upgrading from 4.1 to 4.2

Regards
 Paul S.

2019-08-13 11:44:36,771+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'customCompatibilityVersion' can 
not be updated when status is 'Up'
2019-08-13 11:44:36,771+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'exportDate' can not be updated 
when status is 'Up'
2019-08-13 11:44:36,771+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'managedDeviceMap' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,771+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'ovfVersion' can not be updated 
when status is 'Up'
2019-08-13 11:44:36,772+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'balloonEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,772+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'watchdog' can not be updated when 
status is 'Up'
2019-08-13 11:44:36,773+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'rngDevice' can not be updated 
when status is 'Up'
2019-08-13 11:44:36,774+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'soundDeviceEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,774+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'consoleEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,775+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'virtioScsiEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:36,776+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'graphicsDevices' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'customCompatibilityVersion' can 
not be updated when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'exportDate' can not be updated 
when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'managedDeviceMap' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'ovfVersion' can not be updated 
when status is 'Up'
2019-08-13 11:44:39,490+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'balloonEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,491+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'watchdog' can not be updated when 
status is 'Up'
2019-08-13 11:44:39,492+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'rngDevice' can not be updated 
when status is 'Up'
2019-08-13 11:44:39,493+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) 
[0b246c13-223f-4728-b988-5da34139aeb2] Field 'soundDeviceEnabled' can not be 
updated when status is 'Up'
2019-08-13 11:44:39,493+01 WARN  
[org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855)

[ovirt-users] Disk Allocation policy changes after a snapshot

2019-08-13 Thread Kevin Doyle

Hi I have linux VM with 2 disks one for OS is sparse the other is for a 
Database and is Preallocated. When I take a snapshot of the VM both disks 
change to sparse policy but the disks in the snapshot are 1 sparse and 1 
allocated. Before the snapshot the VM was running fine, now it crashes when 
data is written to the database. When I delete the snapshot the disks go back 
to 1 sparse and 1 allocated. Has anyone else seen this happen. Ovirt is 
4.3.2.1-1.el7 and it is running on a hostedEngine

Many thanks
Kevin
___
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/OAT5MIMTIZUUHENZNQI6N7MPGHK4TN7C/

[ovirt-users] Re: Either allow 2 CD-ROM's or selectable *.vfd Floppy Images from Storage via Run Once other than from deprcated ISO-Storage

2019-08-13 Thread Michal Skrivanek



> On 12 Aug 2019, at 15:05, Vinícius Ferrão  wrote:
> 
> Ralf, you can change CD on the Load Drivers section.
> 
> Change for the oVirt Tools Disc, load the drivers and then change back to 
> Windows.

you can also use emulate drivers during installation, e.g. in Run Once dialog 
instead of virtio drivers

> 
> It’s a bad workflow, I know. But it’s how I’m doing here. I agree that the 
> Windows Tools is not really friendly with oVirt.

go ahead and complain to Microsoft that they don’t include virtio drivers in 
their installation images. Without that we can’t really do much…they’re just 
not there out of the box.

Thanks,
michal

> 
> Sent from my iPhone
> 
> On 12 Aug 2019, at 08:03, Ralf Schenk  > wrote:
> 
>> Hello,
>> 
>> when Installing Windows VM's on Ovirt we need either 2 CD-ROM's attached as 
>> ISO Files (Installer ISO and Virtio-Win-ISO) to be able to install to 
>> Virtio-(SCSI)-Disks.
>> 
>> In Ovirt 4.3.4 it is not possible to attach 2 CD-ROM's to a VM. So we have 
>> to use Floppy Images (virtio-win-*.vfd) attached to install drivers within 
>> Installer.
>> 
>> We need to use "Run Once" to attach flopppy disks. There are only *.vfd 
>> selectable which are located on ISO-Storage.Domain, which will be deprecated 
>> now or then. 
>> 
>> -> We won't be able to install Windows VM's from unmodified ISO 
>> Installer-CD's without ISO Storage Domain or making *.vfd Files selectable 
>> via "Run Once" 
>> 
>> When will that be available... ?
>> 
>> Bye
>> 
>> -- 
>> 
>> 
>> 
>> Ralf Schenk
>> fon +49 (0) 24 05 / 40 83 70
>> fax +49 (0) 24 05 / 40 83 759
>> mail r...@databay.de 
>>  
>> Databay AG
>> Jens-Otto-Krag-Straße 11
>> D-52146 Würselen
>> www.databay.de 
>> 
>> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
>> Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. 
>> Philipp Hermanns
>> Aufsichtsratsvorsitzender: Wilhelm Dohmen
>> ___
>> 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/3G5BEWATSBZCUKLPS5ZNOAFDHIVNAYQV/
>>  
>> 
> ___
> 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/HLWL43FJ2D5WYXUCVNCBCMI34U3TTXQA/

___
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/6T2O6XMNSRR4VGITHY4CZYTNHAS5DKRF/

[ovirt-users] Re: Either allow 2 CD-ROM's or selectable *.vfd Floppy Images from Storage via Run Once other than from deprcated ISO-Storage

2019-08-13 Thread Vinícius Ferrão

Ralf, you can change CD on the Load Drivers section.

Change for the oVirt Tools Disc, load the drivers and then change back to 
Windows.

It’s a bad workflow, I know. But it’s how I’m doing here. I agree that the 
Windows Tools is not really friendly with oVirt.

Sent from my iPhone

On 12 Aug 2019, at 08:03, Ralf Schenk mailto:r...@databay.de>> 
wrote:


Hello,

when Installing Windows VM's on Ovirt we need either 2 CD-ROM's attached as ISO 
Files (Installer ISO and Virtio-Win-ISO) to be able to install to 
Virtio-(SCSI)-Disks.

In Ovirt 4.3.4 it is not possible to attach 2 CD-ROM's to a VM. So we have to 
use Floppy Images (virtio-win-*.vfd) attached to install drivers within 
Installer.

We need to use "Run Once" to attach flopppy disks. There are only *.vfd 
selectable which are located on ISO-Storage.Domain, which will be deprecated 
now or then.

-> We won't be able to install Windows VM's from unmodified ISO Installer-CD's 
without ISO Storage Domain or making *.vfd Files selectable via "Run Once"

When will that be available... ?

Bye

--



Ralf Schenk
fon +49 (0) 24 05 / 40 83 70
fax +49 (0) 24 05 / 40 83 759
mail r...@databay.de

Databay AG
Jens-Otto-Krag-Straße 11
D-52146 Würselen
www.databay.de

Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp 
Hermanns
Aufsichtsratsvorsitzender: Wilhelm Dohmen

___
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/3G5BEWATSBZCUKLPS5ZNOAFDHIVNAYQV/
___
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/HLWL43FJ2D5WYXUCVNCBCMI34U3TTXQA/

[ovirt-users] Re: Problem with cloud-init (metrics install)

2019-08-13 Thread Dominik Holler

On Mon, Aug 12, 2019 at 3:25 PM Chris Adams  wrote:

> I'm using ovirt-engine 4.3.5.5-1.el7.  I installed the Metrics Store
> using this guide and its CentOS settings:
>
>
> https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_Store.html
>
> I tried to set a static IP on the created master0 VM per the guide by
> setting the network settings under the Initial Run tab of the VM
> settings, but they are not applied.  If I start the VM with Run Once and
> the network settings, they are applied, but if I shut it down and go
> back to a regular run, the VM reverts back to DHCP.
>
>
>From my understanding cloud-init oVirt should only provide the data source
for cloud-init during the initial run.
But the cloud-init data should be provided during the initial run if the VM
is started by "Run" or "Run once".


> Once upon a time, Dominik Holler  said:
> > On Sun, Aug 11, 2019 at 3:42 PM Liran Rotenberg 
> wrote:
> >
> > > Hi again,
> > > Adding +Dominik Holler
> > >
> >
> > Thanks for the heads up.
> >
> >
> > > If you deployed the static configuration to the VM using cloud-init
> > > you might be hitting this bug:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1593010
> > >
> > > Let me know if this is the case. If not, please elaborate on the steps
> > > you did to this VM.
> > >
> > >
> > Which version of ovirt-engine do you use?
> > Which cloud image do you use?
> > Which network setting is not applied as you expect?
> >
> >
> > > Regards,
> > > Liran.
> > >
> > >
> > >
> > > On Thu, Aug 8, 2019 at 8:32 PM Chris Adams  wrote:
> > > >
> > > > How do you keep it from reverting back to DHCP on the next reboot?
> > > >
> > > > Once upon a time, Jayme  said:
> > > > > I found this a bit confusing myself.  I ended up having to do it
> > > manually
> > > > > by logging in to the VM and changing the IP afterward.
> > > > >
> > > > > On Thu, Aug 8, 2019 at 11:21 AM Chris Adams 
> wrote:
> > > > >
> > > > > > I'm following this guide:
> > > > > >
> > > > > >
> > > > > >
> > >
> https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_Store.html
> > > > > >
> > > > > > Specifically, the step "Setup virtual machine static IP and Mac
> > > > > > address".  The deploy does a bunch of stuff automatically, so the
> > > first
> > > > > > opportunity I have to do anything is after the VM is already
> booted.
> > > > > >
> > > > > > It seems that having a DHCP server, with matching
> reverse/forward DNS
> > > > > > entries for each IP, is a requirement, and that there's not a
> way to
> > > set
> > > > > > the metrics store VM to a static IP (despite having to have a DNS
> > > entry
> > > > > > pointing to an IP).
> > > > > >
> > > > > > Once upon a time, Liran Rotenberg  said:
> > > > > > > Hi Chris,
> > > > > > > Run Once option is different from normal run.
> > > > > > > For cloud-init you shall need the pre-requirement:
> > > > > > > A sealed VM, for example if you wish to create a template:
> > > > > > >
> > > > > >
> > >
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/virtual_machine_management_guide/chap-templates#Sealing_Virtual_Machines_in_Preparation_for_Deployment_as_Templates
> > > > > > > Cloud-init service should be installed and enabled on the VM
> (make
> > > > > > > sure before sealing the VM).
> > > > > > > Run will consume the cloud-init configuration only if it is the
> > > VM's
> > > > > > first run.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Liran.
> > > > > > >
> > > > > > > On Thu, Aug 8, 2019 at 4:07 PM Chris Adams 
> > > wrote:
> > > > > > > >
> > > > > > > > I am trying to set up the oVirt Metrics Store, which uses
> > > cloud-init
> > > > > > for
> > > > > > > > network settings, so I set the info under the "Initial Run"
> tab.
> > > > > > > > However, it doesn't seem to actually apply the network
> settings
> > > unless
> > > > > > I
> > > > > > > > "run once" and enable clout-init there.
> > > > > > > >
> > > > > > > > I haven't used cloud-init before (been on my to-do list to
> check
> > > out) -
> > > > > > > > am I missing something?
> > > > > > > >
> > > > > > > > --
> > > > > > > > Chris Adams 
> > > > > > > > ___
> > > > > > > > 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/UKBKKLQQBFDNSVEIKETOD5GQPVVX2LBT/
> > > > > > > ___
> > > > > > > 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:
> > > > > >

[ovirt-users] Re: Inconsistent metadata on VM's disks

2019-08-13 Thread Strahil

I see only inconsistent VG errors...
Most probably it is CentOS specific.

Best Regards,
Strahil NikolovOn Aug 13, 2019 12:03, Nardus Geldenhuys  
wrote:
>
> Hi There
>
> Hope you are all well. We got this weird issue at the moment. Let me explain.
>
> We are on ovirt 4.3.5. We use Centos 7.6 and when we do an update on the VM's 
> the VM's can not boot into multi user mode. It complains that the root mount 
> can't be found. When you boot using ISO and rescue mode you can see the 
> disks. When you chroot into the VM and run pvscan twice your VM can be 
> rebooted and it is fixed. We don't know if this is Centos based or maybe 
> something on ovirt. Screenshots below. Any help would be appreciated.
>
>
>
>
>
___
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/3HUCTLZGSKB4AUQNYLPKU2FUB2ZE4HOQ/

[ovirt-users] Re: oVirt 4.3.5 potential issue with NFS storage

[ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

[ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

[ovirt-users] ovirt node install

[ovirt-users] Re: Either allow 2 CD-ROM's or selectable *.vfd Floppy Images from Storage via Run Once other than from deprcated ISO-Storage

[ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

[ovirt-users] Disk Allocation policy changes after a snapshot

[ovirt-users] Re: Either allow 2 CD-ROM's or selectable *.vfd Floppy Images from Storage via Run Once other than from deprcated ISO-Storage

[ovirt-users] Re: Either allow 2 CD-ROM's or selectable *.vfd Floppy Images from Storage via Run Once other than from deprcated ISO-Storage

[ovirt-users] Re: Problem with cloud-init (metrics install)

[ovirt-users] Re: Inconsistent metadata on VM's disks

11 matches

Site Navigation

Mail list logo

Footer information