OpenLens 6.3.0 Blank UI

Question

OpenLens 6.3.0 Blank UI

rajaie-sg opened this issue 2 years ago · 70 comments

I upgraded from OpenLens 6.2.5 to 6.3.0 and now see a blank UI when I connect to any cluster

I was not experiencing this issue with 6.2.5. I tried opening and closing the application multiple times, but the same issue persisted. Anyone else having similar issues?

felipefda commented 2 years ago

Same here

kderck commented 2 years ago

Same here

Answer 1 · 2022-12-22T17:43:13.000Z

Same.

The only thing that solved me for now is cmd+r after you are connected to the cluster and see the blank page.
I've tried the deletion of ~/Library/Application Support/Lens with no success.
I've tried also: https://github.com/ykursadkaya/homebrew-openlens and it's the same
I've tried also downloading the 6.2.5 and it was the same...
EDIT: 6.2.5 is working! go down to my msg, explaining how to downgrade back to 6.2.5

Answer 2 · 2022-12-22T18:03:09.000Z

@ErezWeiss thank you for cmd+r, indeed helps

Answer 3 · 2022-12-22T18:07:49.000Z

@mtomilov great!
Let us know if you solved it somehow

Answer 4 · 2022-12-22T18:19:41.000Z

cmd+r made the UI come back, but it seems that I have to run it every time I open Lens. Another issue I discovered is that the "Exec into container" and "Logs" button is gone from Pods

Answer 5 · 2022-12-22T18:29:58.000Z

Was it in the previous version?

Answer 6 · 2022-12-22T18:35:09.000Z

Nope. With 6.2.5 I see the "Pod Logs" and "Pod Shell" and "Attach to Pod" buttons

Answer 7 · 2022-12-22T18:38:34.000Z

seems related:
lensapp/lens#1690

Answer 8 · 2022-12-22T18:43:27.000Z

I've managed to install 6.2.5 and it seems to be working

Answer 9 · 2022-12-22T18:46:29.000Z

brew uninstall openlens

rm -rf ~/Library/Application Support/OpenLens

rm -rf ~/Library/Logs/OpenLens

vi openlens.rb and paste this:

cask "openlens" do
  arch arm: "-arm64"

  version "6.2.5"
  sha256 arm:   "673a4ad49bb108bd1b995bf0d3eda971254ab6da4f54ad65f067208c8cde99db",
         intel: "e680ca5f0091663435696eff4da6666007d7bc8cb69078f56d1b7d7674cca296"

  url "https://github.com/MuhammedKalkan/OpenLens/releases/download/v#{version}/OpenLens-#{version}#{arch}.dmg"
  name "OpenLens"
  desc "Open source build of Lens Kubernetes IDE"
  homepage "https://github.com/MuhammedKalkan/OpenLens/"

  auto_updates true

  app "OpenLens.app"

  zap trash: [
    "~/Library/Application Support/OpenLens",
    "~/Library/Logs/OpenLens",
  ]
end

brew install --cask openlens.rb

Answer 10 · 2022-12-22T21:22:26.000Z

lensapp/lens#1690

Relevant issue lensapp/lens#6823

Answer 11 · 2022-12-23T10:43:53.000Z

lensapp/lens#6819 Smells of revenue protection disguised as a technical fix. The arch package maintainer has got stuffed by this too. I expect a fork from 6.2.x will be the only solution.

Answer 12 · 2022-12-23T11:23:14.000Z

yeah they killed it

lensapp/lens#6823 (comment)

Answer 13 · 2022-12-23T12:40:33.000Z

Reading PRs like lensapp/lens#6722 feels like they also want to disable binaries at OpenLens at all.

Answer 14 · 2022-12-25T09:18:47.000Z

Wow...
Seems like I will change from Lens

Answer 15 · 2022-12-27T08:55:50.000Z

Also additionally to the above experience, I cannot change the sync files and folders option to have a specific config file. Always get reset to the default one.

Answer 16 · 2022-12-27T09:04:45.000Z

Also additionally to the above experience, I cannot change the sync files and folders option to have a specific config file. Always get reset to the default one.

lensapp/lens#6834

Answer 17 · 2022-12-27T09:09:51.000Z

With 6.2.5 dmg, things work as expected. Unfortunately ther is no brew support for installing this specific version.

Answer 18 · 2022-12-27T10:55:29.000Z

@rajaie-sg Can you test if it's still an issue in latest master?

Answer 19 · 2022-12-30T11:23:37.000Z

The good news is, that 6.4.0-alpha.0 fixes this issue and #6834 as well.
Tested with local build on macOS Big Sur (M1 silicon)

Answer 20 · 2023-01-02T19:37:02.000Z

With 6.2.5 dmg, things work as expected. Unfortunately ther is no brew support for installing this specific version.

I've explained it above

Answer 21 · 2023-01-03T11:00:05.000Z

ErezWeiss

@ErezWeiss, this only works for one time and the application is auto-updated to 6.3.0. tried to brew cu pin openlens and other methods but can't get it to stop updating... any ideas?

Answer 22 · 2023-01-03T11:02:16.000Z

Lens decide to make the update non toggleable.

Answer 23 · 2023-01-03T11:15:48.000Z

The good news is, that 6.4.0-alpha.0 fixes this issue and #6834 as well. Tested with local build on macOS Big Sur (M1 silicon)

Maybe we have to build this one

Answer 24 · 2023-01-03T13:15:06.000Z

ErezWeiss

@ErezWeiss, this only works for one time and the application is auto-updated to 6.3.0. tried to brew cu pin openlens and other methods but can't get it to stop updating... any ideas?

Hi,
after installing version 6.2.5 you can block updates by changing the permissions of the pending folder:

sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending

Answer 25 · 2023-01-03T16:24:03.000Z

same error here, on macOS with v6.3.0

Answer 26 · 2023-01-03T17:06:45.000Z

Just my 2c, this kind of thing is typically "fork in the road" time to break off from upstream.

Answer 27 · 2023-01-03T17:32:22.000Z

@djvs feel free to fork

Answer 28 · 2023-01-03T17:57:01.000Z

@jkroepke To fork off from the main Lens I mean, not to fork OpenLens, sorry.

Answer 29 · 2023-01-04T09:29:48.000Z

Im just using 6.2.5 binary until some new developments in this case, i dont want to pay for the features i dont use anyway

Answer 30 · 2023-01-04T16:06:50.000Z

since i exec this command to block update, openlens is not launching anymore, no know how to fix this

Answer 31 · 2023-01-04T16:13:31.000Z

since i exec this command to block update, openlens is not launching anymore, no know how to fix this

working for me...

Answer 32 · 2023-01-04T16:30:48.000Z

sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending

Dude you can restore permissions with this command:

sudo chmod -R 755 ~/Library/Application\ Support/Caches/open-lens-updater/pending

in tshoot i've deleted this folder, after reinstalling openlens, this folder not recreate ~/Library/Application Support/Caches/open-lens-updater/pending: No such file or directory

Answer 33 · 2023-01-04T16:31:09.000Z

since i exec this command to block update, openlens is not launching anymore, no know how to fix this

I simply changed the permissions of the folder....if you want restore permissions run this command:

sudo chmod -R 755 ~/Library/Application\ Support/Caches/open-lens-updater/pending

Answer 34 · 2023-01-04T16:33:45.000Z

sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending

Dude you can restore permissions with this command:
sudo chmod -R 755 ~/Library/Application\ Support/Caches/open-lens-updater/pending

in tshoot i've deleted this folder, after reinstalling openlens, this folder not recreate ~/Library/Application Support/Caches/open-lens-updater/pending: No such file or directory

Could you explain better, I can't follow you...

Answer 35 · 2023-01-04T16:45:35.000Z

Anyway I can't see the pods menu in 6.3.0 😅😅 it's an error?

Answer 36 · 2023-01-04T16:48:50.000Z

For 6.3.0, go to Extensions and install @alebcay/openlens-node-pod-menu, then pods menu are back. Its way more easier then try to block to auto-update

Checkout README.md in this repository, because its documented.

Answer 37 · 2023-01-04T17:15:48.000Z

sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending

Dude you can restore permissions with this command:
sudo chmod -R 755 ~/Library/Application\ Support/Caches/open-lens-updater/pending

in tshoot i've deleted this folder, after reinstalling openlens, this folder not recreate ~/Library/Application Support/Caches/open-lens-updater/pending: No such file or directory

Could you explain better, I can't follow you...

found how to fixed, brew uninstall didn't killed the lens process, so found it in monitor activity then kill it my self then workd, 6.2.5. Awesome thanks guys

Answer 38 · 2023-01-05T14:07:12.000Z

ErezWeiss

@ErezWeiss, this only works for one time and the application is auto-updated to 6.3.0. tried to brew cu pin openlens and other methods but can't get it to stop updating... any ideas?

Hi, after installing version 6.2.5 you can block updates by changing the permissions of the pending folder:

sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending

for Linux it's ~/.cache/open-lens-updater/pending directory

Answer 39 · 2023-01-05T14:27:40.000Z

For 6.3.0, go to Extensions and install @alebcay/openlens-node-pod-menu, then pods menu are back. Its way more easier then try to block to auto-update

thank you!

Answer 40 · 2023-01-05T17:55:13.000Z

I confirm I'm experiencing the same issue on ARM using 6.3.0. No issues on 6.2.5

Answer 41 · 2023-01-05T18:12:44.000Z

Seeing this here as well. I can put 6.2.5 back on, but the darn thing keeps auto-updating to 6.3.0 and breaking again.

Answer 42 · 2023-01-06T10:04:03.000Z

I think 6.3.0 release should be withdrawn from stable channel

Answer 43 · 2023-01-10T11:25:55.000Z

For anyone using 6.3.0 on Windows, it is CTRL+R that will show the cluster details. Thanks @ErezWeiss

Answer 44 · 2023-01-10T12:24:06.000Z

CTRL+R does not consistently work for me. Moreover, sometimes when it shows the cluster, it shows corrupted or half-rendered data. 6.3.0 is just straight-up broken and should be yanked from stable channel.

Answer 45 · 2023-01-10T19:09:08.000Z

Ok so that i understand. When i install extensions on 6.3.0 there is no issue. Are you guys talking about something else. Because i am not experiencing any missing behaviour

Answer 46 · 2023-01-10T20:41:11.000Z

In my case I have just started using 6.3.0 on Windows today. Using it as is, straight after installing without any add-ons/extensions. Only run into the blank UI issue but with the CTRL+R fix it has worked for me so far. However only used a subset of the functionality and haven't used it long enough to be able to tell if 6.3.0 is a good release or not.

Answer 47 · 2023-01-11T07:39:21.000Z

@MuhammedKalkan the issue is the blank page when accessing cluster, as others mentioned cmd+r relates the screen, but even after that it doesn't look like it fully loads the information. When clicking on a pod there's no option to get a shell of it or see logs. There might be more things, but I didn't explore more, because the above already makes the product unusable.

Also an option to disable upgrade is absolutely needed. The recommendation given by others don't work. For example changing permissions on pending folder prevents OpenLens from starting.

Making the app (in OS X) read only, seems to work, but then open lens nags periodically to enter password.

Answer 48 · 2023-01-11T09:35:04.000Z

@MuhammedKalkan there's a screencap right at the top of this thread. That's what it looks like for me too.

(In my opinion) Basic install of app should 'work', i.e.

As a Kubernetes administrator with a functioning ~/.kube/config and current authentication:

I can install OpenLens (via a supported mechanism on a supported platform)
I can immediately run OpenLens,
I can immediately browse my cluster catalogue in OpenLens
I can immediately explore my clusters in OpenLens

There should be no non-obvious steps required for basic functionality such as installing extensions or the cmd+R/Ctrl+R that I had to come here to find out about. Consider electron apps like:

VSCode
Google Chrome
Slack

6.2.5 acheived this

Answer 49 · 2023-01-11T10:39:05.000Z

I agree with you but currently Lens team seems to prioritize making OpenLens a package rather than an executable app. More than 3 weeks now, they have not published a new version. I feel next version will be just a package stripped to the bone.
We need to wait and see where this goes and then take action.

That being said, until then, auto update will not fetch 6.3.0 for now and you can revert to whatever version you like.

Keep in mind tho, this repo does not alter source code, so all that functionality needs a fork. That remains to be decided

Answer 50 · 2023-01-11T12:04:15.000Z

For 6.3.0, go to Extensions and install @alebcay/openlens-node-pod-menu, then pods menu are back. Its way more easier then try to block to auto-update

Checkout README.md in this repository, because its documented.

I am using this fix from @jkroepke (6.3.0) Windows 10 and its working fine so far.

Answer 51 · 2023-01-11T13:34:48.000Z

non-obvious steps required for basic functionality

@joshuamkite Please note that pod shell and pod logs are not longer part of the basic functionality for OpenLens 6.3.0.
If you want this functionality, you have to install extensions. If you have a different opinion, share you feelings here: https://github.com/lensapp/lens/

Answer 52 · 2023-01-12T07:23:24.000Z

Is this still an issue with the latest version ?

Answer 53 · 2023-01-12T09:04:46.000Z

issue

Unfortunately, yes. Facing the same issue. m1, installed via brew, version - 6.3.0

Answer 54 · 2023-01-12T09:06:11.000Z

no i meant 6.4.0 alpha. There is nothing to be done for 6.3.0

Answer 55 · 2023-01-12T10:36:24.000Z

@MuhammedKalkan I tested the new version. The Pods entry is back, but I cannot access logs or start a shell of any Pod, just Editing or Deleting them.

Answer 56 · 2023-01-12T11:11:01.000Z

@simonberger did you install the extension? @alebcay/openlens-node-pod-menu

Answer 57 · 2023-01-12T11:19:04.000Z

@jkroepke No as I tested it on 6.3 but it was no working solution for me. Just to ensure proper configuration I again cleaned up config/extension folder before re-launching. Result remains and also the empty app issue is still in Alpha 2 for the first start but the known CMD + R solved it

Answer 58 · 2023-01-12T11:30:20.000Z

It feels like an upstream issue, I guess this issue can be closed here, since the error has nothing todo with the redistribution.

Answer 59 · 2023-01-13T07:01:30.000Z

@simonberger did you install the extension? @alebcay/openlens-node-pod-menu

I tried to install extension '@alebcay/openlens-node-pod-menu' in Extensions in Openlens UI. But I got
"Failed to get registry information for extension: d: request to https://registry.npmjs.org/@alebcay/openlens-node-pod-menu failed, reason: unable to verify the first certificate"

Answer 60 · 2023-01-13T07:09:22.000Z

That seems you have configured npm for a proxy or a vpn. Not relevant anything here

Either connect vpn or fix npm config

Answer 61 · 2023-01-13T07:15:03.000Z

That seems you have configured npm for a proxy or a vpn. Not relevant anything here

Either connect vpn or fix npm config

thank you for responding. you are correct, my VPN made the install failed.

Answer 62 · 2023-01-19T17:04:06.000Z

On version 6.3.0 or that latest alpha with @alebcay/openlens-node-pod-menu installed I still don't get any of the menus back. Any suggestions?

Answer 63 · 2023-01-23T21:54:31.000Z

@hyprsnpr noticing this as well. Is this extension not working?

Answer 64 · 2023-01-23T22:05:11.000Z

@hyprsnpr noticing this as well. Is this extension not working?

It's def not working for me, it seems to be working for others so not sure why I'm broken. I'm windows where as a lot of the other examples I see is MacOS. I would have to think windows was tested though.

Answer 65 · 2023-01-23T22:54:40.000Z

Updated cask for OpenLens v6.4.0-alpha4:

cask "openlens-6.4.0.4" do
  arch arm: "-arm64"

  version "6.4.0-alpha.4"
  sha256 arm:   "19ff657ec70114015382411b1a6ba8735148a6a0eefa7be29f0f61d50fd695c2",
         intel: "18643cfaa1461a15e4d07474491994ca17cdb17bb3dced28568e0bd223bff44c"

  url "https://github.com/MuhammedKalkan/OpenLens/releases/download/v#{version}/OpenLens-#{version}#{arch}.dmg"
  name "OpenLens"
  desc "Open source build of Lens Kubernetes IDE"
  homepage "https://github.com/MuhammedKalkan/OpenLens/"

  auto_updates true

  app "OpenLens.app"

  zap trash: [
    "~/Library/Application Support/OpenLens",
    "~/Library/Logs/OpenLens",
  ]
end

(renamed cask so as to not conflict/autoupdate with standard openlens cask)

Answer 66 · 2023-02-14T08:23:05.000Z

menu installed I still don't

~~where's this extension ui is located? I can't seem to be able to find it~~
Command+Shift+E should show it

Answer 67 · 2023-02-14T16:18:44.000Z

For me the "Pods" item is missing from the Workloads menu:

Answer 68 · 2023-05-23T13:59:57.000Z

Nope. With 6.2.5 I see the "Pod Logs" and "Pod Shell" and "Attach to Pod" buttons
@rajaie-sg Thank you for suggestion.

On Windows 10 machine, I was able to resolve missing Pod shell/terminal and Log issue after installing 6.2.5 version.
https://github.com/MuhammedKalkan/OpenLens/releases/tag/v6.2.5

Uninstall existing OpenLens(if any) from "Add or remove programs"
If you have existing OpenLens then feel free to delete it.
Delete C:\Users\YOURUSER\AppData\Roaming
Delete C:\Users\YOURUSER\AppData\Local\Programs

Existing unwanted plugins can be removed also
Delete C:\Users\YOURUSER\ .k8slens

Configure Kubectl and start using it.