[magnum] region_name needs to be configured in magnum.conf
I am following installation guide from magnum documentation. but I get an error when trying to create kubernetes cluster. *region_name needs to be configured in magnum.conf* this is my full log : [root@zu-bssn-controller1 opt]# openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster bfdf76df-8b43-44e3-a094-90a76189610a accepted [root@zu-bssn-controller1 opt]# openstack coe cluster list +--------------------------------------+--------------------+---------+------------+--------------+---------------+ | uuid | name | keypair | node_count | master_count | status | +--------------------------------------+--------------------+---------+------------+--------------+---------------+ | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | mykey | 1 | 1 | CREATE_FAILED | +--------------------------------------+--------------------+---------+------------+--------------+---------------+ [root@zu-bssn-controller1 opt]# openstack coe cluster show kubernetes-cluster +---------------------+---------------------------------------------------+ | Field | Value | +---------------------+---------------------------------------------------+ | status | CREATE_FAILED | | cluster_template_id | 560f72a9-d6ac-4404-ad9e-3cd129496022 | | node_addresses | [] | | uuid | bfdf76df-8b43-44e3-a094-90a76189610a | | stack_id | None | | status_reason | region_name needs to be configured in magnum.conf | | created_at | 2018-12-14T11:25:37+00:00 | | updated_at | 2018-12-14T11:25:40+00:00 | | coe_version | None | | labels | {} | | faults | {} | | keypair | mykey | | api_address | None | | master_addresses | [] | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | master_count | 1 | | container_version | None | | name | kubernetes-cluster | | master_flavor_id | amphora | | flavor_id | amphora | +---------------------+---------------------------------------------------+ [root@zu-bssn-controller1 opt]# Anyone know what is happening? Best Regards, Zufar Dhiyaulhaq
I did not get this error but in magnum.conf I have the following section: [cinder_client] # # From magnum.conf # # Region in Identity service catalog to use for communication with the # OpenStack service. (string value) region_name = RegionOne Il giorno ven 14 dic 2018 alle ore 12:33 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
I am following installation guide from magnum documentation. but I get an error when trying to create kubernetes cluster.
*region_name needs to be configured in magnum.conf*
this is my full log :
[root@zu-bssn-controller1 opt]# openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster bfdf76df-8b43-44e3-a094-90a76189610a accepted [root@zu-bssn-controller1 opt]# openstack coe cluster list
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | uuid | name | keypair | node_count | master_count | status |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | mykey | 1 | 1 | CREATE_FAILED |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ [root@zu-bssn-controller1 opt]# openstack coe cluster show kubernetes-cluster +---------------------+---------------------------------------------------+ | Field | Value | +---------------------+---------------------------------------------------+ | status | CREATE_FAILED | | cluster_template_id | 560f72a9-d6ac-4404-ad9e-3cd129496022 | | node_addresses | [] | | uuid | bfdf76df-8b43-44e3-a094-90a76189610a | | stack_id | None | | status_reason | region_name needs to be configured in magnum.conf | | created_at | 2018-12-14T11:25:37+00:00 | | updated_at | 2018-12-14T11:25:40+00:00 | | coe_version | None | | labels | {} | | faults | {} | | keypair | mykey | | api_address | None | | master_addresses | [] | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | master_count | 1 | | container_version | None | | name | kubernetes-cluster | | master_flavor_id | amphora | | flavor_id | amphora | +---------------------+---------------------------------------------------+ [root@zu-bssn-controller1 opt]#
Anyone know what is happening?
Best Regards, Zufar Dhiyaulhaq
Hi Ignazio, my OpenStack does not have cinder deployed. it is possible? Best Regards, Zufar Dhiyaulhaq On Fri, Dec 14, 2018 at 7:20 PM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
I did not get this error but in magnum.conf I have the following section: [cinder_client]
# # From magnum.conf #
# Region in Identity service catalog to use for communication with the # OpenStack service. (string value) region_name = RegionOne
Il giorno ven 14 dic 2018 alle ore 12:33 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
I am following installation guide from magnum documentation. but I get an error when trying to create kubernetes cluster.
*region_name needs to be configured in magnum.conf*
this is my full log :
[root@zu-bssn-controller1 opt]# openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster bfdf76df-8b43-44e3-a094-90a76189610a accepted [root@zu-bssn-controller1 opt]# openstack coe cluster list
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | uuid | name | keypair | node_count | master_count | status |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | mykey | 1 | 1 | CREATE_FAILED |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ [root@zu-bssn-controller1 opt]# openstack coe cluster show kubernetes-cluster
+---------------------+---------------------------------------------------+ | Field | Value |
+---------------------+---------------------------------------------------+ | status | CREATE_FAILED | | cluster_template_id | 560f72a9-d6ac-4404-ad9e-3cd129496022 | | node_addresses | [] | | uuid | bfdf76df-8b43-44e3-a094-90a76189610a | | stack_id | None | | status_reason | region_name needs to be configured in magnum.conf | | created_at | 2018-12-14T11:25:37+00:00 | | updated_at | 2018-12-14T11:25:40+00:00 | | coe_version | None | | labels | {} | | faults | {} | | keypair | mykey | | api_address | None | | master_addresses | [] | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | master_count | 1 | | container_version | None | | name | kubernetes-cluster | | master_flavor_id | amphora | | flavor_id | amphora |
+---------------------+---------------------------------------------------+ [root@zu-bssn-controller1 opt]#
Anyone know what is happening?
Best Regards, Zufar Dhiyaulhaq
Hi Zufar, Yes it is possible but if you want persistent storage you need cinder. Magnum can use cinder. Ignazio Il giorno Ven 14 Dic 2018 13:24 Zufar Dhiyaulhaq <zufar@onf-ambassador.org> ha scritto:
Hi Ignazio,
my OpenStack does not have cinder deployed. it is possible?
Best Regards, Zufar Dhiyaulhaq
On Fri, Dec 14, 2018 at 7:20 PM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
I did not get this error but in magnum.conf I have the following section: [cinder_client]
# # From magnum.conf #
# Region in Identity service catalog to use for communication with the # OpenStack service. (string value) region_name = RegionOne
Il giorno ven 14 dic 2018 alle ore 12:33 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
I am following installation guide from magnum documentation. but I get an error when trying to create kubernetes cluster.
*region_name needs to be configured in magnum.conf*
this is my full log :
[root@zu-bssn-controller1 opt]# openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster bfdf76df-8b43-44e3-a094-90a76189610a accepted [root@zu-bssn-controller1 opt]# openstack coe cluster list
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | uuid | name | keypair | node_count | master_count | status |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | mykey | 1 | 1 | CREATE_FAILED |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ [root@zu-bssn-controller1 opt]# openstack coe cluster show kubernetes-cluster
+---------------------+---------------------------------------------------+ | Field | Value |
+---------------------+---------------------------------------------------+ | status | CREATE_FAILED | | cluster_template_id | 560f72a9-d6ac-4404-ad9e-3cd129496022 | | node_addresses | [] | | uuid | bfdf76df-8b43-44e3-a094-90a76189610a | | stack_id | None | | status_reason | region_name needs to be configured in magnum.conf | | created_at | 2018-12-14T11:25:37+00:00 | | updated_at | 2018-12-14T11:25:40+00:00 | | coe_version | None | | labels | {} | | faults | {} | | keypair | mykey | | api_address | None | | master_addresses | [] | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | master_count | 1 | | container_version | None | | name | kubernetes-cluster | | master_flavor_id | amphora | | flavor_id | amphora |
+---------------------+---------------------------------------------------+ [root@zu-bssn-controller1 opt]#
Anyone know what is happening?
Best Regards, Zufar Dhiyaulhaq
Hi thank you, this solves my issue. Best Regards, Zufar Dhiyaulhaq On Sat, Dec 15, 2018 at 1:26 AM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
Hi Zufar, Yes it is possible but if you want persistent storage you need cinder. Magnum can use cinder. Ignazio
Il giorno Ven 14 Dic 2018 13:24 Zufar Dhiyaulhaq <zufar@onf-ambassador.org> ha scritto:
Hi Ignazio,
my OpenStack does not have cinder deployed. it is possible?
Best Regards, Zufar Dhiyaulhaq
On Fri, Dec 14, 2018 at 7:20 PM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
I did not get this error but in magnum.conf I have the following section: [cinder_client]
# # From magnum.conf #
# Region in Identity service catalog to use for communication with the # OpenStack service. (string value) region_name = RegionOne
Il giorno ven 14 dic 2018 alle ore 12:33 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
I am following installation guide from magnum documentation. but I get an error when trying to create kubernetes cluster.
*region_name needs to be configured in magnum.conf*
this is my full log :
[root@zu-bssn-controller1 opt]# openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster bfdf76df-8b43-44e3-a094-90a76189610a accepted [root@zu-bssn-controller1 opt]# openstack coe cluster list
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | uuid | name | keypair | node_count | master_count | status |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | mykey | 1 | 1 | CREATE_FAILED |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ [root@zu-bssn-controller1 opt]# openstack coe cluster show kubernetes-cluster
+---------------------+---------------------------------------------------+ | Field | Value |
+---------------------+---------------------------------------------------+ | status | CREATE_FAILED | | cluster_template_id | 560f72a9-d6ac-4404-ad9e-3cd129496022 | | node_addresses | [] | | uuid | bfdf76df-8b43-44e3-a094-90a76189610a | | stack_id | None | | status_reason | region_name needs to be configured in magnum.conf | | created_at | 2018-12-14T11:25:37+00:00 | | updated_at | 2018-12-14T11:25:40+00:00 | | coe_version | None | | labels | {} | | faults | {} | | keypair | mykey | | api_address | None | | master_addresses | [] | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | master_count | 1 | | container_version | None | | name | kubernetes-cluster | | master_flavor_id | amphora | | flavor_id | amphora |
+---------------------+---------------------------------------------------+ [root@zu-bssn-controller1 opt]#
Anyone know what is happening?
Best Regards, Zufar Dhiyaulhaq
Do you mean upgrading to Rocky solved kubernetes cluster issue? Il giorno Sab 15 Dic 2018 19:01 Zufar Dhiyaulhaq <zufar@onf-ambassador.org> ha scritto:
Hi thank you,
this solves my issue.
Best Regards, Zufar Dhiyaulhaq
On Sat, Dec 15, 2018 at 1:26 AM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
Hi Zufar, Yes it is possible but if you want persistent storage you need cinder. Magnum can use cinder. Ignazio
Il giorno Ven 14 Dic 2018 13:24 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
Hi Ignazio,
my OpenStack does not have cinder deployed. it is possible?
Best Regards, Zufar Dhiyaulhaq
On Fri, Dec 14, 2018 at 7:20 PM Ignazio Cassano < ignaziocassano@gmail.com> wrote:
I did not get this error but in magnum.conf I have the following section: [cinder_client]
# # From magnum.conf #
# Region in Identity service catalog to use for communication with the # OpenStack service. (string value) region_name = RegionOne
Il giorno ven 14 dic 2018 alle ore 12:33 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
I am following installation guide from magnum documentation. but I get an error when trying to create kubernetes cluster.
*region_name needs to be configured in magnum.conf*
this is my full log :
[root@zu-bssn-controller1 opt]# openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster bfdf76df-8b43-44e3-a094-90a76189610a accepted [root@zu-bssn-controller1 opt]# openstack coe cluster list
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | uuid | name | keypair | node_count | master_count | status |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | mykey | 1 | 1 | CREATE_FAILED |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ [root@zu-bssn-controller1 opt]# openstack coe cluster show kubernetes-cluster
+---------------------+---------------------------------------------------+ | Field | Value |
+---------------------+---------------------------------------------------+ | status | CREATE_FAILED | | cluster_template_id | 560f72a9-d6ac-4404-ad9e-3cd129496022 | | node_addresses | [] | | uuid | bfdf76df-8b43-44e3-a094-90a76189610a | | stack_id | None | | status_reason | region_name needs to be configured in magnum.conf | | created_at | 2018-12-14T11:25:37+00:00 | | updated_at | 2018-12-14T11:25:40+00:00 | | coe_version | None | | labels | {} | | faults | {} | | keypair | mykey | | api_address | None | | master_addresses | [] | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | master_count | 1 | | container_version | None | | name | kubernetes-cluster | | master_flavor_id | amphora | | flavor_id | amphora |
+---------------------+---------------------------------------------------+ [root@zu-bssn-controller1 opt]#
Anyone know what is happening?
Best Regards, Zufar Dhiyaulhaq
No, it is a different issue. I am still stuck when creating a cluster (swarm or kubernetes) because of this error that i find in cloud-init log. - requests.exceptions.ConnectionError: HTTPConnectionPool(host='10.60.60.10', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f02f57321d0>: Failed to establish a new connection: [Errno 110] Connection timed out',)) Swarm Instance try to open connection to 10.60.60.10 which is my management IP address on OpenStack. But it cannot (by design it cannot, I try to curl manual to 10.60.60.10 and error). When curl to 10.61.61.10 which is my floating IP and external IP for OpenStack cluster, it works. Do you know how to change the URL that installed inside the cloud-init? Best Regards, Zufar Dhiyaulhaq On Sun, Dec 16, 2018 at 1:04 AM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
Do you mean upgrading to Rocky solved kubernetes cluster issue?
Il giorno Sab 15 Dic 2018 19:01 Zufar Dhiyaulhaq <zufar@onf-ambassador.org> ha scritto:
Hi thank you,
this solves my issue.
Best Regards, Zufar Dhiyaulhaq
On Sat, Dec 15, 2018 at 1:26 AM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
Hi Zufar, Yes it is possible but if you want persistent storage you need cinder. Magnum can use cinder. Ignazio
Il giorno Ven 14 Dic 2018 13:24 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
Hi Ignazio,
my OpenStack does not have cinder deployed. it is possible?
Best Regards, Zufar Dhiyaulhaq
On Fri, Dec 14, 2018 at 7:20 PM Ignazio Cassano < ignaziocassano@gmail.com> wrote:
I did not get this error but in magnum.conf I have the following section: [cinder_client]
# # From magnum.conf #
# Region in Identity service catalog to use for communication with the # OpenStack service. (string value) region_name = RegionOne
Il giorno ven 14 dic 2018 alle ore 12:33 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
I am following installation guide from magnum documentation. but I get an error when trying to create kubernetes cluster.
*region_name needs to be configured in magnum.conf*
this is my full log :
[root@zu-bssn-controller1 opt]# openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster bfdf76df-8b43-44e3-a094-90a76189610a accepted [root@zu-bssn-controller1 opt]# openstack coe cluster list
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | uuid | name | keypair | node_count | master_count | status |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | mykey | 1 | 1 | CREATE_FAILED |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ [root@zu-bssn-controller1 opt]# openstack coe cluster show kubernetes-cluster
+---------------------+---------------------------------------------------+ | Field | Value |
+---------------------+---------------------------------------------------+ | status | CREATE_FAILED | | cluster_template_id | 560f72a9-d6ac-4404-ad9e-3cd129496022 | | node_addresses | [] | | uuid | bfdf76df-8b43-44e3-a094-90a76189610a | | stack_id | None | | status_reason | region_name needs to be configured in magnum.conf | | created_at | 2018-12-14T11:25:37+00:00 | | updated_at | 2018-12-14T11:25:40+00:00 | | coe_version | None | | labels | {} | | faults | {} | | keypair | mykey | | api_address | None | | master_addresses | [] | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | master_count | 1 | | container_version | None | | name | kubernetes-cluster | | master_flavor_id | amphora | | flavor_id | amphora |
+---------------------+---------------------------------------------------+ [root@zu-bssn-controller1 opt]#
Anyone know what is happening?
Best Regards, Zufar Dhiyaulhaq
The master node needs to speak with port 5000 where you deployed keystone endpoint. I think you must modify heat.conf under clients_keystone section. Il giorno Sab 15 Dic 2018 19:10 Zufar Dhiyaulhaq <zufar@onf-ambassador.org> ha scritto:
No, it is a different issue. I am still stuck when creating a cluster (swarm or kubernetes) because of this error that i find in cloud-init log.
- requests.exceptions.ConnectionError: HTTPConnectionPool(host='10.60.60.10', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f02f57321d0>: Failed to establish a new connection: [Errno 110] Connection timed out',))
Swarm Instance try to open connection to 10.60.60.10 which is my management IP address on OpenStack. But it cannot (by design it cannot, I try to curl manual to 10.60.60.10 and error). When curl to 10.61.61.10 which is my floating IP and external IP for OpenStack cluster, it works.
Do you know how to change the URL that installed inside the cloud-init?
Best Regards, Zufar Dhiyaulhaq
On Sun, Dec 16, 2018 at 1:04 AM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
Do you mean upgrading to Rocky solved kubernetes cluster issue?
Il giorno Sab 15 Dic 2018 19:01 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
Hi thank you,
this solves my issue.
Best Regards, Zufar Dhiyaulhaq
On Sat, Dec 15, 2018 at 1:26 AM Ignazio Cassano < ignaziocassano@gmail.com> wrote:
Hi Zufar, Yes it is possible but if you want persistent storage you need cinder. Magnum can use cinder. Ignazio
Il giorno Ven 14 Dic 2018 13:24 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
Hi Ignazio,
my OpenStack does not have cinder deployed. it is possible?
Best Regards, Zufar Dhiyaulhaq
On Fri, Dec 14, 2018 at 7:20 PM Ignazio Cassano < ignaziocassano@gmail.com> wrote:
I did not get this error but in magnum.conf I have the following section: [cinder_client]
# # From magnum.conf #
# Region in Identity service catalog to use for communication with the # OpenStack service. (string value) region_name = RegionOne
Il giorno ven 14 dic 2018 alle ore 12:33 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
> I am following installation guide from magnum documentation. but I > get an error when trying to create kubernetes cluster. > > *region_name needs to be configured in magnum.conf* > > this is my full log : > > [root@zu-bssn-controller1 opt]# openstack coe cluster create > kubernetes-cluster --cluster-template kubernetes-cluster-template > --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster > bfdf76df-8b43-44e3-a094-90a76189610a accepted > [root@zu-bssn-controller1 opt]# openstack coe cluster list > > +--------------------------------------+--------------------+---------+------------+--------------+---------------+ > | uuid | name | > keypair | node_count | master_count | status | > > +--------------------------------------+--------------------+---------+------------+--------------+---------------+ > | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | > mykey | 1 | 1 | CREATE_FAILED | > > +--------------------------------------+--------------------+---------+------------+--------------+---------------+ > [root@zu-bssn-controller1 opt]# openstack coe cluster show > kubernetes-cluster > > +---------------------+---------------------------------------------------+ > | Field | > Value | > > +---------------------+---------------------------------------------------+ > | status | > CREATE_FAILED | > | cluster_template_id | > 560f72a9-d6ac-4404-ad9e-3cd129496022 | > | node_addresses | > [] | > | uuid | > bfdf76df-8b43-44e3-a094-90a76189610a | > | stack_id | > None | > | status_reason | region_name needs to be configured in > magnum.conf | > | created_at | > 2018-12-14T11:25:37+00:00 | > | updated_at | > 2018-12-14T11:25:40+00:00 | > | coe_version | > None | > | labels | > {} | > | faults | > {} | > | keypair | > mykey | > | api_address | > None | > | master_addresses | > [] | > | create_timeout | > 60 | > | node_count | > 1 | > | discovery_url | > None | > | master_count | > 1 | > | container_version | > None | > | name | > kubernetes-cluster | > | master_flavor_id | > amphora | > | flavor_id | > amphora | > > +---------------------+---------------------------------------------------+ > [root@zu-bssn-controller1 opt]# > > Anyone know what is happening? > > Best Regards, > Zufar Dhiyaulhaq >
Probably it means it solves the region error. ...sorry. Ignazio Il giorno Sab 15 Dic 2018 19:01 Zufar Dhiyaulhaq <zufar@onf-ambassador.org> ha scritto:
Hi thank you,
this solves my issue.
Best Regards, Zufar Dhiyaulhaq
On Sat, Dec 15, 2018 at 1:26 AM Ignazio Cassano <ignaziocassano@gmail.com> wrote:
Hi Zufar, Yes it is possible but if you want persistent storage you need cinder. Magnum can use cinder. Ignazio
Il giorno Ven 14 Dic 2018 13:24 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
Hi Ignazio,
my OpenStack does not have cinder deployed. it is possible?
Best Regards, Zufar Dhiyaulhaq
On Fri, Dec 14, 2018 at 7:20 PM Ignazio Cassano < ignaziocassano@gmail.com> wrote:
I did not get this error but in magnum.conf I have the following section: [cinder_client]
# # From magnum.conf #
# Region in Identity service catalog to use for communication with the # OpenStack service. (string value) region_name = RegionOne
Il giorno ven 14 dic 2018 alle ore 12:33 Zufar Dhiyaulhaq < zufar@onf-ambassador.org> ha scritto:
I am following installation guide from magnum documentation. but I get an error when trying to create kubernetes cluster.
*region_name needs to be configured in magnum.conf*
this is my full log :
[root@zu-bssn-controller1 opt]# openstack coe cluster create kubernetes-cluster --cluster-template kubernetes-cluster-template --master-count 1 --node-count 1 --keypair mykeyRequest to create cluster bfdf76df-8b43-44e3-a094-90a76189610a accepted [root@zu-bssn-controller1 opt]# openstack coe cluster list
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | uuid | name | keypair | node_count | master_count | status |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ | bfdf76df-8b43-44e3-a094-90a76189610a | kubernetes-cluster | mykey | 1 | 1 | CREATE_FAILED |
+--------------------------------------+--------------------+---------+------------+--------------+---------------+ [root@zu-bssn-controller1 opt]# openstack coe cluster show kubernetes-cluster
+---------------------+---------------------------------------------------+ | Field | Value |
+---------------------+---------------------------------------------------+ | status | CREATE_FAILED | | cluster_template_id | 560f72a9-d6ac-4404-ad9e-3cd129496022 | | node_addresses | [] | | uuid | bfdf76df-8b43-44e3-a094-90a76189610a | | stack_id | None | | status_reason | region_name needs to be configured in magnum.conf | | created_at | 2018-12-14T11:25:37+00:00 | | updated_at | 2018-12-14T11:25:40+00:00 | | coe_version | None | | labels | {} | | faults | {} | | keypair | mykey | | api_address | None | | master_addresses | [] | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | master_count | 1 | | container_version | None | | name | kubernetes-cluster | | master_flavor_id | amphora | | flavor_id | amphora |
+---------------------+---------------------------------------------------+ [root@zu-bssn-controller1 opt]#
Anyone know what is happening?
Best Regards, Zufar Dhiyaulhaq
participants (2)
-
Ignazio Cassano
-
Zufar Dhiyaulhaq