** Branch linked: lp:~cloud-init-dev/cloud-init/maverick
--
t1.micro instances hang on reboot
https://bugs.launchpad.net/bugs/634102
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:ubuntu/cloud-init
--
t1.micro instances hang on reboot
https://bugs.launchpad.net/bugs/634102
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Tags added: server-mrs
--
t1.micro instances hang on reboot
https://bugs.launchpad.net/bugs/634102
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: cloud-init (Ubuntu Maverick)
Milestone: None = ubuntu-10.10
--
t1.micro instances hang on reboot
https://bugs.launchpad.net/bugs/634102
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: cloud-init (Ubuntu Lucid)
Importance: Undecided
Status: New
--
t1.micro instances hang on reboot
https://bugs.launchpad.net/bugs/634102
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Also affects: cloud-init (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Maverick)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu Maverick)
Status: New = Confirmed
** Changed in: cloud-init (Ubuntu Maverick)
** Changed in: cloud-init (Ubuntu Lucid)
Importance: Undecided = High
** Changed in: cloud-init (Ubuntu Lucid)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu Lucid)
Milestone: None = lucid-updates
** Description changed:
Binary package hint: cloud-init
- on Amazon's
This looks like a problem with the block mapping when the AMI is
registered.
After firing up an t1-miro instance, the Metadata shows:
block-device-mapping:
ami: /dev/sda1
ephemeral0: /dev/sda2
root: /dev/sda1
While one that does have an ephemeral mapping shows:
Sorry...the previous comment should read:
After firing up an t1-miro instance with Lucid, the Metadata shows:
block-device-mapping:
ami: /dev/sda1
ephemeral0: /dev/sda2
root: /dev/sda1
While one that does not have an ephemeral mapping shows:
block-device-mapping:
** Description changed:
Binary package hint: cloud-init
- on Amazon's new t1.micro instance type, there is no ephemeral storage at
- all. If you run a ubuntu ebs image on instance type t1.micro and
- reboot, it will not come back up. mountall will wait indefinitely for
- /dev/sda2, which
On Thu, 9 Sep 2010, Ben Howard wrote:
This looks like a problem with the block mapping when the AMI is
registered.
Well, yes, sort of.
All Ubuntu images are registered with '--block-device-mapping' for the
smallest type of the given arch. See lines 391 at [1]. I recently bumped
into this and
** Description changed:
Binary package hint: cloud-init
- on Amazon's new t1. instance type, there is no ephemeral storage at all.
- If you run a ubuntu ebs image on instance type t1.micro and reboot, it
- will not come back up. mountall will wait indefinitely for /dev/sda2,
- which is
** Branch linked: lp:ubuntu/lucid-proposed/cloud-init
** Branch linked: lp:cloud-init
--
t1.micro instances hang on reboot
https://bugs.launchpad.net/bugs/634102
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
13 matches
Mail list logo
