juju-gui get unusable if using multiple sessions browsers

The safari issue is currently https://bugs.launchpad.net/bugs/1329823 and can be worked around by accepting the self signed cert used. We're looking at a better way to do that.

Thanks for the report Nicolas, we'll investigate multiple browsers against the same live environment.

Sorry that's bug https://bugs.launchpad.net/juju-gui/+bug/1322596 for the safari issue.

Hi Nicolas, this is quite an interesting bug thanks for reporting it.

Unfortunately I'm not able to reproduce on various combinations of OS's and browsers using EC2.

I'm a little confused about the comments in the report. You mentioned EC2, but tagged orange-box, did the issue only present itself when using MAAS? If you can reproduce it in EC2, or other cloud provider, can you provide step by step detailed instructions on the reproduction steps which include the Environment Details, Client OS, browser versions, bundle id etc etc. Basically anything that can help me reproduce this locally.

It's also very likely that there will be errors in the browser console. If you could include these as well that would be very helpful. If your not familiar with it already here is a page which details how to use it in Chrome https://developer.chrome.com/devtools/index#console

It happens on Orange box during a live demo ..

So with MAAS but I did reproduce some on EC2 thinking it would be easier
to reproduce.

Deploy a bundle (like mongo) .. destroy some services and try to deploy
something else or the same ... lines get destroyed, boxes do not appaer
etc... and weirder stuff difficult to reproduce.

On 13/06/2014 19:25, Jeff Pihach wrote:
> Hi Nicolas, this is quite an interesting bug thanks for reporting it.
>
> Unfortunately I'm not able to reproduce on various combinations of OS's
> and browsers using EC2.
>
> I'm a little confused about the comments in the report. You mentioned
> EC2, but tagged orange-box, did the issue only present itself when using
> MAAS? If you can reproduce it in EC2, or other cloud provider, can you
> provide step by step detailed instructions on the reproduction steps
> which include the Environment Details, Client OS, browser versions,
> bundle id etc etc. Basically anything that can help me reproduce this
> locally.
>
> It's also very likely that there will be errors in the browser console.
> If you could include these as well that would be very helpful. If your
> not familiar with it already here is a page which details how to use it
> in Chrome https://developer.chrome.com/devtools/index#console
>
> ** Changed in: juju-gui
> Status: Triaged => Incomplete
>

--
Best Regards,
Nicolas Thomas Sales Engineer - Canonical
http://insights.ubuntu.com/?p=889
GPG FPR: D592 4185 F099 9031 6590 6292 492F C740 F03A 7EB9

Sorry I'm still not able to reproduce. It's possible that this is a bug only shows itself when hooked up to a MAAS environment. It would be immensely helpful if, when you get a chance, you could report back with detailed steps to reproduce.

Did you actually try ??

On Fri, Jun 13, 2014 at 10:38 PM, Jeff Pihach
<email address hidden> wrote:
> Sorry I'm still not able to reproduce. It's possible that this is a bug
> only shows itself when hooked up to a MAAS environment. It would be
> immensely helpful if, when you get a chance, you could report back with
> detailed steps to reproduce.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1329823
>
> Title:
> juju-gui get unusable if using multiple sessions browsers
>
> Status in Juju Graphical Interface:
> Incomplete
>
> Bug description:
> I did a try on EC2 with 4 GUIs in // deploy 1 bundle . got lots of
> changes and lines or even boxes not appaering on some.
>
>
> + does not appear at all on Safari from MacOS.. stuck in loading wheel mode.
>
> Multiple browsers/session is allowed and usefull for sharing or
> demoing ..
>
> Start 2 / 3 different browsers and deploy a bundle.
>
> It even append to have several boxes stuck (no movement allowed) on
> top of each other and no way to solve than destroy environment.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-gui/+bug/1329823/+subscriptions

--
Best Regards,
       Nicolas Thomas
http://insights.ubuntu.com/?p=889
EMEA Sales Engineer Canonical
GPG FPR: D592 4185 F099 9031 6590 6292 492F C740 F03A 7EB9

Nicolas, yes, Jeff states that he's tried. He's attempted to reproduce the scenario while watching from several connected browsers at the same time using chrome, firefox, and multiple times from the same browser via private browsing tools.

We're working on getting a test maas environment setup, but we're unable to replicate that scenario currently.

What we'd appreciate are a very clear set of steps that reproduce this for you. For instance:

What version of ubuntu, juju, and browsers are you running?
if you deploy to ec2, what version of the gui are you deploying?
once it's deployed, you mention deploying the mongodb bundle. Can you specify which bundle specifically you deploy?
when you mention destroying 'some services' what are you destroying. In the mongodb case, is the bundle completed and all relation lines are drawn before you attempt to destroy anything? Which of the services are you destroying?
After this destroying, what did you attempt to deploy? What boxes were you expecting to appear? Did you get an error notification in the GUI about conflicting service names or bundle errors?

As you mention, it's difficult to reproduce and we're attempting to but not having any success so far. Trying to narrow down your experience helps us do that.

Jeff has spent several hours attempting to replicate anything that resembles your issue, but has not had success. Please do not question that he's made an attempt. If you have something running that you can reproduce, please let us know and we'll be happy to do a hangout to help guide you through collecting error information from the environment so that we can get the details necessary to file bugs on the GUI or Juju as required.