New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ELB parsing broken when listeners have applied policies #755
Comments
jimbrowne
added a commit
to jimbrowne/boto
that referenced
this issue
May 16, 2012
Currently fails due to bug boto#755. Should be enhanced to assert on ELB listener policies once they are supported in the Listener object.
jimbrowne
added a commit
to jimbrowne/boto
that referenced
this issue
May 17, 2012
jimbrowne
added a commit
to jimbrowne/boto
that referenced
this issue
May 17, 2012
I found ec228f9 while examining the LoadBalancer objects for this bug. |
Are you going to submit a pull request? It looks like you have a fix in your branch. |
Doh! Thought I had. Just submitted one. |
msabramo
pushed a commit
to msabramo/boto
that referenced
this issue
Nov 28, 2012
Currently fails due to bug boto#755. Should be enhanced to assert on ELB listener policies once they are supported in the Listener object.
msabramo
pushed a commit
to msabramo/boto
that referenced
this issue
Nov 28, 2012
msabramo
pushed a commit
to msabramo/boto
that referenced
this issue
Nov 28, 2012
This was merged by #788 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tested against 2.1.1 and 2.4.0. Looks like loadbalancer.py is expecting only Listener stanzas inside of the member list for ListenerDescriptions. When PolicyNames is just a close tag it winds up as a setattr in the Listener object; when PolicyNames is its own list with enclosed member tags the parser is confused.
See the PolicyNames description at http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/APIReference/API_ListenerDescription.html
Anonymized section of XML return from AWS API:
The text was updated successfully, but these errors were encountered: