On 2/13/20 12:44 PM, Christian Tramnitz wrote:
> Is there any progress in getting 19.3 into stable? I can see it was not
> part of the Buster 10.3 release.
> If this takes any longer I'd suggest to backport the initially mentioned
> patch.
>
>
> BR,
> Christian
We currently don't have any ans
Is there any progress in getting 19.3 into stable? I can see it was not
part of the Buster 10.3 release.
If this takes any longer I'd suggest to backport the initially mentioned
patch.
BR,
Christian
OnTue, 31. Dez. 2019 at 16:57 Uhr Thomas Goirand wrote:
> This is included in cloud-init 19.
On 12/31/19 1:13 PM, Christian Tramnitz wrote:
> On Tue, 13 Aug 2019 10:04:03 +0200 Bastian Blank wrote:
>> - cloud-init write the config file using a name that is ignored by
>> ifupdown. The filename is "50-cloud-init.cfg" and everything with "-"
>> or "_" in it is ignored. (wtf?)
>
> No, i
On Tue, 13 Aug 2019 10:04:03 +0200 Bastian Blank wrote:
> - cloud-init write the config file using a name that is ignored by
> ifupdown. The filename is "50-cloud-init.cfg" and everything with "-"
> or "_" in it is ignored. (wtf?)
No, it's the other way around:
File names may *only* include
Hi Sven
On Thu, Jun 27, 2019 at 02:38:53PM +0200, Sven Bartscher wrote:
> The specified network-config doesn't seem to have any actual effect on
> what actually happens when the system boots. From what I see,
> cloud-init generates a configuration file from my specified
> configuration in /etc/net
Package: cloud-init
Version: 18.3-6
Severity: normal
I was trying to start a machine with a static network setup using
cloud-init. I supplied cloud-init with the following data on a NoCloud
ISO image:
/meta-data:
instance-id: iid-foo-1
local-hostname: foo
/user-data:
#cloud-config
chpasswd: { ex
6 matches
Mail list logo
