** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: diablo-4 => 2011.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739815
Title:
euca-authorize and
** Changed in: nova
Milestone: None => diablo-4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739815
Title:
euca-authorize and euca-revoke throws unknown error for invalid port
range
To manag
** Changed in: nova
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739815
Title:
euca-authorize and euca-revoke throws unknown error for invalid port
range
** Changed in: nova
Assignee: (unassigned) => John Tran (jtran)
** Branch linked: lp:~jtran/nova/lp739815
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739815
Title:
euca-authorize and euca-re
Ah, i copied and pasted the entry from the description which contained a
"-" infront of the port. This is obviously invalid syntax.
With correct syntax, it does indeed return as described:
$ euca-authorize -P tcp -p 22 -s 0.0.0.0/0 default
default None None tcp 22 22 0.0.0.0/0
Unknown
Using boto 2.0, this doesn't seem to reach nova and returns a less than
desirable error. Therefore opening a boto task, as this should be
resolved with both client and server.
$ euca-authorize -P tcp -p -22 -s 0.0.0.0/0 default
Traceback (most recent call last):
File "/usr/bin/euca-authoriz
