3.5 install issues: failed to setup ovirtmgmt
--Sig_/UCS9Qt+.3XGZ4pTqVuU5k2x Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I'm on my 4th attempt to get a 3.5 hosted-engine set up on CentOS 6.5. I seem to hit a different snag each time. The first 3 were with the ovirtmgmt bridge on a tagged VLAN, so I decided to go back to an untagged interface and see if I had better luck. But this install failed even earlier, when creating the management bridge: 2014-10-25 12:37:24 INFO otopi.plugins.ovirt_hosted_engine_setup.network.br= idge bridge._misc:198 Configuring the management bridge 2014-10-25 12:37:25 DEBUG otopi.context context._executeMethod:152 method e= xception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _e= xecuteMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hoste= d-engine-setup/network/bridge.py", line 207, in _misc _setupNetworks(conn, networks, {}, {'connectivityCheck': False}) File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hoste= d-engine-setup/network/bridge.py", line 225, in _setupNetworks 'message: "%s"' % (networks, code, message)) RuntimeError: Failed to setup networks {'ovirtmgmt': {'nic': 'eth0', 'netma= sk': '255.255.255.0', 'bootproto': 'none', 'ipaddr': '10.69.79.31'}}. Error= code: "16" message: "Unexpected exception" 2014-10-25 12:37:25 ERROR otopi.context context._executeMethod:161 Failed t= o execute stage 'Misc configuration': Failed to setup networks {'ovirtmgmt'= : {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', 'ipaddr'= : '10.69.79.31'}}. Error code: "16" message: "Unexpected exception" 2014-10-25 12:37:25 DEBUG otopi.transaction transaction.abort:131 aborting = 'File transaction for '/etc/ovirt-hosted-engine/firewalld/hosted-console.xm= l'' 2014-10-25 12:37:25 DEBUG otopi.transaction transaction.abort:131 aborting = 'File transaction for '/etc/ovirt-hosted-engine/iptables.example'' 2014-10-25 12:37:25 DEBUG otopi.transaction transaction.abort:131 aborting = 'File transaction for '/etc/sysconfig/iptables'' 2014-10-25 12:37:25 DEBUG otopi.transaction transaction.abort:131 aborting = 'File transaction for '/etc/ovirt-hosted-engine-ha/broker.conf'' Complete log here: http://futz.org/users/tmp/ovirt5/ovirt-hosted-engine-setup-20141025123111-g= 51fy0.log I thought it might because there was still a tagged vlan on the interface, so I tried to deploy again after removing everything else from eth0, but still no luck. that log is at http://futz.org/users/tmp/ovirt5/ovirt-hosted-engine-setup-20141025150830-s= 2byre.log any hints tips appreciated... Robert --=20 Senior Software Engineer @ Parsons --Sig_/UCS9Qt+.3XGZ4pTqVuU5k2x Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlRL94sACgkQ7/fVLLY1mngq5gCghmZXSHf0Svg0QAp4PGSAHpJL 6IIAmgPh23Hd2KBemHszMgcG9OZgMLB6 =jR+l -----END PGP SIGNATURE----- --Sig_/UCS9Qt+.3XGZ4pTqVuU5k2x--
On Sat, Oct 25, 2014 at 03:18:32PM -0400, Robert Story wrote:
I'm on my 4th attempt to get a 3.5 hosted-engine set up on CentOS 6.5. I seem to hit a different snag each time. The first 3 were with the ovirtmgmt bridge on a tagged VLAN, so I decided to go back to an untagged interface and see if I had better luck. But this install failed even earlier, when creating the management bridge:
2014-10-25 12:37:24 INFO otopi.plugins.ovirt_hosted_engine_setup.network.bridge bridge._misc:198 Configuring the management bridge 2014-10-25 12:37:25 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/network/bridge.py", line 207, in _misc _setupNetworks(conn, networks, {}, {'connectivityCheck': False}) File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/network/bridge.py", line 225, in _setupNetworks 'message: "%s"' % (networks, code, message)) RuntimeError: Failed to setup networks {'ovirtmgmt': {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', 'ipaddr': '10.69.79.31'}}. Error code: "16" message: "Unexpected exception"
This means that something nasty happened inside Vdsm while attempting to create the bridge. Can you attach vdsm.log and supervdsmd.log?
--Sig_/Ki+7V+kK+Lzag3h0NZoN94g Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 25 Oct 2014 23:30:41 +0100 Dan wrote: DK> On Sat, Oct 25, 2014 at 03:18:32PM -0400, Robert Story wrote: DK> > line 225, in _setupNetworks 'message: "%s"' % (networks, code, DK> > message)) RuntimeError: Failed to setup networks {'ovirtmgmt': DK> > {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', DK> > 'ipaddr': '10.69.79.31'}}. Error code: "16" message: "Unexpected DK> > exception" DK>=20 DK> This means that something nasty happened inside Vdsm while attempting to DK> create the bridge. DK>=20 DK> Can you attach vdsm.log and supervdsmd.log? Sure... http://futz.org/users/tmp/ovirt5/supervdsm.log http://futz.org/users/tmp/ovirt5/vdsm.log Robert --=20 Senior Software Engineer @ Parsons --Sig_/Ki+7V+kK+Lzag3h0NZoN94g Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlRMS90ACgkQ7/fVLLY1mnjMcgCeK7Tp0sf4hFNj33dwouraEC5I ehoAoIrdqiOfYUl6XZfwg2t+IuTlaW7a =/Ii5 -----END PGP SIGNATURE----- --Sig_/Ki+7V+kK+Lzag3h0NZoN94g--
On Sat, Oct 25, 2014 at 09:18:18PM -0400, Robert Story wrote:
On Sat, 25 Oct 2014 23:30:41 +0100 Dan wrote: DK> On Sat, Oct 25, 2014 at 03:18:32PM -0400, Robert Story wrote: DK> > line 225, in _setupNetworks 'message: "%s"' % (networks, code, DK> > message)) RuntimeError: Failed to setup networks {'ovirtmgmt': DK> > {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', DK> > 'ipaddr': '10.69.79.31'}}. Error code: "16" message: "Unexpected DK> > exception" DK> DK> This means that something nasty happened inside Vdsm while attempting to DK> create the bridge. DK> DK> Can you attach vdsm.log and supervdsmd.log?
Sure...
http://futz.org/users/tmp/ovirt5/supervdsm.log http://futz.org/users/tmp/ovirt5/vdsm.log
supervdsm.log has MainProcess|Thread-16::DEBUG::2014-10-25 12:37:25,045::supervdsmServer::101::SuperVdsm.ServerCallback::(wrapper) call setupNetworks with ({'ovirtmgmt': {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', 'ipaddr': '10.69.79.31'}}, {}, {'connectivityCheck': False}) {} MainProcess|Thread-16::WARNING::2014-10-25 12:37:25,046::libvirtconnection::135::root::(wrapper) connection to libvirt broken. ecode: 1 edom: 7 MainProcess|Thread-16::CRITICAL::2014-10-25 12:37:25,046::libvirtconnection::137::root::(wrapper) taking calling process down. MainThread::DEBUG::2014-10-25 12:37:25,046::supervdsmServer::451::SuperVdsm.Server::(main) Terminated normally MainProcess|Thread-16::DEBUG::2014-10-25 12:37:25,046::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 1 edom: 7 level: 2 message: internal error client socket is closed which means that libvirtd has died (or was restarted). Jiri, can you tell why this has happened? Dan.
On 10/26/2014 11:13 PM, Dan Kenigsberg wrote:
On Sat, Oct 25, 2014 at 09:18:18PM -0400, Robert Story wrote:
On Sat, 25 Oct 2014 23:30:41 +0100 Dan wrote: DK> On Sat, Oct 25, 2014 at 03:18:32PM -0400, Robert Story wrote: DK> > line 225, in _setupNetworks 'message: "%s"' % (networks, code, DK> > message)) RuntimeError: Failed to setup networks {'ovirtmgmt': DK> > {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', DK> > 'ipaddr': '10.69.79.31'}}. Error code: "16" message: "Unexpected DK> > exception" DK> DK> This means that something nasty happened inside Vdsm while attempting to DK> create the bridge. DK> DK> Can you attach vdsm.log and supervdsmd.log?
Sure...
http://futz.org/users/tmp/ovirt5/supervdsm.log http://futz.org/users/tmp/ovirt5/vdsm.log
supervdsm.log has
MainProcess|Thread-16::DEBUG::2014-10-25 12:37:25,045::supervdsmServer::101::SuperVdsm.ServerCallback::(wrapper) call setupNetworks with ({'ovirtmgmt': {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', 'ipaddr': '10.69.79.31'}}, {}, {'connectivityCheck': False}) {} MainProcess|Thread-16::WARNING::2014-10-25 12:37:25,046::libvirtconnection::135::root::(wrapper) connection to libvirt broken. ecode: 1 edom: 7 MainProcess|Thread-16::CRITICAL::2014-10-25 12:37:25,046::libvirtconnection::137::root::(wrapper) taking calling process down. MainThread::DEBUG::2014-10-25 12:37:25,046::supervdsmServer::451::SuperVdsm.Server::(main) Terminated normally MainProcess|Thread-16::DEBUG::2014-10-25 12:37:25,046::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 1 edom: 7 level: 2 message: internal error client socket is closed
which means that libvirtd has died (or was restarted).
Jiri, can you tell why this has happened?
Hi Dan, I'm not libvirt expert, so I don't have any idea why it died and I don't think the setup restarts it during the installation. --Jirka
Dan.
On Mon, Oct 27, 2014 at 07:49:45AM +0100, Jiri Moskovcak wrote:
On 10/26/2014 11:13 PM, Dan Kenigsberg wrote:
On Sat, Oct 25, 2014 at 09:18:18PM -0400, Robert Story wrote:
On Sat, 25 Oct 2014 23:30:41 +0100 Dan wrote: DK> On Sat, Oct 25, 2014 at 03:18:32PM -0400, Robert Story wrote: DK> > line 225, in _setupNetworks 'message: "%s"' % (networks, code, DK> > message)) RuntimeError: Failed to setup networks {'ovirtmgmt': DK> > {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', DK> > 'ipaddr': '10.69.79.31'}}. Error code: "16" message: "Unexpected DK> > exception" DK> DK> This means that something nasty happened inside Vdsm while attempting to DK> create the bridge. DK> DK> Can you attach vdsm.log and supervdsmd.log?
Sure...
http://futz.org/users/tmp/ovirt5/supervdsm.log http://futz.org/users/tmp/ovirt5/vdsm.log
supervdsm.log has
MainProcess|Thread-16::DEBUG::2014-10-25 12:37:25,045::supervdsmServer::101::SuperVdsm.ServerCallback::(wrapper) call setupNetworks with ({'ovirtmgmt': {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', 'ipaddr': '10.69.79.31'}}, {}, {'connectivityCheck': False}) {} MainProcess|Thread-16::WARNING::2014-10-25 12:37:25,046::libvirtconnection::135::root::(wrapper) connection to libvirt broken. ecode: 1 edom: 7 MainProcess|Thread-16::CRITICAL::2014-10-25 12:37:25,046::libvirtconnection::137::root::(wrapper) taking calling process down. MainThread::DEBUG::2014-10-25 12:37:25,046::supervdsmServer::451::SuperVdsm.Server::(main) Terminated normally MainProcess|Thread-16::DEBUG::2014-10-25 12:37:25,046::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 1 edom: 7 level: 2 message: internal error client socket is closed
which means that libvirtd has died (or was restarted).
Jiri, can you tell why this has happened?
Hi Dan, I'm not libvirt expert, so I don't have any idea why it died and I don't think the setup restarts it during the installation.
When `vdsm-tool configure` change libvirt's condifuration, the installation should restart libvirtd. Vdsm (and supervdsm) must be restarted after the new libvirtd process is up. I remember that we had some problems in developement time, and wonder if we see here another case. Can you or Sandro compare timeings and check this out?
participants (3)
-
Dan Kenigsberg -
Jiri Moskovcak -
Robert Story