update gophercloud to the newest version

[zengchen1024]

The current version of 'gophercloud' may not work well to parse the identity endpoint such as 'https://${ip}/identity', and will be broken when creating a new client of 'ProviderClient' by passing an endpoint like that. However, the newest version of 'gophcloud' works well.
Which issue this PR fixes: #3676

[k8s-ci-robot]

Hi @zengchen1024. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[zengchen1024]

/cc @justinsb Please take a look at this PR! Thanks!

[zengchen1024]

/assign @zengchen1024

[suramya-shah]

/retest

[k8s-ci-robot]

@ss22ever: you can't request testing unless you are a kubernetes member.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[justinsb]

/retest

[chrislovecnm]

This is a new error https://s3.amazonaws.com/archive.travis-ci.org/jobs/295193259/log.txt?X-Amz-Expires=30&X-Amz-Date=20171031T190032Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20171031/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=962063dc5fd3e9dc3f853111fa1bf8d26a263467b351f543a898ba312e47fabb

[chrislovecnm]

/ok-to-tesf

[chrislovecnm]

/ok-to-test

[justinsb]

/lgtm

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• OWNERS [justinsb]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[justinsb]

Thanks @zengchen1024 - FYI, upstream k8s is on 443743e88335413103dcf1997e46d401b264fbcd at master, so we're jumping a little ahead of upstream (and I have no problem with doing so). I imagine this will sort itself out by the k8s 1.9 anyway - we typically sync up our versions at each major k8s release.

[zengchen1024]

@justinsb Thanks for promoting this PR. By the way, do I need to follow the upstream k8s if I update the other dependency next time?

[zengchen1024]

@justinsb My question is the upstream k8s may have not updated its dependency when I want to update it on kops. So I don't know which version will k8s update to. What should I do for this case? Thanks

[k8s-github-robot]

Automatic merge from submit-queue.