[FEATURE] Missing option to see(/change/clear) if PullSecret is store in credential manager (Windows)

[odockal]

General information

Since I had a crc installed on the machine before, and I thought I did a full clean in order to install new versoin, I suspect that some leftover config where the pull secret file is was left there. So the question is, how do I do a proper clean up.

• Windows
• Hypervisor: Hyper-V
• Did you run crc setup before starting it (Yes/No)? Not myself, extension did initialization
• Running CRC on: Laptop

CRC version

CRC version: 2.24.1+81aeeb
OpenShift version: 4.13.6
Podman version: 4.4.4

CRC status

DEBU CRC version: 2.24.1+81aeeb
DEBU OpenShift version: 4.13.6
DEBU Podman version: 4.4.4
DEBU Running 'crc status'
CRC VM:          Running
OpenShift:       Running (v4.13.6)
RAM Usage:       7.016GB of 9.374GB
Disk Usage:      20.02GB of 32.68GB (Inside the CRC VM)
Cache Usage:     44.03GB
Cache Directory: C:\Users\Ondrej\.crc\cache

CRC config

- consent-telemetry                     : no

Host Operating System

not relevant

Steps to reproduce

Expected

Actual

Logs

Before gather the logs try following if that fix your issue

$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue.
CRC start log from Podman desktop

listening vsock://00000400-FACB-11E6-BD58-64006A7986D3
listening \\.\pipe\crc-http
Checking minimum RAM requirements
Checking if running in a shell with administrator rights
Checking Windows release
Checking Windows edition
Checking if Hyper-V is installed and operational
Checking if Hyper-V service is enabled
Checking if crc-users group exists
Checking if current user is in crc-users and Hyper-V admins group
Checking if vsock is correctly configured
Checking if the daemon task is installed
Checking if the daemon task is running
Checking admin helper service is running
Loading bundle: crc_hyperv_4.13.6_amd64...
Creating CRC VM for OpenShift 4.13.6...
Generating new SSH key pair...
Generating new password for the kubeadmin user
Starting CRC VM for openshift 4.13.6...
Listening on: \\.\pipe\crc-podman
CRC instance is running with IP 127.0.0.1
new connection from 00000000-0000-0000-0000-000002f8ffff:b8badad4-facb-11e6-bd58-64006a7986d3 to 00000000-0000-0000-0000-000000000000:00000400-facb-11e6-bd58-64006a7986d3
CRC VM is running
Updating authorized keys...
Check internal and public DNS query...
Check DNS query from host...
Verifying validity of the kubelet certificates...
Starting kubelet service
Waiting for kube-apiserver availability... [takes around 2min]
Adding user's pull secret to the cluster...
Updating SSH key to machine config resource...
Waiting until the user's pull secret is written to the instance disk...
Changing the password for the kubeadmin user
Updating cluster ID...
Updating root CA cert to admin-kubeconfig-client-ca configmap...
Starting openshift instance... [waiting for the cluster to stabilize]
4 operators are progressing: image-registry, kube-storage-version-migrator, openshift-controller-manager, service-ca
2 operators are progressing: image-registry, openshift-controller-manager
Operator image-registry is progressing
All operators are available. Ensuring stability...
Operators are stable (2/3)...
Operators are stable (3/3)...
Adding crc-admin and crc-developer contexts to kubeconfig...
Stopping kubelet and all containers...
Stopping the instance, this may take a few minutes...
cannot receive packets from 00000000-0000-0000-0000-000002f8ffff:b8badad4-facb-11e6-bd58-64006a7986d3, disconnecting: cannot read size from socket: EOF
Checking minimum RAM requirements
Checking if running in a shell with administrator rights
Checking Windows release
Checking Windows edition
Checking if Hyper-V is installed and operational
Checking if Hyper-V service is enabled
Checking if crc-users group exists
Checking if current user is in crc-users and Hyper-V admins group
Checking if vsock is correctly configured
Checking if the daemon task is running
Checking admin helper service is running
new connection from 00040246-0000-0000-0000-000006a2ffff:01d90653-facb-11e6-bd58-64006a7986d3 to 00000000-0000-0000-0000-000000000000:00000400-facb-11e6-bd58-64006a7986d3
CRC VM is running
Check internal and public DNS query...
Check DNS query from host...
Verifying validity of the kubelet certificates...
Starting kubelet service
Operators are stable (3/3).... [waiting for the cluster to stabilize]

[gbraad]

not following your issue. has this machine run the setup once before, requesting the pull secret? if so, this is stored so we dont keepal asking people. only a fresh install or removal will work here. please check secure storage, like credential manager on windowz

[cfergeau]

crc cleanup should remove it: https://github.com/crc-org/crc/blob/97705a008eda801ba291fe3b9982af464d4759e0/pkg/crc/preflight/preflight_checks_common.go#L63-L69
It calls https://github.com/zalando/go-keyring/blob/b0e756d4fd2ce0775d2482c891194fe34cacfbfa/keyring_windows.go#L49-L60 to do this.

[odockal]

not following your issue. has this machine run the setup once before, requesting the pull secret? if so, this is stored so we dont keepal asking people. only a fresh install or removal will work here. please check secure storage, like credential manager on windowz

Yes, you are right. It was there actually, I did not know about the place. Thx.
Although, user does not have a visibility over that directly from podman desktop nor crc binary or crc config. Is it possible to show it somewhere?

crc cleanup should remove it: https://github.com/crc-org/crc/blob/97705a008eda801ba291fe3b9982af464d4759e0/pkg/crc/preflight/preflight_checks_common.go#L63-L69 It calls https://github.com/zalando/go-keyring/blob/b0e756d4fd2ce0775d2482c891194fe34cacfbfa/keyring_windows.go#L49-L60 to do this.

Great! Thx, will try to get it into my workflow.

[gbraad]

Although, user does not have a visibility over that directly from podman desktop nor crc binary or crc config. Is it possible to show it somewhere?

We do not have this functionality currently in CRC; that would have to be solved first