Re: [Users] "unable to connect after upgrade 3.3.3 to 3.4.0"
----- Original Message -----
From: "Yedidyah Bar David" <didi(a)redhat.com>
To: "nicola gentile" <nicola.gentile.to(a)gmail.com>
Cc: "Users(a)ovirt.org" <users(a)ovirt.org>
Sent: Wednesday, April 2, 2014 3:40:04 PM
Subject: Re: [Users] "unable to connect after upgrade 3.3.3 to 3.4.0"
----- Original Message -----
> From: "nicola gentile" <nicola.gentile.to(a)gmail.com>
> To: "Users(a)ovirt.org" <users(a)ovirt.org>
> Sent: Monday, March 31, 2014 5:48:19 PM
> Subject: Re: [Users] "unable to connect after upgrade 3.3.3 to 3.4.0"
>
> Thank you, now works!
>
> NG
>
> 2014-03-31 16:40 GMT+02:00 Maurice James <midnightsteel(a)msn.com>:
> > Check your firewall settings. I have found that even though you tell the
> > install script to leave the firewall alone it still configures it for
> > you.
> > You might want try stopping your firewall temporarily.
> >
> >> Date: Mon, 31 Mar 2014 16:25:26 +0200
> >> From: nicola.gentile.to(a)gmail.com
> >> To: Users(a)ovirt.org
> >> Subject: [Users] "unable to connect after upgrade 3.3.3 to
3.4.0"
> >
> >>
> >> Hello,
> >> I'm trying oVirt allinone version 3.3.3 and after the upgrade to 3.4.0
> >> the virtual machines do not start using spice client (linux or
> >> windows).
> >> I'm using centos 6.5.
> >> The message displayed is "unable to connect to server console.vv
> >> graphics."
> >> Can someone help me?
Thanks both of you for the report.
This should not happen. Can you please post relevant logs? Including setup
and host-deploy? resulting firewall configuration?
Just to clarify: There was recently a discussion about a similar problem
in hosted-engine [1] resulting in opening a bug [2]. I do not know about
a similar problem in all-in-one. There, it's the opposite - setup asks
the engine to call host-deploy without changing the firewall, also without
allowing to override - 'override_iptables=False' in [3].
So if setup does change your firewall settings, it's doing that by itself,
not by host-deploy, despite you telling it not to (by your report).
[1] http://lists.ovirt.org/pipermail/users/2014-March/thread.html#22674
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1080823
[3]
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=packaging/setu...
--
Didi