CloudConfigDrive removal

[Tristis Oris]

I try to get how is this button should work.

only one task at .conf

# Base
hostname: {name}%

sudo journalctl -u cloud-config -f
Feb 11 12:40:14 clonme systemd[1]: Starting cloud-config.service - Cloud-init: Config Stage...
Feb 11 12:40:15 test123 cloud-init[1037]: Cloud-init v. 25.2-0ubuntu1~24.04.1 running 'modules:config' at Wed, 11 Feb 2026 09:40:15 +0000. Up 8.85 seconds.
Feb 11 12:40:15 test123 systemd[1]: cloud-config.service: Main process exited, code=exited, status=1/FAILURE
Feb 11 12:40:15 test123 systemd[1]: cloud-config.service: Failed with result 'exit-code'.
Feb 11 12:40:15 test123 systemd[1]: Failed to start cloud-config.service - Cloud-init: Config Stage.

old hostname at log, but all changes from config is applied to host.

Next run

systemctl status cloud-config
● cloud-config.service - Cloud-init: Config Stage
     Loaded: loaded (/usr/lib/systemd/system/cloud-config.service; enabled; preset: enabled)
     Active: active (exited) since Wed 2026-02-11 12:44:06 MSK; 3min 0s ago
    Process: 787 ExecStart=/usr/bin/cloud-init modules --mode=config (code=exited, status=0/SUCCESS)
   Main PID: 787 (code=exited, status=0/SUCCESS)
        CPU: 362ms

Feb 11 12:44:06 test123 systemd[1]: Starting cloud-config.service - Cloud-init: Config Stage...
Feb 11 12:44:06 test123 cloud-init[936]: Cloud-init v. 25.2-0ubuntu1~24.04.1 running 'modules:config' at Wed, 11 Feb 2026 09:44:06 +0000. Up 7.42 seconds.
Feb 11 12:44:06 test123 systemd[1]: Finished cloud-config.service - Cloud-init: Config Stage.

Few times shutdown, but drive still not removed

After 3rd cycle drive is disappeared.

When i test it with force poweroff, i got error and VM stuck at grey state till next poweroff.
But after this, the drive been removed.

vm.stop
{
  "id": "102e48dd-d6f6-c8a6-7f10-e449fb43dcb2",
  "force": true,
  "bypassBlockedOperation": false
}
{
  "code": "INTERNAL_ERROR",
  "params": [
    "Object with type VM and id 102e48dd-d6f6-c8a6-7f10-e449fb43dcb2/vbd.xvdb does not exist in xenopsd"
  ],
  "task": {
    "uuid": "a345de27-ac17-ab29-c66b-2afd629d724e",
    "name_label": "Async.VM.hard_shutdown",
    "name_description": "",
    "allowed_operations": [],
    "current_operations": {},
    "created": "20260211T09:33:50Z",
    "finished": "20260211T09:33:54Z",
    "status": "failure",
    "resident_on": "OpaqueRef:b31541df-b7c1-27fc-85d0-36a5c1d94242",
    "progress": 1,
    "type": "<none/>",
    "result": "",
    "error_info": [
      "INTERNAL_ERROR",
      "Object with type VM and id 102e48dd-d6f6-c8a6-7f10-e449fb43dcb2/vbd.xvdb does not exist in xenopsd"
    ],
    "other_config": {},
    "subtask_of": "OpaqueRef:NULL",
    "subtasks": [],
    "backtrace": "(((process xapi)(filename ocaml/xapi-client/client.ml)(line 7))((process xapi)(filename ocaml/xapi-client/client.ml)(line 19))((process xapi)(filename ocaml/xapi-client/client.ml)(line 7874))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 144))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2169))((process xapi)(filename ocaml/xapi/rbac.ml)(line 229))((process xapi)(filename ocaml/xapi/rbac.ml)(line 239))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))"
  },
  "message": "INTERNAL_ERROR(Object with type VM and id 102e48dd-d6f6-c8a6-7f10-e449fb43dcb2/vbd.xvdb does not exist in xenopsd)",
  "name": "XapiError",
  "stack": "XapiError: INTERNAL_ERROR(Object with type VM and id 102e48dd-d6f6-c8a6-7f10-e449fb43dcb2/vbd.xvdb does not exist in xenopsd)
    at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202602091212/packages/xen-api/_XapiError.mjs:16:12)
    at default (file:///opt/xo/xo-builds/xen-orchestra-202602091212/packages/xen-api/_getTaskResult.mjs:13:29)
    at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202602091212/packages/xen-api/index.mjs:1078:24)
    at file:///opt/xo/xo-builds/xen-orchestra-202602091212/packages/xen-api/index.mjs:1112:14
    at Array.forEach (<anonymous>)
    at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202602091212/packages/xen-api/index.mjs:1102:12)
    at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202602091212/packages/xen-api/index.mjs:1275:14)"
}

[Tristis Oris]

Also i tried to auto extend drive, but this is only thing which not works. Packages update run without issue.

# nope
resize_rootfs: true
growpart:
  mode: auto
  devices: ['/, /dev/xvda']
  ignore_growroot_disabled: false

# ok
package_update: true
package_upgrade: true

[Pilow]

@Tristis-Oris do you have same issues from HUB templates ?

if not, something like a plugin is missing in your cloudconfig configuration
in CLOUDBASE init on windows, we have to specify some plugins to allow auto extend of disk, never tried a manual linux template creation, as HUB ones are enough for our usage and ready to deploy.