Re: [ovirt-users] Fwd: web-ui issues

2016-12-07 Thread Oved Ourfali
We are looking into the issue.
>From what I saw this is specific in the VMs tab, so we're trying to
understand what might have caused it.

Thanks,
Oved


On Wed, Dec 7, 2016 at 1:21 PM, Maton, Brett 
wrote:

> This didn't get sent to the list...
>
> -- Forwarded message --
> From: Alexander Wels 
> Date: 6 December 2016 at 16:43
> Subject: Re: [ovirt-users] web-ui issues
> To: "Maton, Brett" 
>
>
> On Tuesday, December 6, 2016 4:41:35 PM EST you wrote:
> > Not odd at all, but yes it does work for awhile before 'dying' again
> >
>
> Great, then I have a system here that is reproducing your issue that I can
> mess with. I will let you know if I find a solution.
>
> > On 6 December 2016 at 16:13, Alexander Wels  wrote:
> > > On Tuesday, December 6, 2016 2:49:55 PM EST you wrote:
> > > > No change...
> > > >
> > > > The 'portal' welcome page does say:
> > > >
> > > > Welcome to Open Virtualization Manager Version 4.0.6.2-1.el7.centos
> > > >
> > > > I would have expected it to have moved to 4.0.6.3
> > > > I've run engine-setup ( a few times ) and yum upgrade isn't finding
> any
> > >
> > > new
> > >
> > > > packages
> > >
> > > Another odd question, if you restart the engine (systemctl restart
> ovirt-
> > > engine) and immediately log back in, does that 'fix' the issue for a
> few
> > > minutes and does it re-appear after that? Or a restart never fixes it
> at
> > > all?
> > >
> > > > On 6 December 2016 at 14:40, Alexander Wels 
> wrote:
> > > > > On Tuesday, December 6, 2016 2:29:39 PM EST you wrote:
> > > > > > I'm not holding my breath as I had the problem before installing
> > >
> > > symbol
> > >
> > > > > > maps, but it might explain why ui.log is empty
> > > > >
> > > > > Well the bugzilla is basically the following scenario:
> > > > >
> > > > > 1. You have oVirt version X and you have the matching debug symbols
> > > > > installed.
> > > > > 2. You upgrade oVirt version to X+1. This doesn't upgrade the debug
> > > > > symbols.
> > > > > 3. You get the interrupted message on your screen.
> > > > >
> > > > > So uninstalling the debug symbols should fix that scenario, if
> yours
> > >
> > > was
> > >
> > > > > not
> > > > > that scenario then you are right it won't change anything. But it
> > > > > can't
> > > > > hurt
> > > > > either.
> > > > >
> > > > > > On 6 December 2016 at 14:26, Alexander Wels 
> > >
> > > wrote:
> > > > > > > On Tuesday, December 6, 2016 2:22:38 PM EST you wrote:
> > > > > > > > I 'bumped' from 4.0.6-2 to 4.0.6-3 ( yum upgrade )
> > > > > > >
> > > > > > > So someone just opened a bugzilla with a sympton that looks
> > > > >
> > > > > suspiciously
> > > > >
> > > > > > > like
> > > > > > > yours, and the resolution to that bugzilla was to REMOVE the
> > > > > > > symbolMaps
> > > > > > > because they were out of sync with the main application (and
> doing
> > >
> > > a
> > >
> > > > > yum
> > > > >
> > > > > > > update isn't automatically updating the symbol maps).
> > > > > > >
> > > > > > > try this:
> > > > > > >
> > > > > > > yum remove ovirt-engine-webadmin-portal-debuginfo
> > > > > > >
> > > > > > > And restart the engine, see if that solves your issue.
> > > > > > >
> > > > > > > > On 6 December 2016 at 14:21, Alexander Wels <
> aw...@redhat.com>
> > > > >
> > > > > wrote:
> > > > > > > > > On Tuesday, December 6, 2016 1:42:33 PM EST you wrote:
> > > > > > > > > > Ok thanks.
> > > > > > > > > >
> > > > > > > > > >   I've restarted the ui a few times today, still nothing
> (
> > > > > > > > > >   at
> > > > >
> > > > > all )
> > > > >
> > > > > > > in
> > > > > > >
> > > > > > > > > > ui.log
> > > > > > > > > >
> > > > > > > > > >   The errors do look like 'iffy' queries, no errors in
> > > > > > > > > >   PostgreSQL
> > > > > > >
> > > > > > > logs
> > > > > > >
> > > > > > > > > > though.
> > > > > > > > >
> > > > > > > > > Strange question, did you recently upgrade from a previous
> > >
> > > version
> > >
> > > > > of
> > > > >
> > > > > > > > > oVirt?
> > > > > > > > >
> > > > > > > > > > On 6 December 2016 at 13:28, Alexander Wels <
> > >
> > > aw...@redhat.com>
> > >
> > > > > > > wrote:
> > > > > > > > > > > On Monday, December 5, 2016 8:49:20 PM EST Maton, Brett
> > >
> > > wrote:
> > > > > > > > > > > > Sure here you go:
> > > > > > > > > > > >
> > > > > > > > > > > > [image: Inline images 1]
> > > > > > > > > > > > Close the dialogs and the dashboard fades in, Virtual
> > > > >
> > > > > Machines
> > > > >
> > > > > > > tab
> > > > > > >
> > > > > > > > > > > doesn't
> > > > > > > > > > >
>
> > > > > > > > > > > > (or I get fed up of closing dialogs before it does)
> > > > > > > > > > > >
> > > > > > > > > > > > [image: Inline images 2]
> > > > > > > > > > >
> > > > > > > > > > > Interesting, those aren't actually UI failures, those
> > >
> > > appear
> > >
> > > > > to be
> > > > >
> > > > > > > > > > > failures

[ovirt-users] Fwd: web-ui issues

2016-12-07 Thread Maton, Brett
This didn't get sent to the list...

-- Forwarded message --
From: Alexander Wels 
Date: 6 December 2016 at 16:43
Subject: Re: [ovirt-users] web-ui issues
To: "Maton, Brett" 


On Tuesday, December 6, 2016 4:41:35 PM EST you wrote:
> Not odd at all, but yes it does work for awhile before 'dying' again
>

Great, then I have a system here that is reproducing your issue that I can
mess with. I will let you know if I find a solution.

> On 6 December 2016 at 16:13, Alexander Wels  wrote:
> > On Tuesday, December 6, 2016 2:49:55 PM EST you wrote:
> > > No change...
> > >
> > > The 'portal' welcome page does say:
> > >
> > > Welcome to Open Virtualization Manager Version 4.0.6.2-1.el7.centos
> > >
> > > I would have expected it to have moved to 4.0.6.3
> > > I've run engine-setup ( a few times ) and yum upgrade isn't finding
any
> >
> > new
> >
> > > packages
> >
> > Another odd question, if you restart the engine (systemctl restart
ovirt-
> > engine) and immediately log back in, does that 'fix' the issue for a few
> > minutes and does it re-appear after that? Or a restart never fixes it at
> > all?
> >
> > > On 6 December 2016 at 14:40, Alexander Wels  wrote:
> > > > On Tuesday, December 6, 2016 2:29:39 PM EST you wrote:
> > > > > I'm not holding my breath as I had the problem before installing
> >
> > symbol
> >
> > > > > maps, but it might explain why ui.log is empty
> > > >
> > > > Well the bugzilla is basically the following scenario:
> > > >
> > > > 1. You have oVirt version X and you have the matching debug symbols
> > > > installed.
> > > > 2. You upgrade oVirt version to X+1. This doesn't upgrade the debug
> > > > symbols.
> > > > 3. You get the interrupted message on your screen.
> > > >
> > > > So uninstalling the debug symbols should fix that scenario, if yours
> >
> > was
> >
> > > > not
> > > > that scenario then you are right it won't change anything. But it
> > > > can't
> > > > hurt
> > > > either.
> > > >
> > > > > On 6 December 2016 at 14:26, Alexander Wels 
> >
> > wrote:
> > > > > > On Tuesday, December 6, 2016 2:22:38 PM EST you wrote:
> > > > > > > I 'bumped' from 4.0.6-2 to 4.0.6-3 ( yum upgrade )
> > > > > >
> > > > > > So someone just opened a bugzilla with a sympton that looks
> > > >
> > > > suspiciously
> > > >
> > > > > > like
> > > > > > yours, and the resolution to that bugzilla was to REMOVE the
> > > > > > symbolMaps
> > > > > > because they were out of sync with the main application (and
doing
> >
> > a
> >
> > > > yum
> > > >
> > > > > > update isn't automatically updating the symbol maps).
> > > > > >
> > > > > > try this:
> > > > > >
> > > > > > yum remove ovirt-engine-webadmin-portal-debuginfo
> > > > > >
> > > > > > And restart the engine, see if that solves your issue.
> > > > > >
> > > > > > > On 6 December 2016 at 14:21, Alexander Wels 
> > > >
> > > > wrote:
> > > > > > > > On Tuesday, December 6, 2016 1:42:33 PM EST you wrote:
> > > > > > > > > Ok thanks.
> > > > > > > > >
> > > > > > > > >   I've restarted the ui a few times today, still nothing (
> > > > > > > > >   at
> > > >
> > > > all )
> > > >
> > > > > > in
> > > > > >
> > > > > > > > > ui.log
> > > > > > > > >
> > > > > > > > >   The errors do look like 'iffy' queries, no errors in
> > > > > > > > >   PostgreSQL
> > > > > >
> > > > > > logs
> > > > > >
> > > > > > > > > though.
> > > > > > > >
> > > > > > > > Strange question, did you recently upgrade from a previous
> >
> > version
> >
> > > > of
> > > >
> > > > > > > > oVirt?
> > > > > > > >
> > > > > > > > > On 6 December 2016 at 13:28, Alexander Wels <
> >
> > aw...@redhat.com>
> >
> > > > > > wrote:
> > > > > > > > > > On Monday, December 5, 2016 8:49:20 PM EST Maton, Brett
> >
> > wrote:
> > > > > > > > > > > Sure here you go:
> > > > > > > > > > >
> > > > > > > > > > > [image: Inline images 1]
> > > > > > > > > > > Close the dialogs and the dashboard fades in, Virtual
> > > >
> > > > Machines
> > > >
> > > > > > tab
> > > > > >
> > > > > > > > > > doesn't
> > > > > > > > > >
> > > > > > > > > > > (or I get fed up of closing dialogs before it does)
> > > > > > > > > > >
> > > > > > > > > > > [image: Inline images 2]
> > > > > > > > > >
> > > > > > > > > > Interesting, those aren't actually UI failures, those
> >
> > appear
> >
> > > > to be
> > > >
> > > > > > > > > > failures
> > > > > > > > > > from backend requests. As in, get me some data, and the
> >
> > query
> >
> > > > > > > > > > fails
> > > > > > > > > > for
> > > > > > > > > > some
> > > > > > > > > > reason, there should be something in the engine log. Let
> > > > > > > > > > me
> > > >
> > > > dig up
> > > >
> > > > > > the
> > > > > >
> > > > > > > > > > ones
> > > > > > > > > > you posted again and take a closer look.
> > > > > > > > > >
> > > > > > > > > > > On 5 December 2016 at 20:11, Alexander Wels <
> > > >
> > > > aw...@redhat.com>
> > > >
> >