+1 I confirmed yesterday as well. subiquity no longer calls cloud-init's stages.Init() when cloud-init is disabled. This was the source of the delay originally which performed all that rediscovery of every cloud-init datasource, including Ec2. Full install with cloud-init disabled on default installs works and we see subiquity correctly claiming cloud-init is disabled.
+1 I confirmed yesterday as well. subiquity no longer calls cloud-init's stages.Init() when cloud-init is disabled. This was the source of the delay originally which performed all that rediscovery of every cloud-init datasource, including Ec2. Full install with cloud-init disabled on default installs works and we see subiquity correctly claiming cloud-init is disabled.