Skip to content
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.

Sign up for GitHub

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

Jump to bottom

clouds.yaml doesn't support doesn't work #69

Closed
flaper87 opened this issue Oct 23, 2018 · 3 comments
Closed

clouds.yaml doesn't support doesn't work #69

flaper87 opened this issue Oct 23, 2018 · 3 comments
Assignees
@flaper87

Comments

@flaper87
Copy link
Contributor

The current implementation is not passing all the required data to the auth step resulting in an authentication failure.
@flaper87
Copy link
Contributor Author

/assign @flaper87

flaper87 added a commit to flaper87/cluster-api-provider-openstack that referenced this issue Oct 23, 2018
@flaper87
Let clientconfig create the AuthOptions instance
ca2241e 
We were creating our own copy of AuthOptions rather than relying on the
utilities provided by clientconfig. Our copy didn't have all the info
required by gophercloud to authenticate.

Closes kubernetes-sigs#69
@flaper87 flaper87 mentioned this issue Oct 23, 2018
Merged
flaper87 added a commit to flaper87/cluster-api-provider-openstack that referenced this issue Oct 23, 2018
@flaper87
Let clientconfig create the AuthOptions instance
29d9d1d 
We were creating our own copy of AuthOptions rather than relying on the
utilities provided by clientconfig. Our copy didn't have all the info
required by gophercloud to authenticate.

Closes kubernetes-sigs#69
flaper87 added a commit to flaper87/cluster-api-provider-openstack that referenced this issue Oct 23, 2018
@flaper87
Let clientconfig create the AuthOptions instance
f8517f1 
We were creating our own copy of AuthOptions rather than relying on the
utilities provided by clientconfig. Our copy didn't have all the info
required by gophercloud to authenticate.

Closes kubernetes-sigs#69
@scruplelesswizard
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@chaosaffe: Closing this issue.

In response to this:

/close

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.

k8s-ci-robot pushed a commit that referenced this issue Oct 23, 2018
@flaper87 @k8s-ci-robot
Let clientconfig create the AuthOptions instance (#70)
d72adf0 
We were creating our own copy of AuthOptions rather than relying on the
utilities provided by clientconfig. Our copy didn't have all the info
required by gophercloud to authenticate.

Closes #69
flaper87 referenced this issue in openshift/cluster-api-provider-openstack Nov 29, 2018
@flaper87
Let clientconfig create the AuthOptions instance (#70)
39d1b06 
We were creating our own copy of AuthOptions rather than relying on the
utilities provided by clientconfig. Our copy didn't have all the info
required by gophercloud to authenticate.

Closes #69
iamemilio pushed a commit to iamemilio/cluster-api-provider-openstack that referenced this issue Jan 6, 2020
@openshift-merge-robot
Merge pull request kubernetes-sigs#69 from Fedosin/boot_from_volume
945cf04 
Bug 1754070: Add boot from volume support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flaper87 flaper87

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@flaper87 @scruplelesswizard @k8s-ci-robot