Weekly news #401

LXD News
,
1

Weekly status for the week of 23rd June to 29th June.

Introduction

This past week, LXD received a series of bug fixes addressing issues with instance migration and copying. The highlight is the added support for using a client secret in the OIDC authorization code flow.

Support for client secret in OIDC authorization code flow

LXD now supports setting oidc.client.secret to enable OIDC authorization code flow with confidential clients.

Please note that oidc.client.secret should only be set if required by the identity provider. The secret is not shared with other LXD clients (such as LXD CLI), which may prevent them from authenticating successfully.

Docs: LXD Docs - OpenID Connect configuration

Bug Fixes

  • Fixed an issue where the source project was incorrectly used instead of the instance’s project during cross-project copy (from Incus).

  • Fixed an issue where instance post migration did not properly cleanup the dnsmasq leases.

  • Fixed an issue where copied VM would be assigned the same IP address as the source VM due to cloud-init not regenerating the DHCP client ID when the VM ID changes. This was fixed for bridge networks by modifying how the DHCP server allocates IPs. It now always uses the client’s MAC address rather than the client’s DHCP client ID.

  • Fixed an issue where limits.memory could not be set to a percentage of the host memory. Behavior is now consistent across VMs and containers (from Incus).

LXD UI

  • Introduced new network details page for displaying active IP leases.

  • Introduced new IPAM page under networks, which unifies IP address management.

  • Added the mac address in the instance detail page.

All changes

The items listed below is all of the work which happened over the past week and which will be included in the next release.

LXD

LXD UI

LXD Charm

  • Nothing to report this week

LXD Terraform provider

  • Nothing to report this week

PyLXD

LXD snap

2 Likes