Martin Pitt [02/06/2014 11:18 PM]
> Robert C Jennings [2014-02-06 20:57 -]:
>> Fix is included in 20140125 daily build of raring.
>
> I presume/hope you mean trusty here :-)
Yes, trusty too. :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
Thanks for the fix!
Robert C Jennings [2014-02-06 20:57 -]:
> Fix is included in 20140125 daily build of raring.
I presume/hope you mean trusty here :-)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https:/
Fix is included in 20140125 daily build of raring.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1273205
Title:
/etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
This is added by the cloud image build process and should be resolved
in the next build. Fix was committed to
lp:~ubuntu-on-ec2/vmbuilder/automated-ec2-builds revision #578 and
#579. With this change the getty will only be started if 'stty -F
/dev/
Yes, I never thought of it as an LXC bug in the first place. Whatever
installs that job (cloud-init? our cloud image build process?) ought to
change the upstart job to only start up if such a device exists in the
first place.
--
You received this bug notification because you are a member of Ubunt
lxc-start-ephemeral doesn't attach to /dev/console but to /dev/tty1
which is why you don't see the boot messsages or that error.
Unfortunately there isn't a great deal we can do about this in LXC, the
best fix is to change the upstart job to only start with "and not-
container". A better fix would
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1273205
Title:
/etc/init/ttyAMA0.conf causes endless tty
Ah, thanks for pointing out /etc/cloud/build.info. In said chroot that
says
build_name: server
serial: 20131219.1
Note that I created this container last Thursday (2014-01-23), I already
wondered why there were a gazillion packages to dist-upgrade right after
I created it with
sudo lxc-create
Another observation: I still see these messages today after dist-
upgrading to container to latest trusty. But *only* with lxc-start,
*not* with lxc-start-ephemeral. In the latter case, the job still gets
started:
$ sudo status ttyAMA0
ttyAMA0 start/running, process 769
but I don't see the spewag
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1273205
Title:
/etc/init/ttyAMA0.conf causes endless tt
Martin,
Can you confirm the contents of /etc/cloud/build.info? New cloud images
have a test to make sure that this sort of thing shouldn't happen. Also
I am a bit concerned that this might be an issue with upstart
determiniing if its in a container. The previous version should have
prevented the j
The problem can be mitigated by deleting /etc/init/ttyAMA0.conf or
editing to contain the following:
# ttyAMA0 - getty
#
# This service maintains a getty on ttyAMA0 from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345] and (
not-contai
12 matches
Mail list logo
