deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DTACLOUD-231) Clicking on "Create new load balancer" button in Web-ui throws error on page
Date Tue, 12 Jun 2012 11:12:43 GMT

     [ 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

        

Mime
View raw message