[ovirt-users] Cannot use virt-viewer to open VM console

[Terry hey]

Dear all,

I would like to ask which version of virt-viewer are you using?
I downloaded virt-viewer 6.0.msi and installed.
But i could not open VM console( i have set the graphic protocol is SPICE).
It shows the following error.

"At least Remote Viewer version 2.0-160 is required to setup this
connection, see
http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources
for details"

Also, i can i verify the version of virt-viewer that i have installed?

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

[ovirt-users] Auto-restart VM from Linux Shell

[Andrei Verovski]

Hi !

I have stubborn VM which time to time freezes, and watchdog for whatever
reason don't restart it.

Basically I would like to combine these 3 command into one script.

ovirt-shell -l https://node00.mydomain.com.lv/ovirt-engine/api
--ca-file="/etc/pki/ovirt-engine/ca.pem" -u "admin@internal" --password
"secret"

action vm MyVM stop
action vm MyVM start

Now I have problems.
1) Option --password "secret" is not recognized anymore in oVirt Shell 4.2.
2) What is the proper syntax to connect & run certain command in oVirt
Shell 4.2? Something like:

ovirt-shell -l https://node00.mydomain.com.lv/ovirt-engine/api
--ca-file="/etc/pki/ovirt-engine/ca.pem" -u "admin@internal" --password
"secret" && action vm MyVM stop

Thanks in advance
Andrei
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM guest agent

[Nir Soffer]

On Mon, Mar 12, 2018 at 12:57 AM Nicolas Vaye 
wrote:

> Hello,
>
> i have installed one oVirt platform with 2 node and 1 HE version 4.2.1.7-1
>
> It seem to work fine, but i would like more information on the guest agent.
> For the HE, the guest agent seem to be OK, on this vm i 've spotted that
> the ovirt-guest-agent and qemu-guest-agent are installed.
>
> I have 2 VM, 1 debian 9 and 1 RHEL 6.5. I've tried to install the same
> service on each VM, but the result is the same :
> no info about IP, fqdn, or app installed for these vm, and there is a
> orange ! for each vm on the web ui (indicate that i need to install latest
> guest agent) .
>
> I have tried different test with spice-vdagent, or ovirt-guest-agent or
> qemu-guest-agent but no way.
>
> ovirt-guest-agent doesn't start on debian 9 and RHEL 6.5 :
> MainThread::INFO::2018-03-11
> 22:46:02,984::ovirt-guest-agent::59::root::Starting oVirt guest
> agentMainThread::ERROR::2018-03-11
> 22:46:02,986::ovirt-guest-agent::141::root::Unhandled exception in oVirt
> guest agent!Traceback (most recent call last):  File
> "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 135, in 
>   agent.run(daemon, pidfile)  File
> "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 65, in run
> self.agent = LinuxVdsAgent(config)  File
> "/usr/share/ovirt-guest-agent/GuestAgentLinux2.py", line 472, in __init__
>   AgentLogicBase.__init__(self, config)  File
> "/usr/share/ovirt-guest-agent/OVirtAgentLogic.py", line 188, in __init__
> self.vio = VirtIoChannel(config.get("virtio", "device"))  File
> "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 153, in __init__
> self._stream = VirtIoStream(vport_name)  File
> "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 134, in __init__
> self._vport = os.open(vport_name, os.O_RDWR)OSError: [Errno 2] No such file
> or directory: '/dev/virtio-ports/com.redhat.rhevm.vdsm'
>
>
> Can i have help for this problem ?
>

I hope that Tomáš can help.

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

[ovirt-users] VM guest agent

[Nicolas Vaye]

Hello,

i have installed one oVirt platform with 2 node and 1 HE version 4.2.1.7-1

It seem to work fine, but i would like more information on the guest agent.
For the HE, the guest agent seem to be OK, on this vm i 've spotted that the 
ovirt-guest-agent and qemu-guest-agent are installed.

I have 2 VM, 1 debian 9 and 1 RHEL 6.5. I've tried to install the same service 
on each VM, but the result is the same :
no info about IP, fqdn, or app installed for these vm, and there is a orange ! 
for each vm on the web ui (indicate that i need to install latest guest agent) .

I have tried different test with spice-vdagent, or ovirt-guest-agent or 
qemu-guest-agent but no way.

ovirt-guest-agent doesn't start on debian 9 and RHEL 6.5 :
MainThread::INFO::2018-03-11 
22:46:02,984::ovirt-guest-agent::59::root::Starting oVirt guest 
agentMainThread::ERROR::2018-03-11 
22:46:02,986::ovirt-guest-agent::141::root::Unhandled exception in oVirt guest 
agent!Traceback (most recent call last):  File 
"/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 135, in 
agent.run(daemon, pidfile)  File 
"/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 65, in run
self.agent = LinuxVdsAgent(config)  File 
"/usr/share/ovirt-guest-agent/GuestAgentLinux2.py", line 472, in __init__
AgentLogicBase.__init__(self, config)  File 
"/usr/share/ovirt-guest-agent/OVirtAgentLogic.py", line 188, in __init__
self.vio = VirtIoChannel(config.get("virtio", "device"))  File 
"/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 153, in __init__
self._stream = VirtIoStream(vport_name)  File 
"/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 134, in __init__
self._vport = os.open(vport_name, os.O_RDWR)OSError: [Errno 2] No such file or 
directory: '/dev/virtio-ports/com.redhat.rhevm.vdsm'


Can i have help for this problem ?

Thanks.

Nicolas VAYE
DSI - Nouméa
NEW CALEDONIA
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] storage domain ovirt-image-repository doesn't work

[Nicolas Vaye]

Hello,

i have installed one oVirt platform with 2 node and 1 HE version 4.2.1.7-1

It seem to work fine, but i have issue with the ovirt-image-repository.

Impossible to get the list of available images for this domain :
[cid:1520807274.29800.1.camel@province-sud.nc]

My cluster is on a private network, so there is a proxy to get internet access.
I have tried with a specific proxy configuration on each node 
(https://www.server-world.info/en/note?os=CentOS_7=squid=2)
so it's a success with yum update, wget or curl with 
http://glance.ovirt.org:9292/, but nothing in the webui for the 
ovirt-image-repository domain.

I have tried another test with a transparent proxy and the result is the same :
success with yum update, wget or curl with http://glance.ovirt.org:9292/, but 
nothing in the webui for the ovirt-image-repository domain.


I don't know where is the specific log for this technical part.

Can i have help for this issue.

Thanks.

Nicolas VAYE
DSI - Nouméa
NEW CALEDONIA
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cannot activate storage domain

[Bruckner, Simone]

Shani,

  all storage domains are FC.

In the meantime I could track it down to corrupt vg metadata. I filed a bug 
(https://bugzilla.redhat.com/show_bug.cgi?id=1553133).

I ran vgcfgrestore, copied the VMs I could recover and recreated the LUNs. 
Would there have been another way of recovering?

All the best,
Simone

Von: Shani Leviim [mailto:slev...@redhat.com]
Gesendet: Sonntag, 11. März 2018 14:09
An: Bruckner, Simone 
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi Simone,
Sorry for the delay replying you.

Does the second storage domain you've mentioned is also an FC?
If so, please execute the following command  /usr/libexec/vdsm/fc-scan -v
on one host of each inactive storage domain and share the results you've got.


Regards,
Shani Leviim

On Thu, Mar 8, 2018 at 9:42 AM, Bruckner, Simone 
> wrote:
Hi Shani,

  today I again lost access to a storage domain. So currently I have two 
storage domains that we cannot activate any more.

I uploaded the logfiles to our Cloud Service: [ZIP Archive]  
logfiles.tar.gz
I lost access today, March 8th 2018 around 0.55am CET
I tried to actived the storage domain around 6.40am CET

Please let me know if there is anything I can do to get this addressed.

Thank you very much,
Simone



Von: users-boun...@ovirt.org 
[users-boun...@ovirt.org]" im Auftrag von 
"Bruckner, Simone 
[simone.bruck...@fabasoft.com]
Gesendet: Dienstag, 06. März 2018 10:19
An: Shani Leviim
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi Shani,

  please find the logs attached.

Thank you,
Simone

Von: Shani Leviim [mailto:slev...@redhat.com]
Gesendet: Dienstag, 6. März 2018 09:48
An: Bruckner, Simone 
>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi Simone,
Can you please share your vdsm and engine logs?

Regards,
Shani Leviim

On Tue, Mar 6, 2018 at 7:34 AM, Bruckner, Simone 
>>
 wrote:
Hello, I apologize for bringing this one up again, but does anybody know if 
there is a change to recover a storage domain, that cannot be activated?

Thank you,
Simone

Von: 
users-boun...@ovirt.org>
 
[mailto:users-boun...@ovirt.org>]
 Im Auftrag von Bruckner, Simone
Gesendet: Freitag, 2. März 2018 17:03

An: 
users@ovirt.org>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi all,

  I managed to get the inactive storage domain to maintenance by stopping all 
running VMs that were using it, but I am still not able to activate it.

Trying to activate results in the following events:

For each host:
VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And finally:
VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)

Is there anything I can do to recover this storage domain?

Thank you and all the best,
Simone

Von: 
users-boun...@ovirt.org>
 [mailto:users-boun...@ovirt.org] Im Auftrag 
von Bruckner, Simone
Gesendet: Donnerstag, 1. März 2018 17:57
An: 
users@ovirt.org>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi,

  we are still struggling getting a storage domain online again. We tried to 
put the storage domain in maintenance mode, that led to “Failed to update OVF 
disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't updated on those OVF 
stores”.

Trying again with ignoring OVF update failures put the storage domain in 
“preparing for maintenance”. We see the following message on all hosts: “Error 
releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 
(monitor:578)”.

Querying the storage domain using vdsm-client on the SPM resulted in
# vdsm-client StorageDomain getInfo 
"storagedomainID"="b83c159c-4ad6-4613-ba16-bab95ccd10c0"
vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID': 
'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
(code=358, message=Storage domain does not exist: 

Re: [ovirt-users] Cannot activate storage domain

[Shani Leviim]

Hi Simone,

Sorry for the delay replying you.

Does the second storage domain you've mentioned is also an FC?

If so, please execute the following command  /usr/libexec/vdsm/fc-scan -v
on one host of each inactive storage domain and share the results you've
got.




*Regards,*

*Shani Leviim*

On Thu, Mar 8, 2018 at 9:42 AM, Bruckner, Simone <
simone.bruck...@fabasoft.com> wrote:

> Hi Shani,
>
>   today I again lost access to a storage domain. So currently I have two
> storage domains that we cannot activate any more.
>
> I uploaded the logfiles to our Cloud Service: [ZIP Archive]
> logfiles.tar.gz 1zf8q45o1e9l8334agryb2crdd>
> I lost access today, March 8th 2018 around 0.55am CET
> I tried to actived the storage domain around 6.40am CET
>
> Please let me know if there is anything I can do to get this addressed.
>
> Thank you very much,
> Simone
>
>
> 
> Von: users-boun...@ovirt.org [users-boun...@ovirt.org]" im Auftrag von
> "Bruckner, Simone [simone.bruck...@fabasoft.com]
> Gesendet: Dienstag, 06. März 2018 10:19
> An: Shani Leviim
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Cannot activate storage domain
>
> Hi Shani,
>
>   please find the logs attached.
>
> Thank you,
> Simone
>
> Von: Shani Leviim [mailto:slev...@redhat.com]
> Gesendet: Dienstag, 6. März 2018 09:48
> An: Bruckner, Simone 
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Cannot activate storage domain
>
> Hi Simone,
> Can you please share your vdsm and engine logs?
>
> Regards,
> Shani Leviim
>
> On Tue, Mar 6, 2018 at 7:34 AM, Bruckner, Simone <
> simone.bruck...@fabasoft.com> wrote:
> Hello, I apologize for bringing this one up again, but does anybody know
> if there is a change to recover a storage domain, that cannot be activated?
>
> Thank you,
> Simone
>
> Von: users-boun...@ovirt.org [mailto:
> users-boun...@ovirt.org] Im Auftrag von
> Bruckner, Simone
> Gesendet: Freitag, 2. März 2018 17:03
>
> An: users@ovirt.org
> Betreff: Re: [ovirt-users] Cannot activate storage domain
>
> Hi all,
>
>   I managed to get the inactive storage domain to maintenance by stopping
> all running VMs that were using it, but I am still not able to activate it.
>
> Trying to activate results in the following events:
>
> For each host:
> VDSM  command GetVGInfoVDS failed: Volume Group does not exist:
> (u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)
>
> And finally:
> VDSM command ActivateStorageDomainVDS failed: Storage domain does not
> exist: (u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
>
> Is there anything I can do to recover this storage domain?
>
> Thank you and all the best,
> Simone
>
> Von: users-boun...@ovirt.org [mailto:
> users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
> Gesendet: Donnerstag, 1. März 2018 17:57
> An: users@ovirt.org
> Betreff: Re: [ovirt-users] Cannot activate storage domain
>
> Hi,
>
>   we are still struggling getting a storage domain online again. We tried
> to put the storage domain in maintenance mode, that led to “Failed to
> update OVF disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't
> updated on those OVF stores”.
>
> Trying again with ignoring OVF update failures put the storage domain in
> “preparing for maintenance”. We see the following message on all hosts:
> “Error releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0
> (monitor:578)”.
>
> Querying the storage domain using vdsm-client on the SPM resulted in
> # vdsm-client StorageDomain getInfo "storagedomainID"="b83c159c-
> 4ad6-4613-ba16-bab95ccd10c0"
> vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID':
> 'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
> (code=358, message=Storage domain does not exist:
> (u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',))
>
> Any ideas?
>
> Thank you and all the best,
> Simone
>
> Von: users-boun...@ovirt.org [mailto:
> users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
> Gesendet: Mittwoch, 28. Februar 2018 15:52
> An: users@ovirt.org
> Betreff: [ovirt-users] Cannot activate storage domain
>
> Hi all,
>
>   we run a small oVirt installation that we also use for automated testing
> (automatically creating, dropping vms).
>
> We got an inactive FC storage domain that we cannot activate any more. We
> see several events at that time starting with:
>
> VM perftest-c17 is down with error. Exit message: Unable to get volume
> size for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 volume
> 686376c1-4be1-44c3-89a3-0a8addc8fdf2.
>
> Trying to activate the strorage domain results in the following alert
> event for each host:
>
> VDSM  command GetVGInfoVDS failed: Volume Group does not exist:
> (u'vg_uuid: 

Re: [ovirt-users] Faulty multipath only cleared with VDSM restart

[Fred Rolland]

The multipath report does not have any effects on stability/performance.
It is used for creating events to the user in the engine, in order to
detect earlier issues in their storage. [1]

In your case, you would have an wrong alarm in the Engine that would not be
cleared until next Vdsm restart.


[1]
https://ovirt.org/develop/release-management/features/storage/multipath-events/#event-reporting

On Sun, Mar 11, 2018 at 2:23 PM, Bruckner, Simone <
simone.bruck...@fabasoft.com> wrote:

> Hi Fred,
>
>
>
>   thank you for the explanation. I restarted VDSM and will monitor the
> behaviour.
>
>
>
> Does that faulty multipath report have any side effects on stability and
> performance?
>
>
>
> All the best,
>
> Oliver
>
>
>
> *Von:* Fred Rolland [mailto:froll...@redhat.com]
> *Gesendet:* Sonntag, 11. März 2018 11:23
> *An:* Bruckner, Simone 
> *Cc:* users@ovirt.org
> *Betreff:* Re: [ovirt-users] Faulty multipath only cleared with VDSM
> restart
>
>
>
> Hi Simone,
>
> The multipath health is built on VDSM start from the current multipath
> state, and after that it is maintained based on events sent by udev.
>
> You can read about the implementation details in [1].
>
> It seems that in your scenario, either udev did not sent the needed
> clearing events or that Vdsm mishandled them.
>
> Therefore only restart of the Vdsm will clear the report.
>
> In order to be able to debug the issue, we will need Vdsm logs with debug
> level (on storage log) when the issue is happening.
>
>
>
> Thanks,
>
> Fred
>
>
> [1] https://ovirt.org/develop/release-management/features/
> storage/multipath-events/
>
>
>
> On Fri, Mar 9, 2018 at 1:07 PM, Bruckner, Simone <
> simone.bruck...@fabasoft.com> wrote:
>
> Hi,
>
>
>
>   after rebooting SAN switches we see faulty multipath entries in VDSM.
>
>
>
> Running vdsm-client Host getStats shows multipathHealth entries
>
>
>
> "multipathHealth": {
>
>   "3600601603cc04500a2f9cd597080db0e": {
>
> "valid_paths": 2,
>
> "failed_paths": [
>
>   "sdcl",
>
>   "sdde"
>
> ]
>
>   },
>
>   …
>
>
>
> Running multipath –ll does not show any errors.
>
>
>
> After restarting VSDM, the multipathHealth entires from vdsm-client are
> empty again.
>
>
>
> Is the a way to clear those multipathHealth entires without restarting
> VDSM?
>
>
>
> Thank you and all the best,
>
> Simone
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Faulty multipath only cleared with VDSM restart

[Bruckner, Simone]

Hi Fred,

  thank you for the explanation. I restarted VDSM and will monitor the 
behaviour.

Does that faulty multipath report have any side effects on stability and 
performance?

All the best,
Oliver

Von: Fred Rolland [mailto:froll...@redhat.com]
Gesendet: Sonntag, 11. März 2018 11:23
An: Bruckner, Simone 
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Faulty multipath only cleared with VDSM restart

Hi Simone,
The multipath health is built on VDSM start from the current multipath state, 
and after that it is maintained based on events sent by udev.
You can read about the implementation details in [1].
It seems that in your scenario, either udev did not sent the needed clearing 
events or that Vdsm mishandled them.
Therefore only restart of the Vdsm will clear the report.
In order to be able to debug the issue, we will need Vdsm logs with debug level 
(on storage log) when the issue is happening.

Thanks,
Fred

[1] 
https://ovirt.org/develop/release-management/features/storage/multipath-events/

On Fri, Mar 9, 2018 at 1:07 PM, Bruckner, Simone 
> wrote:
Hi,

  after rebooting SAN switches we see faulty multipath entries in VDSM.

Running vdsm-client Host getStats shows multipathHealth entries

"multipathHealth": {
  "3600601603cc04500a2f9cd597080db0e": {
"valid_paths": 2,
"failed_paths": [
  "sdcl",
  "sdde"
]
  },
  …

Running multipath –ll does not show any errors.

After restarting VSDM, the multipathHealth entires from vdsm-client are empty 
again.

Is the a way to clear those multipathHealth entires without restarting VDSM?

Thank you and all the best,
Simone


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

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

Re: [ovirt-users] Ghost Snapshot Disk

[Shani Leviim]

Hi Enrico,

Can you please send your question on a new different mail to users' list?
(So we won't mix up the answers due to different ovirt-engine's versions).

Thanks for cooperation.


*Regards,*

*Shani Leviim*

On Thu, Mar 8, 2018 at 6:08 PM, Enrico  wrote:

> Hi All,
> I've a similar question , I can't remove a snapshot. oVirt version is the
> last stable 4.2.1.7
> with engine running in non hosted mode. Before remove snapshot  I've
> shutdown vm.
> These are logs from engine:
>
> 2018-03-08 16:57:47,153+01 INFO  
> [org.ovirt.engine.core.bll.ProcessDownVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-40253) [711eba7d] Running command:
> ProcessDownVmCommand internal: true.
> 2018-03-08 16:57:55,589+01 INFO  [org.ovirt.engine.core.
> vdsbroker.monitoring.VmsStatisticsFetcher] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-71)
> [] Fetched 8 VMs from VDS '85bbf811-1069-4e67-ba86-e50dec9f5da9'
> 2018-03-08 16:59:00,561+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.RemoveDiskSnapshotsCommand]
> (default task-31) [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] Lock Acquired to
> object 
> 'EngineLock:{exclusiveLocks='[281a869f-8541-49cf-894b-f583bd26083d=DISK]',
> sharedLocks=''}'
> 2018-03-08 16:59:00,599+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.RemoveDiskSnapshotsCommand]
> (EE-ManagedThreadFactory-engine-Thread-40284) 
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e]
> Running command: RemoveDiskSnapshotsCommand internal: false. Entities
> affected :  ID: 01f9b5f2-9e48-4c24-80e5-dca7f1d4d128 Type: VMAction group
> MANIPULATE_VM_SNAPSHOTS with role type USER
> 2018-03-08 16:59:00,613+01 INFO  [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engine-Thread-40284)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] EVENT_ID:
> USER_REMOVE_DISK_SNAPSHOT(373), Disk 'SOL_Disk1' from Snapshot(s) 'PHP
> 5.6.29' of VM 'SOL-DEV' deletion was initiated by admin@internal-authz.
> 2018-03-08 16:59:00,615+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.RemoveDiskSnapshotsCommand]
> (EE-ManagedThreadFactory-engine-Thread-40284) 
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e]
> Lock freed to object 'EngineLock:{exclusiveLocks='[
> 281a869f-8541-49cf-894b-f583bd26083d=DISK]', sharedLocks=''}'
> 2018-03-08 16:59:00,993+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.RemoveDiskSnapshotsCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] Starting child command 1 of 1,
> image '64e8f28d-6c00-41d8-9f60-26a87d51cb8c'
> 2018-03-08 16:59:01,026+01 INFO  [org.ovirt.engine.core.bll.snapshots.
> ColdMergeSnapshotSingleDiskCommand] 
> (EE-ManagedThreadFactory-commandCoordinator-Thread-7)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] Running command:
> ColdMergeSnapshotSingleDiskCommand internal: true. Entities affected :
> ID: ---- Type: Storage
> 2018-03-08 16:59:02,026+01 INFO  [org.ovirt.engine.core.bll.snapshots.
> ColdMergeSnapshotSingleDiskCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] Command
> 'ColdMergeSnapshotSingleDisk' id '2bbd81c3-9fa1-4e48-ab69-5588e1367539'
> executing step 'PREPARE_MERGE'
> 2018-03-08 16:59:02,048+01 INFO  [org.ovirt.engine.core.bll.
> storage.disk.image.PrepareMergeCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] Running command:
> PrepareMergeCommand internal: true. Entities affected :  ID:
> ---- Type: Storage
> 2018-03-08 16:59:02,049+01 INFO  [org.ovirt.engine.core.
> vdsbroker.irsbroker.PrepareMergeVDSCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] START, PrepareMergeVDSCommand(
> SPMColdMergeVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7',
> ignoreFailoverLimit='false'}), log id: 447f2b58
> 2018-03-08 16:59:02,178+01 INFO  [org.ovirt.engine.core.
> vdsbroker.irsbroker.PrepareMergeVDSCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] FINISH, PrepareMergeVDSCommand,
> log id: 447f2b58
> 2018-03-08 16:59:02,221+01 INFO  
> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] CommandAsyncTask::Adding
> CommandMultiAsyncTasks object for command 'b5983000-d637-47da-8aa2-
> fb8fec50b480'
> 2018-03-08 16:59:02,221+01 INFO  
> [org.ovirt.engine.core.bll.CommandMultiAsyncTasks]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [ceb64d67-ce9e-41a8-93dd-ffa512bfd18e] CommandMultiAsyncTasks::attachTask:
> Attaching task '0f762196-21ed-4b70-995d-729f3ed72425' to command
> 'b5983000-d637-47da-8aa2-fb8fec50b480'.
> 2018-03-08 16:59:02,235+01 INFO  
> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> 

Re: [ovirt-users] Faulty multipath only cleared with VDSM restart

[Fred Rolland]

Hi Simone,

The multipath health is built on VDSM start from the current multipath
state, and after that it is maintained based on events sent by udev.
You can read about the implementation details in [1].

It seems that in your scenario, either udev did not sent the needed
clearing events or that Vdsm mishandled them.
Therefore only restart of the Vdsm will clear the report.

In order to be able to debug the issue, we will need Vdsm logs with debug
level (on storage log) when the issue is happening.

Thanks,
Fred

[1]
https://ovirt.org/develop/release-management/features/storage/multipath-events/

On Fri, Mar 9, 2018 at 1:07 PM, Bruckner, Simone <
simone.bruck...@fabasoft.com> wrote:

> Hi,
>
>
>
>   after rebooting SAN switches we see faulty multipath entries in VDSM.
>
>
>
> Running vdsm-client Host getStats shows multipathHealth entries
>
>
>
> "multipathHealth": {
>
>   "3600601603cc04500a2f9cd597080db0e": {
>
> "valid_paths": 2,
>
> "failed_paths": [
>
>   "sdcl",
>
>   "sdde"
>
> ]
>
>   },
>
>   …
>
>
>
> Running multipath –ll does not show any errors.
>
>
>
> After restarting VSDM, the multipathHealth entires from vdsm-client are
> empty again.
>
>
>
> Is the a way to clear those multipathHealth entires without restarting
> VDSM?
>
>
>
> Thank you and all the best,
>
> Simone
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users