incus remote add --auth-type oidc unable to create the configuration file error

[rgl]

Required information

• Distribution: Debian
• Distribution version: 12
• The output of "incus info" or if that fails:
  • Kernel version: Linux pandora 6.1.0-16-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.67-1 (2023-12-12) x86_64 GNU/Linux
  • LXC version: N/A
  • Incus version: 0.4
  • Storage backend in use: btrfs

Issue description

When executing the incus remote add incus.test --auth-type oidc command in a machine without the ~/.config directory, the following error is displayed:

vagrant@pandora:~$ ll
total 24
drwx------ 3 vagrant vagrant 4096 dez 29 12:11 ./
drwxr-xr-x 3 root    root    4096 dez 22 07:41 ../
-rw-r--r-- 1 vagrant vagrant  220 dez 22 07:41 .bash_logout
-rw-r--r-- 1 vagrant vagrant 3526 dez 22 07:41 .bashrc
-rw-r--r-- 1 vagrant vagrant  807 dez 22 07:41 .profile
drwx------ 2 vagrant vagrant 4096 dez 29 12:11 .ssh/
-rw-r--r-- 1 vagrant vagrant    0 dez 22 07:42 .sudo_as_admin_successful

vagrant@pandora:~$ incus remote add incus.test --auth-type oidc
URL: https://pandora.incus.test:8443/realms/pandora/device?user_code=HODQ-QPSB
Code: HODQ-QPSB

Error: Unable to create the configuration file: open /home/vagrant/.config/incus/config.yml: no such file or directory

Please note that running with --debug did not display anything related to the directory creation.

Workaround: Manually create the .config/incus directory before calling incus.

Steps to reproduce

1. See the description.

Information to attach

• Any relevant kernel output (dmesg)
• Container log (incus info NAME --show-log)
• Container configuration (incus config show NAME --expanded)
• Main daemon log (at /var/log/incus/incusd.log)
• Output of the client with --debug
• Output of the daemon with --debug (alternatively output of incus monitor --pretty while reproducing the issue)

[stgraber]

Could you check what happens if you only create .config and not .config/incus?

I know we have some logic to create the directory if missing, but it may be assuming that some of the default XDG directories are already present.

[rgl]

I have to create both directories.

[stgraber]

I've tried using my root user here to get a user where I don't care about .config but I've been unable to reproduce the issue:

root@castiana:~# rm -Rf .config/
root@castiana:~# incus remote add test cluster.dcmtl.stgraber.org
To start your first container, try: incus launch images:ubuntu/22.04
Or for a virtual machine: incus launch images:ubuntu/22.04 --vm

Generating a client certificate. This may take a minute...
URL: https://services.stgraber.org/oidc/realms/master/device?user_code=WMMS-LUKR
Code: WMMS-LUKR

root@castiana:~# incus remote^C
root@castiana:~# rm -Rf .config/
root@castiana:~# incus remote add test cluster.dcmtl.stgraber.org --auth-type oidc
To start your first container, try: incus launch images:ubuntu/22.04
Or for a virtual machine: incus launch images:ubuntu/22.04 --vm

URL: https://services.stgraber.org/oidc/realms/master/device?user_code=PHFP-ZCOG
Code: PHFP-ZCOG

root@castiana:~# 

[stgraber]

Oh, is that a system that only has incus-client installed?

[stgraber]

I suspect that's the case as that would trigger a code path that would lead to what you're reporting.

[rgl]

Indeed, it only has the client installed.