Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] CRC fails to store pull secret in KDE wallet #4543

Closed
rohanKanojia opened this issue Jan 6, 2025 · 3 comments
Closed

[BUG] CRC fails to store pull secret in KDE wallet #4543

rohanKanojia opened this issue Jan 6, 2025 · 3 comments
Labels
kind/bug Something isn't working

Comments

@rohanKanojia
Copy link
Contributor

General information

Related to #2572

I'm using KDE Plasma Desktop environment where there is no GNOME Keyring

When I start the cluster using crc start, I'm able to start it but I get a minor warning:

WARN Cannot add pull secret to keyring: The name org.freedesktop.secrets was not provided by any .service files

Perhaps, this issue could be due to the underlying library (https://github.com/zalando/go-keyring) for storing pull secrets not supporting the KDE wallet. It's documentation states:

The Linux and *BSD implementation depends on the Secret Service dbus interface, which is provided by GNOME Keyring.

If I install gnome-keyring / seahorse packages, I'm able to resolve the issue.

Operating System

Linux

Hypervisor

KVM

Did you run crc setup before crc start?

yes

Running on

Laptop

Steps to reproduce

  1. Log in using KDE Desktop environment
  2. crc setup
  3. crc start
  4. Provide pull secret
  5. You'd see the warning message

CRC version

CRC version: 2.45.0+7aeb3b
OpenShift version: 4.17.7
MicroShift version: 4.17.7

CRC status

CRC config

Host Operating System

Ubuntu with KDE Plasma Desktop Environment

Expected behavior

CRC should be able to store pull secret in KDE keyring system. Or maybe we should document it that we only support GNOME Keyring.

Actual behavior

CRC logs a warning that's not clear enough to the user.

CRC Logs

~ : $ crc start
INFO Using bundle path /home/rohan/.crc/cache/crc_libvirt_4.17.7_amd64.crcbundle  
INFO Checking if running as non-root               
INFO Checking if running inside WSL2               
INFO Checking if crc-admin-helper executable is cached  
INFO Checking if running on a supported CPU architecture  
INFO Checking if crc executable symlink exists     
INFO Checking minimum RAM requirements             
INFO Check if Podman binary exists in: /home/rohan/.crc/bin/oc  
INFO Checking if Virtualization is enabled         
INFO Checking if KVM is enabled                    
INFO Checking if libvirt is installed              
INFO Checking if user is part of libvirt group     
INFO Checking if active user/process is currently part of the libvirt group  
INFO Checking if libvirt daemon is running         
INFO Checking if a supported libvirt version is installed  
INFO Checking if crc-driver-libvirt is installed   
INFO Checking crc daemon systemd socket units      
INFO Checking if AppArmor is configured            
INFO Checking if systemd-networkd is running       
INFO Checking if NetworkManager is installed       
INFO Checking if NetworkManager service is running  
INFO Checking if dnsmasq configurations file exist for NetworkManager  
INFO Checking if the systemd-resolved service is running  
INFO Checking if /etc/NetworkManager/dispatcher.d/99-crc.sh exists  
INFO Checking if libvirt 'crc' network is available  
INFO Checking if libvirt 'crc' network is active   
INFO Loading bundle: crc_libvirt_4.17.7_amd64...   
CRC requires a pull secret to download content from Red Hat.
You can copy it from the Pull Secret section of https://console.redhat.com/openshift/create/local.
? Please enter the pull secret ********************************************************************************

WARN Cannot add pull secret to keyring: The name org.freedesktop.secrets was not provided by any .service files
 
INFO Creating CRC VM for OpenShift 4.17.7...

Additional context

No response

@rohanKanojia rohanKanojia added the kind/bug Something isn't working label Jan 6, 2025
@rohanKanojia
Copy link
Contributor Author

originally posted by @anjannath in internal chat:

KDE wallet can also work as a secret service provider, there was a settings in KDEwallet to enable this
from the Arch wiki:
Enable the Secret Service interface. There are two ways to do this: Go to System Settings > KDE Wallet and enable Use KWallet for the Secret Service interface

After configuring it like this I observed that CRC is correctly adding secret in KDE wallet.

@rohanKanojia rohanKanojia reopened this Jan 6, 2025
@rohanKanojia rohanKanojia closed this as not planned Won't fix, can't repro, duplicate, stale Jan 6, 2025
@cfergeau
Copy link
Contributor

cfergeau commented Jan 6, 2025

Might be worth documenting somewhere

@rohanKanojia
Copy link
Contributor Author

rohanKanojia commented Jan 6, 2025

I have a PR open that's related to this issue crc-org/docs#15. Let me try to add it there .

edit:

Added abovementioned steps as a NOTE in crc-org/docs#15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants