Please include a debug flag

Bug #966757 reported by Michael Still
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
awsome
Medium
Unassigned

Bug Description

It would be nice to include a debug flag so that I can try and diagnose what's happening with awesome. For example, the output of euca-describe-instances isn't what I would expect it to be when I am using awsome, and debug output would help me nail down why that is the case.

Revision history for this message
Martin Packman (gz) wrote :

What kind of output were you thinking of for this case?

Currently the proxy logs the openstack interactions, but not the final xml responses. I've found that when I want to look at that, I also want to compare it to the output from aws, so it makes most sense to print it out from the client side. That way a trivial script using txaws can run the same request against both and see what differs.

Revision history for this message
Michael Still (mikal) wrote :

I guess I was thinking the HTTP requests and responses, including headers. If I was trying to nail down a problem in production, I think that's the first thing I'd want to look at.

James Troup (elmo)
tags: added: canonistack
Jelmer Vernooij (jelmer)
visibility: private → public
Changed in awsome:
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers