Adding a simple condition seems to do the work:

The current fix is necessary, but it's not complete.

The problem exists because, in the latest builds, the config.boot.default file was moved to /usr/share/vyos/config.boot.default. Therefore, when Cloud-init searches for one of the config files to apply the initial configuration, it cannot find any - neither the main nor the default file.

Since the problem was resolved by Proxmox, we will skip this one task.

The problem is in the regex filter: https://github.com/vyos/vyos-1x/blob/3710c5879f5733d05aae6e156f74d62b73821b2d/interface-definitions/system_login.xml.in#L193

I think, a new command is required for this show integrity or similar. Also a brief status in MOTD and show version.

A workaround doe DHCP client to make it work again: https://github.com/vyos/vyos-1x/pull/4002

I agree, the logic in a template seems to be wrong.

PR for current: https://github.com/vyos/vyos-cloud-init/pull/78

PR for 1.4: https://github.com/vyos/vyos-1x/pull/3806

PR for current: https://github.com/vyos/vyos-1x/pull/3776

The only reason I see why this can happen is that the config.boot format can be unexpected. But this should not happen anymore, because now Cloud-init always runs migrations before doing any work, which should always add required metadata if the original file is a valid VyOS config.

I tend to say that this is not necessary and very dangerous. These modules can easily destroy the VyOS filesystem when used improperly.

PR for 1.5: https://github.com/vyos/vyos-build/pull/654

PR for 1.5: https://github.com/vyos/vyos-1x/pull/3592

PR for 1.5: https://github.com/vyos/vyos-build/pull/638

@jestabro could it be that the validator needs an update to allow special characters in the user/password field?
https://github.com/vyos/vyos-utils/blob/0d57cc9a266fe8d6fc87df5a769f42b4a45c7221/src/url.ml

@thannaske it would be very nice if you could re-check now this with VyOS 1.5. It should be fixed by https://github.com/vyos/vyos-cloud-init/commit/70304ff90d931265cb736ace692967242c9b9729

By looking at this and the documentation, I do not see any proofs that flowtables support any encapsulation except VLAN and PPPOE.

PR for 1.5: https://github.com/vyos/vyos-build/pull/579

Should be fixed by https://github.com/vyos/vyos-cloud-init/commit/fd8c12784127e3258762d0163455d595b427ea53

This is closed now because the required functionality perfectly works with Cloud-init + NoCloud/ConfigDrive.

Workaround for clouds introduced in:
https://github.com/vyos/vyos-cloud-init/pull/68
https://github.com/vyos/vyos-cloud-init/pull/69

PR for 1.5: https://github.com/vyos/vyos-build/pull/476

PR for 1.5: https://github.com/vyos/vyos-build/pull/469