[ovirt-users] Update problem with one node in HC env. 4.1.5->4.1.6

[Jesper Andersson]

Hi, we have a HC (ovirt node) environment with 3 nodes, where 2 of them
updated from ovirt 4.1.5 to 4.1.6 just fine but one node fails the update.

I talked to sbonazzo on IRC and was asked to mail the users@ovirt.org
with an sosreport.

The sosreport can be found here:

https://ufile.io/47jhs


Best regards

Jesper

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

[ovirt-users] Vdsm Fail after update

[carl langlois]

Hi,

I have just update my Centos 7 and now vdsm is not starting:

i got this error :

Job vdsmd.service/start failed with result 'dependency'.


and in the libvirtd error also :


Oct 12 10:15:32 ovhost5 libvirtd[1434]: 2017-10-12 15:15:32.959+: 1434:
error : virNetSocketReadWire:1808 : End of file while reading data:
Input/output error
Oct 12 10:15:33 ovhost5 libvirtd[1434]: 2017-10-12 15:15:33.160+: 1492:
error : virNetSASLSessionListMechanisms:390 : internal error: cannot list
SASL mechanisms -4 (SASL(-4): no mechanism available: Internal Error -4 in
server.c near line 1757)
Oct 12 10:15:33 ovhost5 libvirtd[1434]: 2017-10-12 15:15:33.160+: 1492:
error : remoteDispatchAuthSaslInit:3411 : authentication failed:
authentication failed
Oct 12 10:15:33 ovhost5 libvirtd[1434]: 2017-10-12 15:15:33.160+: 1434:
error : virNetSocketReadWire:1808 : End of file while reading data:
Input/output error
Oct 12 10:15:33 ovhost5 libvirtd[1434]: 2017-10-12 15:15:33.361+: 1493:
error : virNetSASLSessionListMechanisms:390 : internal error: cannot list
SASL mechanisms -4 (SASL(-4): no mechanism available: Internal Error -4 in
server.c near line 1757)

any help would apreciated. Everything was working perfectly before the
update.


current version
CentOS Linux release 7.4.1708 (Core)
ovirt-release40

Regards.

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

Re: [ovirt-users] How to change network card configuration under bridge on host?

[Derek Atkins]

Hi,

Derek Atkins  writes:

> How do I convince ovirt to stop overwriting those files?  Or how do I
> tell ovirt about the new configuration?

For the record, the answer was that I needed to change the VDSM
persistence files and then it swapped over to the new devices.  It took
me a few hours to both track this down and get the files formatted
correctly.

> Thanks,
>
> -derek

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt 4.0 and EL 7.4

[Jorick Astrego]

Fixed it by downgrading libvirt, I had the libvirt latest repo 
"http://mirror.centos.org/centos-7/7.3.1611/virt/x86_64/libvirt-latest/; 
configured on our Katello

Working packages:

libvirt-daemon-driver-network-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-driver-qemu-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-driver-lxc-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-driver-interface-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-driver-secret-2.0.0-10.el7_3.9.x86_64
libvirt-lock-sanlock-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-kvm-2.0.0-10.el7_3.9.x86_64
libvirt-client-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-driver-storage-2.0.0-10.el7_3.9.x86_64
libvirt-daemon-config-network-2.0.0-10.el7_3.9.x86_64
libvirt-2.0.0-10.el7_3.9.x86_64
libvirt-python-2.0.0-2.el7.x86_64

On 10/10/2017 07:41 PM, Jorick Astrego wrote:
>
> Hi,
>
> I've redeployed a node with 7.3 to fix this issue but got the same 
> errors with ovirt 4.0.
>
> MainThread::DEBUG::2017-10-10
> 18:30:30,945::upgrade::90::upgrade::(apply_upgrade) Running
> upgrade upgrade-unified-persistence
> MainThread::DEBUG::2017-10-10
> 18:30:30,951::libvirtconnection::160::root::(get) trying to
> connect libvirt
> MainThread::ERROR::2017-10-10
> 18:30:41,125::upgrade::94::upgrade::(apply_upgrade) Failed to run
> upgrade-unified-persistence
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/tool/upgrade.py",
> line 92, in apply_upgrade
> upgrade.run(ns, args)
>   File
> "/usr/lib/python2.7/site-packages/vdsm/tool/unified_persistence.py",
> line 195, in run
> run()
>   File
> "/usr/lib/python2.7/site-packages/vdsm/tool/unified_persistence.py",
> line 46, in run
> networks, bondings = _getNetInfo()
>   File
> "/usr/lib/python2.7/site-packages/vdsm/tool/unified_persistence.py",
> line 132, in _getNetInfo
> netinfo = NetInfo(netswitch.netinfo())
>   File
> "/usr/lib/python2.7/site-packages/vdsm/network/netswitch.py", line
> 298, in netinfo
> _netinfo = netinfo_get(compatibility=compatibility)
>   File
> "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py",
> line 109, in get
> return _get(vdsmnets)
>   File
> "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py",
> line 70, in _get
> libvirt_nets = libvirt.networks()
>   File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py",
> line 113, in networks
> conn = libvirtconnection.get()
>   File
> "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line
> 163, in get
> password)
>   File
> "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line
> 99, in open_connection
> return utils.retry(libvirtOpen, timeout=10, sleep=0.2)
>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 547,
> in retry
> return func()
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 105,
> in openAuth
> if ret is None:raise libvirtError('virConnectOpenAuth() failed')
> libvirtError: authentication failed: authentication failed
>
>
> Oct 10 19:35:55 host1 sasldblistusers2: _sasldb_getkeyhandle has
> failed
>
> Oct 10 19:36:20 host1 libvirtd: 2017-10-10 17:36:20.002+:
> 13660: error : virNetSASLSessionListMechanisms:390 : internal
> error: cannot list SASL mechanisms -4 (SASL(-4): no mechanism
> available: Internal Error -4 in server.c near line 1757)
> Oct 10 19:36:20 host1 libvirtd: 2017-10-10 17:36:20.002+:
> 13660: error : remoteDispatchAuthSaslInit:3411 : authentication
> failed: authentication failed
> Oct 10 19:36:20 host1 libvirtd: 2017-10-10 17:36:20.002+:
> 13650: error : virNetSocketReadWire:1808 : End of file while
> reading data: Input/output error
> Oct 10 19:36:20 host1 vdsm-tool: libvirt: XML-RPC error :
> authentication failed: authentication failed
> Oct 10 19:36:20 host1 systemd: vdsm-network.service: control
> process exited, code=exited status=1
> Oct 10 19:36:20 host1 systemd: Failed to start Virtual Desktop
> Server Manager network restoration.
> Oct 10 19:36:20 host1 systemd: Dependency failed for Virtual
> Desktop Server Manager.
> Oct 10 19:36:20 host1 systemd: Dependency failed for MOM instance
> configured for VDSM purposes.
> Oct 10 19:36:20 host1 systemd: Job mom-vdsm.service/start failed
> with result 'dependency'.
> Oct 10 19:36:20 host1 systemd: Job vdsmd.service/start failed with
> result 'dependency'.
> Oct 10 19:36:20 host1 systemd: Unit vdsm-network.service entered
> failed state.
>   

Re: [ovirt-users] Issues with Windows 7 VM

[Tomas Jelinek]

could you please share the engine logs and the vdsm, libvirt and qemu logs
from the host where it tried and failed to start?

On Thu, Oct 5, 2017 at 3:29 PM, Marc Turner  wrote:

> Hello,
>
> I'm a Systems Administrator at Wolfram Research, and we've been having an
> issue with a Windows 7 x64 VM.  This is a new VM with a newly created
> Cinder VM image attached to it, which was working without issue last week.
> Earlier today I performed a Windows update and shutdown the VM.  When
> trying to start it back up, it does nothing but fail with the message
> "Failed to start VM on host.  We have several VM hosts set up, so it will
> bounce around between a few of them, failing each time before giving up
> entirely.
>
> Myself and another SysAdmin have looked through the logs and have not been
> able to find any reason as to why this VM won't start.  No other VM's are
> having problems, and Cinder is working correctly.  If you would have any
> idea as to why this is happening, or where we could look to figure out what
> may be going on, it would be much appreciated.
>
> Thank you,
>
> Marc Turner
> Systems Administrator
> Wolfram Research
> ___
> 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