On Mon, Oct 14, 2019 at 05:47:04PM +0200, Thomas Goirand wrote:
> The /etc/hosts isn't getting updated by cloud-init.
> Normally, the hostname of the VM should appear there
> after boot.
Please explain what the /etc/hosts update fixes. All the environments
do DNS for exactly this name.
Bastian
On Mon, Oct 14, 2019 at 07:13:34PM +0200, Thomas Goirand wrote:
> On 10/14/19 5:58 PM, Bastian Blank wrote:
> > Which exact image did you use? What is the log output?
> Both the daily generic and genericcloud image have the issue.
> Logs attached.
The log shows:
> 2019-10-14 15:58:52,057 -
On 10/14/19 5:58 PM, Bastian Blank wrote:
> Control: reassign -1 cloud-init
>
> On Mon, Oct 14, 2019 at 05:47:04PM +0200, Thomas Goirand wrote:
>> The /etc/hosts isn't getting updated by cloud-init.
>> Normally, the hostname of the VM should appear there
>> after boot.
>
> This is handled by
Package: cloud.debian.org
Severity: normal
Not only backports are activated (they should not be there at all...),
but they are activated twice:
- once in /etc/apt/sources.list
- once in /etc/apt/sources.list.d/backport.list
Please remove backports completely from the image.
Thomas
Processing control commands:
> reassign -1 cloud-init
Bug #942325 [cloud.debian.org] /etc/hosts not updated in the generic image
Bug reassigned from package 'cloud.debian.org' to 'cloud-init'.
Ignoring request to alter found versions of bug #942325 to the same values
previously set
Ignoring
Control: reassign -1 cloud-init
On Mon, Oct 14, 2019 at 05:47:04PM +0200, Thomas Goirand wrote:
> The /etc/hosts isn't getting updated by cloud-init.
> Normally, the hostname of the VM should appear there
> after boot.
This is handled by cloud-init.
Which exact image did you use? What is the
Package: cloud.debian.org
Severity: normal
The /etc/hosts isn't getting updated by cloud-init.
Normally, the hostname of the VM should appear there
after boot.
