This issue is now being tracked upstream at
http://eucalyptus.atlassian.net/browse/EUCA-2674
Please watch that issue for further updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
This issue is now being tracked upstream at
http://eucalyptus.atlassian.net/browse/EUCA-2674
Please watch that issue for further updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/506332
Title:
Marking Invalid for the Eucalyptus (ubuntu) task, as it seems to be
resolved elsewhere. Please re-open if this is not the case.
Thanks.
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = Invalid
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
Marking Invalid for the Eucalyptus (ubuntu) task, as it seems to be
resolved elsewhere. Please re-open if this is not the case.
Thanks.
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = Invalid
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Incomplete = Won't Fix
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
instead of a list of string for ssh public keys
https://bugs.launchpad.net/bugs/506332
You received this bug notification because you
** Tags added: patch
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
instead of a list of string for ssh public keys
https://bugs.launchpad.net/bugs/506332
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Debdiff looks sane but is for a package in main, so subscribing
sponsors.
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
instead of a list of string for ssh public keys
https://bugs.launchpad.net/bugs/506332
You received this bug notification because you are
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Incomplete = Won't Fix
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
instead of a list of string for ssh public keys
https://bugs.launchpad.net/bugs/506332
You received this bug notification because you
** Tags added: patch
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
instead of a list of string for ssh public keys
https://bugs.launchpad.net/bugs/506332
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Debdiff looks sane but is for a package in main, so subscribing
sponsors.
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
instead of a list of string for ssh public keys
https://bugs.launchpad.net/bugs/506332
You received this bug notification because you are
Okay, so what remains to be fixed in Ubuntu's Eucalyptus package for
this bug?
I see a request from Chris for more information such that Eucalyptus
could solve this.
I'm marking this bug incomplete, for now, as it doesn't appear there's
enough information to solve the Eucalyptus part of this bug
Just to clarify, I am not objecting to fixing the issue in Eucalyptus.
Rather, the information provided in this bug report is not enough for
me to fix it (and I would need someone to provide that information for
me as I don't have an EC2 account). The HTTP response itself would be
good enough.
Just to clarify, I am not objecting to fixing the issue in Eucalyptus.
Rather, the information provided in this bug report is not enough for
me to fix it (and I would need someone to provide that information for
me as I don't have an EC2 account). The HTTP response itself would be
good enough.
We workarounded the issue in ec2-init by supporting both formats. The
issue still stands in eucalyptus, but it's no longer blocking for us (so
set to importance Low). It's more about other tools that might query the
metadata service and could run into the same issue as we did. Even if
it's not
We workarounded the issue in ec2-init by supporting both formats. The
issue still stands in eucalyptus, but it's no longer blocking for us (so
set to importance Low). It's more about other tools that might query the
metadata service and could run into the same issue as we did. Even if
it's not
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: Medium = Low
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
instead of a list of string for ssh public keys
https://bugs.launchpad.net/bugs/506332
You received this bug notification because you are a
Actually, this is not part of any of the EC2 specifications.
If there is a need to change the behaviour of Eucalyptus to remedy
this problem I will need more information about what differs between
the two. That is, the provided output indicates there is a
difference, but neither is the actual
Actually, this is not part of any of the EC2 specifications.
If there is a need to change the behaviour of Eucalyptus to remedy
this problem I will need more information about what differs between
the two. That is, the provided output indicates there is a
difference, but neither is the actual
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: Medium = Low
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
instead of a list of string for ssh public keys
https://bugs.launchpad.net/bugs/506332
You received this bug notification because you are a
** Also affects: ec2-init (Ubuntu Lucid)
Importance: High
Assignee: Scott Moser (smoser)
Status: In Progress
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: Undecided
Status: New
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
Even if the bug is in boto parsing, there is something different in UEC
metadata output, compared to EC2, that makes boto behave differently ?
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu Lucid)
Status: New = Confirmed
--
ec2-init (0.5.0-0ubuntu3) lucid; urgency=low
* work around difference in uec/ec2 metadata service (LP:506332)
-- Scott Moser smo...@ubuntu.com Tue, 12 Jan 2010 11:33:11 -0500
** Changed in: ec2-init (Ubuntu Lucid)
Status: In Progress = Fix Released
--
Can't login with SSH to Lucid
yes, obviously there is something different in the server metadata
output that makes the client parse it different. by definition of api
compatibility, that is a bug in the server. I agree that the parsed
eucalyptus data seems more sane, but thats not something that can be
changed.
--
Can't
** Also affects: ec2-init (Ubuntu Lucid)
Importance: High
Assignee: Scott Moser (smoser)
Status: In Progress
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: Undecided
Status: New
--
Can't login with SSH to Lucid UEC image - uec metadata service returns a string
Even if the bug is in boto parsing, there is something different in UEC
metadata output, compared to EC2, that makes boto behave differently ?
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu Lucid)
Status: New = Confirmed
--
ec2-init (0.5.0-0ubuntu3) lucid; urgency=low
* work around difference in uec/ec2 metadata service (LP:506332)
-- Scott Moser smo...@ubuntu.com Tue, 12 Jan 2010 11:33:11 -0500
** Changed in: ec2-init (Ubuntu Lucid)
Status: In Progress = Fix Released
--
Can't login with SSH to Lucid
yes, obviously there is something different in the server metadata
output that makes the client parse it different. by definition of api
compatibility, that is a bug in the server. I agree that the parsed
eucalyptus data seems more sane, but thats not something that can be
changed.
--
Can't
Not as relevant here, but to point out, there are other differences in the 2
files:
- uec has 'ancestor-ami-ids' field (probably ok)
- ec2 has instance-action
- uec has 'product-codes' . apparently if there are none, ec2 doesn't present
that in the metadata
- the noted public-keys difference
#12:
ancestor-ami-ids are also in ec2 if the image has ancestors.
instance-action is not supported by Eucalyptus at this time (so it is absent).
#11:
The difference between the two outputs posted seems to be a parser issue which
is converting the public-key string into a list. Note the second
Not as relevant here, but to point out, there are other differences in the 2
files:
- uec has 'ancestor-ami-ids' field (probably ok)
- ec2 has instance-action
- uec has 'product-codes' . apparently if there are none, ec2 doesn't present
that in the metadata
- the noted public-keys difference
#12:
ancestor-ami-ids are also in ec2 if the image has ancestors.
instance-action is not supported by Eucalyptus at this time (so it is absent).
#11:
The difference between the two outputs posted seems to be a parser issue which
is converting the public-key string into a list. Note the second
31 matches
Mail list logo
