> > Looking at the output provided, all we can tell is that we're on
> > VMWare, but no indication that it's OpenStack, so cloud-init can't
> > reasonable expect to know that it should enable the OpenStack
> > datasource.
>
> Let me mention again that this bug was introduced in Ubuntu 18.04; previ
https://kb.vmware.com/s/article/74597
https://docs.openstack.org/nova/latest/user/flavors.html#extra-specs
https://kb.vmware.com/s/article/2148863
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185545
Another workaround for people experiencing the same issue is to force
the use of a config drive in OpenStack. This can be done without
involving VIO admins in two ways:
1. Set property `img__config_drive` on the image to `mandatory`.
2. Pass option `--config-drive true` to `openstack server creat
@ Scott thanks a lot, that is very useful! Do I understand correctly
that `smbios.assetTag` is a property of the *flavor*? I cannot seem to
find any image property with the same effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For what its worth, see bug 1669875.
Specifically see comment 7
https://bugs.launchpad.net/cloud-init/+bug/1669875/comments/7 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855458
Title:
cloud-in
> Looking at the output provided, all we can tell is that we're on
> VMWare, but no indication that it's OpenStack, so cloud-init can't
> reasonable expect to know that it should enable the OpenStack
> datasource.
Let me mention again that this bug was introduced in Ubuntu 18.04;
previous versions
Thanks for filing the bug. It's unfortunate that VIO does not identify
that it's running images in OpenStack.
Looking at the output provided, all we can tell is that we're on VMWare,
but no indication that it's OpenStack, so cloud-init can't reasonable
expect to know that it should enable the Ope
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855458
Title:
cloud-init on Ubuntu 18.04 image does not run in VIO
To
I am providing here the additional information that were requested in
https://bugs.launchpad.net/ubuntu/+source/open-vm-
tools/+bug/1760776/comments/17
I'm attaching the collected cloud-init logs; here is the output of
commands.
The Linux kernel correctly determines the hypervisor is VMware (exce
>From the `ds-identify.log` file in the uploaded archive, one can see
that `ds-identify` rejects the `Ec2` metadata source and disables
`cloud-init`:
Running on vmware but rpctool query returned 1: No value found
is_ds_enabled(IBMCloud) = true.
ec2 platform is 'Unknown'.
No ds foun
10 matches
Mail list logo
