This bug was fixed in the package euca2ools - 1.0+bzr20090923-0ubuntu1
---
euca2ools (1.0+bzr20090923-0ubuntu1) karmic; urgency=low
* Upstream bugfix release, fixes LP: #435126, LP: #430093.
-- Thierry CarrezWed, 23 Sep 2009
11:56:45 +0200
** Changed in: euca2ools (Ubuntu Kar
Upstream says it's a euca2ools bug, fixed in latest upstream revs.
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged => Invalid
** Also affects: euca2ools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: euca2ools (Ubuntu Karmic)
Importance: Undecided => High
Might be a euca2ools error, parent of bug 431847. Could you try with ec2
-run-instances instead ?
--
Eucalyptus "403 Forbidden" when trying to run instance
https://bugs.launchpad.net/bugs/430093
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Same error. New install. Also new re-install after much frustration :)
20:31:49 WARN PipelineRegistry | => More than one candidate pipeline.
Ignoring offer by: internal-query-pipeline-Eucalyptus of type
InternalQueryPipeline
com.eucalyptus.ws.AuthenticationException: User authentication
** Also affects: eucalyptus (Ubuntu Karmic)
Importance: High
Status: Triaged
--
Eucalyptus "403 Forbidden" when trying to run instance
https://bugs.launchpad.net/bugs/430093
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
This happens also on fresh installs of 1.6~bzr746-0ubuntu3.
** Summary changed:
- Eucalyptus "403 Forbidden" when trying to run instance after package upgrade
+ Eucalyptus "403 Forbidden" when trying to run instance
** Changed in: eucalyptus (Ubuntu)
Status: New => Triaged
** Changed in:
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => High
** Tags added: eucalyptus
--
Eucalyptus "403 Forbidden" when trying to run instance after package upgrade
https://bugs.launchpad.net/bugs/430093
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Sorry for the double post. I posted this to bug #428010 but Etienne
suggested this might be a better place for it.
I am getting a similar error to this one, here is the exact command line
and error message.
$ euca-run-instances emi-67DC1321 -k mykey
Warning: failed to parse error message from AWS