OpenStack Heat

heat deploying loadbalancer takes more than 600 secs, and the deployment failed

Bug #1240565 reported by Hai Ming Yang
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Low
Daneyon Hansen

Bug Description

AWS::ElasticLoadBalancing::LoadBalancer resource has to be deployed within 600 secs.
it is not possible for my low speed (relatively low) internet connection, since the resource needs to download and install HAProxy to the LB_instance in the nested stack.
then the deployment is failed.

Steve Baker (steve-stevebaker)
Changed in heat:
status: New → Triaged
importance: Undecided → Low
Daneyon Hansen (danehans)
Changed in heat:
assignee: nobody → Daneyon Hansen (danehans)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/93204

Changed in heat:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on heat (master)

Change abandoned by Daneyon Hansen (<email address hidden>) on branch: master
Review: https://review.openstack.org/93204
Reason: Not needed.

Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

Fixed by https://review.openstack.org/#/c/64874

One can easily use a custom template for the AWS loadbalancer resource now, where the desired timeout specific for deployment might be set.

Changed in heat:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.