Local charms icons not properly shown in the GUI canvas #3067

Open
ionutbalutoiu opened this Issue Jul 11, 2017 · 6 comments

Comments

Projects
None yet
4 participants

ionutbalutoiu commented Jul 11, 2017

I have a local Juju controller on MAAS with GUI enabled and I deployed a couple of local charms.
The charms icons are broken in the GUI canvas and this is what I see: http://balutoiu.com/ionut/icons.png

If I do an inspect element on the charm box from the canvas and open the icon url into another tab, I see that icon is properly fetched from the Juju controller.

Moreover, when using Firefox, there is no issue and icons are properly shown in the GUI canvas.

Versions of the tools used:

  • Juju 2.2.1
  • Google Chrome 59.0.3071.115
  • Firefox 54.0.1

@hatched hatched added this to the loyal la forge milestone Jul 11, 2017

Owner

hatched commented Jul 11, 2017

Thanks for the report! We'll look into this shortly.

@hatched hatched modified the milestones: loyal la forge - 2.8.0, massive morn Aug 1, 2017

@frankban frankban modified the milestones: naive nog, massive morn Aug 24, 2017

Any update on this bug ? I'm using 2.2.4-xenial-amd64 right now and it icons are still not visible in Google Chrome.

deephack1982 commented Sep 26, 2017

I just commented on this related issue. https://github.com/juju/juju-gui/issues/1262#issuecomment-332166336

Can confirm that it works correctly in Firefox.

Owner

hatched commented Oct 3, 2017

As this requires extensive changes in Juju to provide us with a different way to securely fetch the local charm assets, any updates to this may be a long time coming. I consider this to be a regression in Chrome and hopefully they will fully revert the change in time.

@hatched hatched modified the milestones: naive nog, __flickering future__ Oct 3, 2017

Member

frankban commented Oct 4, 2017

Yes I agree. We need to implement a macaroon based auth for getting charm files from the controller. This means adding macaraq logic for local users as well. While this is something that we'd like to implement for other auth-related reasons as well, we'll have to find a slot for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment