From de5356b15247cebe142e4179aa1a41a941b8b6b2 Mon Sep 17 00:00:00 2001 From: Olivier Gayot Date: Mon, 7 Oct 2024 18:19:47 +0200 Subject: [PATCH] storage: log disk-id in POST /storage/v2/add_boot_partition It seems that we have a strange behavior when /storage/v2/add_boot_partition is called on a disk different from the disk partitioned for installation. However, we did not log the disk ID so post-mortem analysis is very hard. Signed-off-by: Olivier Gayot --- subiquity/server/controllers/filesystem.py | 1 + 1 file changed, 1 insertion(+) diff --git a/subiquity/server/controllers/filesystem.py b/subiquity/server/controllers/filesystem.py index e5aba6c2e..69f8e2694 100644 --- a/subiquity/server/controllers/filesystem.py +++ b/subiquity/server/controllers/filesystem.py @@ -1327,6 +1327,7 @@ async def v2_reformat_disk_POST(self, data: ReformatDisk) -> StorageResponseV2: return await self.v2_GET() async def v2_add_boot_partition_POST(self, disk_id: str) -> StorageResponseV2: + log.debug("v2_add_boot_partition: disk-id: %s", disk_id) self.locked_probe_data = True disk = self.model._one(id=disk_id) if boot.is_boot_device(disk):