[Bug 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist

[Martin Pitt]

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 -t ubuntu-cloud -n trusty-cloud -- -r trusty

but I created that on saucy, with trusty's cloud-image-utils (as saucy's
doesn't find the armhf images). Perhaps that was the reason why it
picked up an ancient cloud image. Is it possible to get a recent one
with saucy's lxc-create, or should I upgrade the whole box to current
trusty?

-- 
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 not
  exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+subscriptions