You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Ramesh A (JIRA)" <ji...@apache.org> on 2012/06/12 08:43:42 UTC
[jira] [Created] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Ramesh A created DTACLOUD-231:
---------------------------------
Summary: Clicking on "Create new load balancer" button in Web-ui throws error on page
Key: DTACLOUD-231
URL: https://issues.apache.org/jira/browse/DTACLOUD-231
Project: DeltaCloud
Issue Type: Bug
Components: Client (Ruby), Server
Environment: OS- RHEL 6.2, Fedora 16
[root@server ~]# rpm -qa| grep deltacloud
deltacloud-core-ec2-0.6.0-2.el6.noarch
deltacloud-core-0.6.0-2.el6.noarch
deltacloud-core-all-0.6.0-2.el6.noarch
deltacloud-core-rhevm-0.6.0-2.el6.noarch
deltacloud-core-doc-0.6.0-2.el6.noarch
deltacloud-core-vsphere-0.6.0-2.el6.noarch
Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
Reporter: Ramesh A
Clicking on "Create new load balancer" button in web-ui throws error on page
Reproduction Steps:
===============
Navigate to the Load Balancer module and click on the "Create new load balancer" button
Result:
======
1. Displays Error on page (Refer LB-Error.png)
2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
Log Trace:
========
10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
<ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
<Error>
<Type>Sender</Type>
<Code>LoadBalancerNotFound</Code>
</Error>
<RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
</ErrorResponse>
#####
W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
REQUEST ID=-undefined-
/usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
/usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
/usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
/usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
/usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
/usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
/usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
/usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
/usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
/usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
/usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Marios Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou resolved DTACLOUD-231.
-------------------------------------
Resolution: Fixed
pushed to master following qe ack. commit hash:
a6876a9675847af85ba0290c081479903fbb8367
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Marios Andreou
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Marios Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou updated DTACLOUD-231:
------------------------------------
Attachment: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch
please test using attached patch - also fixes issues with various nits with 'register', 'unregister' and 'delete' load balancers. Please check this functionality - should be ok now.
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Marios Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou updated DTACLOUD-231:
------------------------------------
Attachment: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch
ok - latest attached patch should resolve this issue - please test.
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Marios Andreou
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Marios Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou updated DTACLOUD-231:
------------------------------------
Attachment: (was: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch)
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Marios Andreou
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Ramesh A (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh A reassigned DTACLOUD-231:
---------------------------------
Assignee: Marios Andreou (was: Ramesh A)
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Marios Andreou
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Marios Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou reassigned DTACLOUD-231:
---------------------------------------
Assignee: Ramesh A
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Ramesh A
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Marios Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou reassigned DTACLOUD-231:
---------------------------------------
Assignee: Ramesh A (was: Marios Andreou)
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Ramesh A
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Ramesh A (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh A reassigned DTACLOUD-231:
---------------------------------
Assignee: Marios Andreou (was: Ramesh A)
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Marios Andreou
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Ramesh A (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh A updated DTACLOUD-231:
------------------------------
Attachment: LB-Error.png
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Attachments: LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Marios Andreou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou closed DTACLOUD-231.
-----------------------------------
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Marios Andreou
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Ramesh A (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293505#comment-13293505 ]
Ramesh A commented on DTACLOUD-231:
-----------------------------------
Verified and working fine with the patch "0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch".
Ack'd to merger to the master
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Ramesh A
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-231) Clicking on "Create new load
balancer" button in Web-ui throws error on page
Posted by "Ramesh A (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293479#comment-13293479 ]
Ramesh A commented on DTACLOUD-231:
-----------------------------------
Hi Marios,
I am able to navigate to the next page. However when in try to create a new loadbalancer by giving the relevant details, following things happen
1. The web page does not change ( it will still in create new loadbalancer page)
2. The loadbalancer get created at the backend
3. Response code 500 show in the log. Refer the below mentioned stack trace for further information
Stack Trace:
==========
I, [2012-06-12T15:03:18.703501 #22189] INFO -- : New Aws::Elb using per_thread-connection mode
I, [2012-06-12T15:03:18.709172 #22189] INFO -- : Creating LoadBalancer called dc-lb-test
I, [2012-06-12T15:03:18.711216 #22189] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
I, [2012-06-12T15:03:20.683469 #22189] INFO -- : New Aws::Elb using per_thread-connection mode
I, [2012-06-12T15:03:20.684503 #22189] INFO -- : Describing Load Balancers
I, [2012-06-12T15:03:21.119020 #22189] INFO -- : New Aws::Ec2 using per_thread-connection mode
I, [2012-06-12T15:03:21.125503 #22189] INFO -- : Opening new HTTPS connection to ec2.us-east-1.amazonaws.com:443
I, [2012-06-12T15:03:22.903975 #22189] INFO -- : New Aws::Ec2 using per_thread-connection mode
I, [2012-06-12T15:03:23.341805 #22189] INFO -- : New Aws::Ec2 using per_thread-connection mode
/home/rananda/deltacloud/server/lib/deltacloud/./collections/load_balancers.rb:52: warning: Object#id will be deprecated; use Object#object_id
NoMethodError - undefined method `each' for nil:NilClass:
/home/rananda/deltacloud/server/lib/deltacloud/./../../views/load_balancers/show.html.haml:19:in `evaluate_source'
/usr/lib/ruby/gems/1.8/gems/tilt-1.3.3/lib/tilt/template.rb:144:in `cached_evaluate'
/usr/lib/ruby/gems/1.8/gems/tilt-1.3.3/lib/tilt/template.rb:127:in `evaluate'
/usr/lib/ruby/gems/1.8/gems/tilt-1.3.3/lib/tilt/haml.rb:24:in `evaluate'
/usr/lib/ruby/gems/1.8/gems/tilt-1.3.3/lib/tilt/template.rb:76:in `render'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:636:in `render_without_format'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_accept.rb:32:in `render'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:532:in `haml'
/home/rananda/deltacloud/server/lib/deltacloud/./collections/load_balancers.rb:56
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_accept.rb:92:in `call'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_accept.rb:92:in `respond_to'
/home/rananda/deltacloud/server/lib/deltacloud/./collections/load_balancers.rb:53
/usr/lib/ruby/gems/1.8/gems/sinatra-rabbit-1.0.5/lib/sinatra/./rabbit/base.rb:311:in `instance_eval'
/usr/lib/ruby/gems/1.8/gems/sinatra-rabbit-1.0.5/lib/sinatra/./rabbit/base.rb:311:in `POST /api/load_balancers'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1211:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1211:in `compile!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `[]'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:801:in `route_eval'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:822:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:820:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:820:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:784:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:783:in `each'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:783:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/showexceptions.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/showexceptions.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/showexceptions.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/showexceptions.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/showexceptions.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:766:in `forward'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:835:in `route_missing'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:796:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:792:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/showexceptions.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:in `call'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_accept.rb:155:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/showexceptions.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.4/lib/rack/accept/context.rb:22:in `call'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_driver_select.rb:45:in `call'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_matrix_params.rb:104:in `call'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_etag.rb:41:in `call'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_date.rb:31:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/commonlogger.rb:20:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1416:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/urlmap.rb:64:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/urlmap.rb:49:in `each'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/urlmap.rb:49:in `call'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_driver_select.rb:45:in `call'
/home/rananda/deltacloud/server/lib/deltacloud/../sinatra/rack_matrix_params.rb:104:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/builder.rb:134:in `call'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:80:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:78:in `catch'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:78:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `call'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `initialize'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `new'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1049:in `defer'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:50:in `process'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:38:in `receive_data'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/backends/base.rb:61:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/server.rb:159:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/controllers/controller.rb:86:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:185:in `send'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:185:in `run_command'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:151:in `run!'
./bin/deltacloudd:239
127.0.0.1 - - [12/Jun/2012 15:03:24] "POST /api/load_balancers HTTP/1.1" 500 516274 5.4781
> Clicking on "Create new load balancer" button in Web-ui throws error on page
> ----------------------------------------------------------------------------
>
> Key: DTACLOUD-231
> URL: https://issues.apache.org/jira/browse/DTACLOUD-231
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: OS- RHEL 6.2, Fedora 16
> [root@server ~]# rpm -qa| grep deltacloud
> deltacloud-core-ec2-0.6.0-2.el6.noarch
> deltacloud-core-0.6.0-2.el6.noarch
> deltacloud-core-all-0.6.0-2.el6.noarch
> deltacloud-core-rhevm-0.6.0-2.el6.noarch
> deltacloud-core-doc-0.6.0-2.el6.noarch
> deltacloud-core-vsphere-0.6.0-2.el6.noarch
> Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
> Reporter: Ramesh A
> Assignee: Ramesh A
> Attachments: 0001-Fixes-JIRA-DTACLOUD_231-Load-balancers-in-the-HTML-U.patch, LB-Error.png
>
>
> Clicking on "Create new load balancer" button in web-ui throws error on page
> Reproduction Steps:
> ===============
> Navigate to the Load Balancer module and click on the "Create new load balancer" button
> Result:
> ======
> 1. Displays Error on page (Refer LB-Error.png)
> 2. Displays error in the Terminal (400 Bad Request from aws and 404 from dc. Refer the log trace for more information)
> Log Trace:
> ========
> 10.11.11.173 - - [11/Jun/2012 13:54:22] "GET /api/load_balancers HTTP/1.1" 200 2268 0.4523
> I, [2012-06-11T13:54:24.480226 #12342] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-06-11T13:54:24.480420 #12342] INFO -- : Describing Load Balancers
> I, [2012-06-11T13:54:24.481789 #12342] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> W, [2012-06-11T13:54:24.575247 #12342] WARN -- : ##### Aws::Elb returned an error: 400 Bad Request
> <ErrorResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2009-05-15/">
> <Error>
> <Type>Sender</Type>
> <Code>LoadBalancerNotFound</Code>
> </Error>
> <RequestId>7b079b76-b3ee-11e1-97e0-87e352f27191</RequestId>
> </ErrorResponse>
> #####
> W, [2012-06-11T13:54:24.579379 #12342] WARN -- : ##### Aws::Elb request: elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D ####
> I, [2012-06-11T13:54:24.580312 #12342] INFO -- : Closing HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443, reason: 'Aws::AWSErrorHandler: code: 400: 'Bad Request', probability: 10%'
> Aws::AwsError:400: Bad Request (elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D)
> REQUEST=elasticloadbalancing.us-east-1.amazonaws.com:443/?AWSAccessKeyId=AKIAIPXNUEQVP32G4T2A&Action=DescribeLoadBalancers&LoadBalancerNames.member.1=new&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2012-06-11T17%3A54%3A24.000Z&Version=2009-05-15&Signature=RlaBR0HrISoM9x1QGIG6ykYKuswLDaBwKjvXt8ahFTc%3D
> REQUEST ID=-undefined-
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:572:in `request_info_impl'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:316:in `request_info2'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:59:in `request_info'
> /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/elb/elb_interface.rb:161:in `describe_load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:363:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:362:in `load_balancers'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/ec2/ec2_driver.rb:354:in `load_balancer'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `send'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/deltacloud_helper.rb:74:in `show'
> 10.11.11.173 - - [11/Jun/2012 13:54:24] "GET /api/load_balancers/new HTTP/1.1" 404 18 0.1110
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira