| 2011-11-15 01:13:27 |
Eric Hammond |
bug |
|
|
added bug |
| 2011-11-15 01:25:47 |
Eric Hammond |
description |
cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2011-11-15 01:28:59 |
Eric Hammond |
description |
cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
When running an EC2 instance on Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2011-11-15 01:29:10 |
Eric Hammond |
description |
When running an EC2 instance on Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
When running an EC2 instance of Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2011-11-15 01:30:14 |
Eric Hammond |
description |
When running an EC2 instance of Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache), say:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
When running an EC2 instance of Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache). For example:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2011-11-15 01:31:20 |
Eric Hammond |
description |
When running an EC2 instance of Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache). For example:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
When running an EC2 instance of Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache). For example:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. My web server never comes up after a simple reboot.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2011-11-15 02:02:43 |
Eric Hammond |
bug |
|
|
added subscriber Scott Moser |
| 2011-11-15 02:06:00 |
Eric Hammond |
bug |
|
|
added subscriber Ben Howard |
| 2011-11-15 05:34:53 |
Eric Hammond |
cloud-init (Ubuntu): status |
New |
Incomplete |
|
| 2011-11-15 05:49:35 |
Eric Hammond |
cloud-init (Ubuntu): status |
Incomplete |
Invalid |
|
| 2011-11-15 13:23:54 |
Scott Moser |
cloud-init (Ubuntu): status |
Invalid |
Confirmed |
|
| 2011-11-15 20:40:29 |
Scott Moser |
description |
When running an EC2 instance of Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache). For example:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. My web server never comes up after a simple reboot.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
When running an EC2 instance of Ubuntu 11.10 Oneiric, cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more sense to my internal software (e.g., Apache). For example:
127.0.1.1 myhost.example.com myhost
BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. My web server never comes up after a simple reboot.
Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run.
The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone.
If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value.
Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same.
See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu22
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Nov 15 00:17:46 2011
Ec2AMI: ami-a7f539ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-805ea7e9
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
related bugs:
* bug 871966: FQDN written to /etc/hosts causes problems for clustering systems |
|
| 2011-11-15 20:40:41 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2011-12-20 01:34:45 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2011-12-20 01:34:47 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2011-12-20 03:49:25 |
Launchpad Janitor |
branch linked |
|
lp:cloud-init |
|
| 2011-12-20 03:51:11 |
Scott Moser |
cloud-init: status |
New |
Fix Committed |
|
| 2011-12-20 03:51:11 |
Scott Moser |
cloud-init: assignee |
|
Scott Moser (smoser) |
|
| 2011-12-22 09:10:13 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2011-12-22 09:10:30 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/cloud-init |
|
| 2012-01-10 21:41:54 |
Tom vN |
bug |
|
|
added subscriber Tom vN |
| 2012-04-11 04:09:34 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2023-05-09 18:35:33 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2221 |
|
