Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Remove Content-Type header for payloadless request #37
Conversation
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-goose |
|
Build failed: Tests failed |
|
$$retry$$
That... is not something this branch in any way touches, perhaps the 1ms timeout is too optimistic given load. |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-goose |
jujubot
merged commit 8f055ce
into
go-goose:v1
Nov 30, 2016
bz2
referenced this pull request
in juju/juju
Dec 2, 2016
Merged
dependencies.tsv: Update goose for secgroup fix #6651
added a commit
to juju/juju
that referenced
this pull request
Dec 2, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
gnuoy commentedNov 30, 2016
If a call out to the OpenStack API does not contain a
payload then do not set a Content-Type header as this
causes the Request to fail for OpenStack Mitaka+
deployments. Fixes lp:1625624
QA Steps
To reproduce the problem run the steps below. The final secgroup-list should not return
any security groups for this environment if Juju has cleaned up properly.