[coreos] Minion is not registering to kubernetes because of certificate error

Bug #1630189 reported by yatin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
yatin

Bug Description

Created a coreos cluster with 3 masters(--master-lb-enabled used at time of creation of cluster template) and 1 minion.

Cluster created successfully but minion not registered:
core@k8-vxiiuznpyr-2-rmsglcwcjtdp-kube-master-mkgwr2crpa7a ~ $ kubernetes/platforms/linux/amd64/kubectl get nodes
NAME STATUS AGE
10.0.0.15 Ready,SchedulingDisabled 1h
10.0.0.16 Ready,SchedulingDisabled 1h
10.0.0.3 Ready,SchedulingDisabled 1h

Minion is missing:-

kubelet logs in minion:-
Unable to write event: 'x509: certificate is valid for 172.18.33.5, 10.0.0.15, 127.0.0.1, not 10.0.0.5 Here 10.0.0.5 is vip_address loadbalancer

yatin (yatinkarel)
Changed in magnum:
assignee: nobody → yatin (yatinkarel)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/382149

Revision history for this message
yatin (yatinkarel) wrote :
Download full text (3.2 KiB)

After fixing this, created coreos cluster with 2 master's and 1 minion:-
minion successfully registered with master nodes.

ubuntu@ubuntubase:/opt/stack/magnum$ magnum cluster-show k8s-cluster
+---------------------+------------------------------------------------------------+
| Property | Value |
+---------------------+------------------------------------------------------------+
| status | CREATE_COMPLETE |
| cluster_template_id | cab7d7c5-c43b-4c92-91b8-4392f6dab19f |
| uuid | d1a1bf9d-fce6-4717-8203-de59faefe9b0 |
| stack_id | 6b83c620-a1df-4622-95d4-36ac8877188e |
| status_reason | Stack CREATE completed successfully |
| created_at | 2016-10-05T04:37:02+00:00 |
| name | k8s-cluster |
| updated_at | 2016-10-05T05:05:50+00:00 |
| discovery_url | https://discovery.etcd.io/9ccef8c176df28aef64204c6fca5b138 |
| api_address | https://172.18.33.11:6443 |
| coe_version | v1.2.0 |
| master_addresses | ['172.18.33.9', '172.18.33.13'] |
| create_timeout | 240 |
| node_addresses | ['172.18.33.4'] |
| master_count | 2 |
| container_version | 1.11.2 |
| node_count | 1 |
+---------------------+------------------------------------------------------------+

ubuntu@ubuntubase:~$ kubernetes/platforms/linux/amd64/kubectl get nodes
NAME STATUS AGE
10.0.0.13 Ready 18m
10.0.0.3 Ready,SchedulingDisabled 30m
10.0.0.8 Ready,SchedulingDisabled 32m

ubuntu@ubuntubase:~$ neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id | fixed_ip_address | floating_ip_address | port_id |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| 0d00cb03-d95a-40df-bc52-3e6d5a5c62d8 | 10.0.0.8 | 172.18.33.9 | ea8b9dc7-2f17-4729-aed9-5a2d7f26f0cc |
| 452f13a4-c4b3-40c2-bc0e-7c94ab360655 | 10.0.0.3 | 172.18.33.13 | 9ebec5a4-a0d1-466c-a13c-f65486c3361e |
| 61c8db7d-1cae-4fad-a24a-1430cdc81c3a | 10.0.0.13 | 172.18.33.4 | 70b9743a-a1ae-4f5c-a111-26f9cc52890c |
| 9b06d2b4-b9ae-43b4-b08c-9963f4122d62 | 10.0.0.9 | 172.18.33.11 | 6f5983b4-5435-4351-a562-362c5ee06029 |
+--------------------------------------+------------------+---------------------+--...

Read more...

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/382150

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/382212

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (stable/newton)

Change abandoned by yatin (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/382212
Reason: Commited by mistake, original: https://review.openstack.org/#/c/382150/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (stable/newton)

Reviewed: https://review.openstack.org/382150
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=7508908c40f0644038efdcd16c1a7d7d4e217397
Submitter: Jenkins
Branch: stable/newton

commit 7508908c40f0644038efdcd16c1a7d7d4e217397
Author: yatin <email address hidden>
Date: Wed Oct 5 14:47:00 2016 +0530

    [coreos] Fix: k8s cluster creation with loadbalancer enabled

    Minions do not register when coreos k8s cluster gets created
    with loadbalancer enabled because loadbalancer vip and
    pool floating ip are not associated with certificates created
    for master.
    With this patch minions successfully registers with masters.

    Change-Id: Ifc8b6bde5a9bc3dd8c7e965e0450e2aa0d243263
    Closes-Bug: #1630189

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/382149
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=40c1e2de6f23ac0b2b62e432d5f2b7c150a1e9bb
Submitter: Jenkins
Branch: master

commit 40c1e2de6f23ac0b2b62e432d5f2b7c150a1e9bb
Author: yatin <email address hidden>
Date: Wed Oct 5 10:51:40 2016 +0530

    [coreos] Allow k8s cluster without floating ip

    This patch allows k8s coreos cluster to be created
    without Floating IP resources.

    Depends-on: I51feb6ccdc0fab91a591568866e6801f2bbb319b
    Change-Id: Ifc8b6bde5a9bc3dd8c7e965e0450e2aa0d243263
    Partially-Implements: blueprint bay-with-no-floating-ips
    Closes-Bug: #1630189
    Partial-Bug: #1490334

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 4.0.0

This issue was fixed in the openstack/magnum 4.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 3.2.0

This issue was fixed in the openstack/magnum 3.2.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.