Public bug reported:
By default, the NoCloud datasource reports 'nocloud' as the instance-id.
While this can be changed in meta-data, the contents of the file are
often static.
In particular, GNS3 appliances clone their disks from a master template.
The result is that all GNS3 virtual machines cloned from a single
appliance get the same instance-id. In particular, the network doesn't
get reconfigured correctly when a new instance boots.
I suggest adding the ability to obtain the system's UUID, as reported by
dmi-decode -s system-uuid, in a Jinja template that can be used in meta-
data, like this:
#cloud-config
instance-id: {{system-uuid}}
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1974062
Title:
NoCloud instance-id's never change
Status in cloud-init:
New
Bug description:
By default, the NoCloud datasource reports 'nocloud' as the instance-
id.
While this can be changed in meta-data, the contents of the file are
often static.
In particular, GNS3 appliances clone their disks from a master
template.
The result is that all GNS3 virtual machines cloned from a single
appliance get the same instance-id. In particular, the network
doesn't get reconfigured correctly when a new instance boots.
I suggest adding the ability to obtain the system's UUID, as reported
by dmi-decode -s system-uuid, in a Jinja template that can be used in
meta-data, like this:
#cloud-config
instance-id: {{system-uuid}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1974062/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
