Description of problem: Version-Release number of selected component (if applicable): $ rpm -qa | egrep '(python26|euca)' python26-libs-2.6.5-6.el5 euca2ools-1.3.1-8.el5 python26-2.6.5-6.el5 python26-boto-2.0-0.1.b4.el5 python26-m2crypto-0.21.1-3.el5 How reproducible: Always Steps to Reproduce: 1. $ euca-authorize -P tcp -p 22 -s 0.0.0.0/0 default default None None tcp 22 22 0.0.0.0/0 Warning: failed to parse error message from AWS: <unknown>:1:0: syntax error EC2ResponseError: 400 Bad Request Failure: 400 Bad Request Failed to bind the following fields: IpPermissions.1.IpProtocol = tcp IpPermissions.1.ToPort = 22 IpPermissions.1.IpRanges.1.CidrIp = 0.0.0.0/0 IpPermissions.1.FromPort = 22 2. 3. Actual results: All other commands seem to work ok on RHEL5, but the above fails for me for a test setup with eucalyptus demo cloud. It works ok on RHEL6 and that's what I use now for the daily work. Expected results: Additional info:
(In reply to comment #0) > Steps to Reproduce: > $ euca-authorize -P tcp -p 22 -s 0.0.0.0/0 default > default None None tcp 22 22 0.0.0.0/0 > Warning: failed to parse error message from AWS: <unknown>:1:0: syntax error > EC2ResponseError: 400 Bad Request > Failure: 400 Bad Request > Failed to bind the following fields: > IpPermissions.1.IpProtocol = tcp > IpPermissions.1.ToPort = 22 > IpPermissions.1.IpRanges.1.CidrIp = 0.0.0.0/0 > IpPermissions.1.FromPort = 22 > > Actual results: > > All other commands seem to work ok on RHEL5, but the above fails for me > for a test setup with eucalyptus demo cloud. It works ok on RHEL6 and that's > what I use now for the daily work. Thanks for your report. Does the same command happen to work when you run it against EC2? It might be a Eucalyptus bug if it only fails when run against Eucalyptus.
I won't be able to run this against EC2, so the only info is that rhel6 works, but rhel5 is currently broken. Server side remains untested. best regards, Florian La Roche
This is an Eucalyptus bug. I executed above command using CentOS 5 without issues against EC2. $ euca-authorize -P tcp -p 22 -s 0.0.0.0/0 default default None None tcp 22 22 0.0.0.0/0 InvalidPermission.Duplicate: The permission '0.0.0.0/0-1-22-22' has already been authorized on the specified group $ euca-authorize -P tcp -p 23 -s 0.0.0.0/0 default default None None tcp 23 23 0.0.0.0/0 GROUP default PERMISSION default ALLOWS tcp 23 23 FROM CIDR 0.0.0.0/0 $ rpm -qa | egrep '(python26|euca)' python26-2.6.5-6.el5 python26-m2crypto-0.21.1-3.el5 python26-boto-2.0-0.1.b4.el5 python26-libs-2.6.5-6.el5 euca2ools-1.3.1-8.el5
(In reply to comment #3) > This is an Eucalyptus bug. I executed above command using CentOS 5 without > issues against EC2. It seems that Eucalyptus 2.0 only supports parameters like "FromPort=22" but not new-style parameters like "IpPermissions.1.FromPort=22", which is what Boto 2.0 sends. Boto's upstream seems to have only tested against Eucalyptus nightlies.
euca2ools-1.3.1-9.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/euca2ools-1.3.1-9.el5
euca2ools-1.3.1-9.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.