@Lain, thanks for taking the time to file this bug.
from the collected ds-identify.log file we have
DMI_PRODUCT_NAME=VC2
DMI_SYS_VENDOR=Vultr
Assuming Vultr puts this DMI_SYS_VENDOR in reliably , then we can use this to
identify Vultr and squelch the warning.
Alternatively, we could add a vultr specific datasource. At first read, it
appears that vultr runs a ec2 lookalike service, but also has its own native
metadata service with 'v1' in the path..
@Lain, thanks for taking the time to file this bug.
from the collected ds-identify.log file we have
DMI_PRODUCT_ NAME=VC2 VENDOR= Vultr
DMI_SYS_
Assuming Vultr puts this DMI_SYS_VENDOR in reliably , then we can use this to
identify Vultr and squelch the warning.
Alternatively, we could add a vultr specific datasource. At first read, it
appears that vultr runs a ec2 lookalike service, but also has its own native
metadata service with 'v1' in the path..
Further reading:
https:/ /www.vultr. com/metadata/ /www.vultr. com/api/ #server_ create /www.vultr. com/docs/ getting- started- with-cloud- init /discuss. vultr.com/ discussion/ 2132/how- to-access- userdata
https:/
https:/
https:/