Marking this invalid against cloud-init, and against linux, although
nothing was done. The bug was fixed in the hypervisor.
** Changed in: cloud-init (Ubuntu Maverick)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Maverick)
Status: Confirmed => Fix Released
--
user
** Visibility changed to: Private
** This bug has been flagged as a security vulnerability
--
user-data is corrupted inside metadata service
https://bugs.launchpad.net/bugs/613083
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubunt
** Also affects: cloud-init (Ubuntu Maverick)
Importance: High
Status: Triaged
** Also affects: linux (Ubuntu Maverick)
Importance: High
Assignee: John Johansen (jjohansen)
Status: Confirmed
** Tags added: server-mro
--
user-data is corrupted inside metadata service
htt
This is not really related to cloud-init, but it "affects" it.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
--
user-data is corrupted inside metadata service
https://bugs.launchpad.net/bugs/613083
You receiv
It is more than trival to test with the latest upstream kernel. John is
working on this bug.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Joha
Hi Scott,
If you could also please test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the 'needs-upstre
Interesting, the user data persisted across a reboot in the above. Ie,
a reboot of the instance, and I still get the corrupted data, and it was
almost identical. There are a couple bytes that were non-text that are
different, but almost identical.
--
user-data is corrupted inside metadata servi
I'm attaching the console output of this instance, as it appears that the dmesg
buffer is getting into the user data.
I'm thinking at this point that this must be kernel related.
** Attachment added: "console from ami-61759e08"
http://launchpadlibrarian.net/53022929/console-ami-61759e08.txt
I've now seen this on
us-east-1 ami-61759e08 ebs/ubuntu-maverick-daily-i386-server-20100803.2
I'm attaching the output here as it is the most interesting of the
bunch.
** Attachment added: "user-data from ec2metadata --user-data"
http://launchpadlibrarian.net/53022527/user-data-ami-61759e08.t
I've now seen this on us-west-1 also.
us-west-1 ami-87d8f2f3 ebs/ubuntu-maverick-daily-i386-server-20100803.2
--
user-data is corrupted inside metadata service
https://bugs.launchpad.net/bugs/613083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: iso-testing
--
user-data is corrupted inside metadata service
https://bugs.launchpad.net/bugs/613083
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
https://lists.u
I opened up a thread in the ec2 forums: http://tinyurl.com/ec2-forums-
lp-613083
--
user-data is corrupted inside metadata service
https://bugs.launchpad.net/bugs/613083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Attachment added: "user-data as provided with --user-data-file"
http://launchpadlibrarian.net/53004256/ud-cloudconfig-01.txt
--
user-data is corrupted inside metadata service
https://bugs.launchpad.net/bugs/613083
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "user-data as seen from inside instance"
http://launchpadlibrarian.net/53004166/user-data
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/53003817/Dependencies.txt
--
user-data is corrupted inside metadata service
https://bugs.launchpad.net/bugs/
14 matches
Mail list logo