cinder volume driver of kubernetes requires hostname to be
same as instance name so that volume can be attached to
node running the pod, hostname-override is not required
by cinder volume driver.
hostname-override was introduced with following patch:
I55df72c8f36d81852bde36018c17670101860f79
In this patch following are fixed:
1) v3 --> v2(incorrect keystone version) is changed to v3 --> v2.0
2) --hostname-override is not added to KUBELET_ARGS for cinder
volume driver.
Reviewed: https:/ /review. openstack. org/373417 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=a7d719d08ac 22bc9e023c1dae7 2bbf20210ff1e6
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit a7d719d08ac22bc 9e023c1dae72bbf 20210ff1e6
Author: yatin <email address hidden>
Date: Tue Sep 20 15:01:27 2016 +0530
Fix k8s_fedora to work with cinder volume driver
cinder volume driver of kubernetes requires hostname to be
same as instance name so that volume can be attached to
node running the pod, hostname-override is not required
by cinder volume driver.
hostname- override was introduced with following patch: 6d81852bde36018 c17670101860f79
I55df72c8f3
In this patch following are fixed:
1) v3 --> v2(incorrect keystone version) is changed to v3 --> v2.0
2) --hostname-override is not added to KUBELET_ARGS for cinder
volume driver.
Change-Id: I1347b934d99ad6 fe04e124e295c49 61fe77c6b20
Closes-Bug: #1625479
Closes-Bug: #1620455