** Changed in: eucalyptus (Ubuntu)
Status: Triaged = Fix Released
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Tags added: iso-testing
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Probably an issue in eucalyptus rather than euca2ools, since the same
command works after issuing a group command (and no state is kept
client-side)
** Changed in: euca2ools (Ubuntu)
Status: Incomplete = Invalid
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You
Actually, this bug has been closed a while ago and I can confirm it is
not present in the current trunk. I'm afraid that it was closed
incidentally and I don't know the revno, sorry.
** Changed in: eucalyptus
Status: Confirmed = Fix Released
--
euca-authorize default failing
** Tags added: eucalyptus
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Only first use error, I don't think it warrants a release note entry.
** Changed in: ubuntu-release-notes
Status: New = Invalid
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
Server Team,
If systematic, we might need to document it in the release notes.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
I looks like this bug happens when an authorize is called before the
group is used in another context (run-instances, describe-group, etc).
For example:
euca-authorize (fails)
euca-describe-groups
euca-authorize (success)
Attaching the log file showing exception, and exact commands
**
I am seeing this problem as well. Knowing where to collect debug info
from would help.
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Please check the wire. I'd be interested in what the cloud is
actually responding with (ngrep -d iface -Wbyline port 8773) on the
front end.
It is likely something to do with packaging. I have never seen it with
the source install.
--
euca-authorize default failing
I have ran a capture of the traffic while the error is occuring:
Request:
CGET
Nick,
do you have a server side exception/stack trace?
Are there other exceptions?
Something is definitely not right with the package.
thanks.
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
On Fri, Oct 16, 2009 at 04:56:26PM -, Neil Soman wrote:
Nick,
do you have a server side exception/stack trace?
Are there other exceptions?
Which file(s) should be looked at?
Something is definitely not right with the package.
Note that the error will disappear after some time and
Unfortunately, the only report of an error on the server side is the one
I got from capturing network traffic. As mathias pointed I cannot
reproduce the error anymore...
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
** Changed in: eucalyptus
Status: Confirmed = Incomplete
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
Perusing the /var/log/eucalyptus/cloud-output.log which seems to contain
an interesting stack trace. Attaching the relevant section.
** Attachment added: stacktrace.log
http://launchpadlibrarian.net/33802622/stacktrace.log
** Changed in: eucalyptus
Status: Incomplete = Confirmed
--
I am unable to reproduce this problem. I am using Eucalyptus revno 931
and Euca2ools revno 221.
Perhaps something went wrong in the packaging?
$ euca-authorize default -P tcp -p 22 -s 0.0.0.0/0
GROUP default
PERMISSION default ALLOWS tcp 22 22 FROMCIDR
0.0.0.0/0
$
On Thu, Oct 15, 2009 at 10:42:55PM -, Neil Soman wrote:
I am unable to reproduce this problem. I am using Eucalyptus revno 931
and Euca2ools revno 221.
I've seen that problem as well. But it's not reliably reproducible.
After some time the command succeeds. If that happens again where can
18 matches
Mail list logo
