If OIDC Provider is a VM on the Server, LXD will not start

1

Good Evening,

I restarted the Server after an update, first time since setting up OIDC Connection for API calls for LXD. Well, the OIDC Provider is a VM on the System. I cannot boot up the OIDC Provider, cause LXD is failing.

Is there a way to modify the LXD Config Directly?

Aug 05 21:01:30 asgard systemd[1]: Starting LXD Container Hypervisor...
Aug 05 21:01:31 asgard lxd[14571]: time="2023-08-05T21:01:31-04:00" level=warning msg="AppArmor support has been disabled because of lack of kernel support"
Aug 05 21:01:31 asgard lxd[14571]: time="2023-08-05T21:01:31-04:00" level=warning msg=" - AppArmor support has been disabled, Disabled because of lack of kernel support"
Aug 05 21:01:31 asgard lxd[14571]: time="2023-08-05T21:01:31-04:00" level=warning msg=" - Couldn't find the CGroup hugetlb controller, hugepage limits will be ignored"
Aug 05 21:01:31 asgard lxd[14571]: time="2023-08-05T21:01:31-04:00" level=warning msg=" - Couldn't find the CGroup network priority controller, network priority will be ignored"
Aug 05 21:02:22 asgard lxd[14571]: time="2023-08-05T21:02:22-04:00" level=error msg="Failed to start the daemon" err="Failed calling OIDC discovery endpoint: Get \"https://auth.signy./applic>
Aug 05 21:02:22 asgard lxd[14571]: Error: Failed calling OIDC discovery endpoint: Get "https://auth.signy/application/o/lxd/.well-known/openid-configuration": dial tcp 172.18.5.137:443: i/o>
Aug 05 21:02:22 asgard systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
~
3

I was able to resolve it with the following

sqlite3 global/db.bin .dump |grep oidc
sqlite3 local.db .dump |grep oidc

Which produced the following

INSERT INTO config VALUES(2,'oidc.issuer','https://auth.signy/application/o/lxd/');
INSERT INTO config VALUES(3,'oidc.client.id','78b1c680d40a5560d0a429d384dfbc7013e1bc6b');

I was able to fix it by creating two files.
patch.local.sql
patch.global.sql
and adding the following into it

delete from config where id = 2;
delete from config where id = 3"

This got the Servers back up, but now cannot perform remote commands.