search

whitmo / charm-kubernetes

A juju charm to deploy a kubernetes minion
Other
1 stars 1 forks source link

Register minion has required fields #19

Open mbruzek opened 9 years ago

mbruzek commented 9 years ago

While attempting to test e2e with the latest kubernetes release v0.14.1 the bundle had deployment errors. It seems that new fields (status.Capacity, and spec.ExternalID) are required.

Here is the relevant information from the error in the log file:

2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 Running with
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 {'proxy_bind_addr': '15.125.95.64', 'overlay_type': 'udp', 'etcd_servers': 'http://10.0.0.220:4001', 'identifier': 'kubernetes-0', 'kubeapi_server': 'http://10.0.0.224:8080', 'kubelet_bind_addr': '10.0.0.221'}
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 Starting cadvisor
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 Starting kubelet
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 Starting proxy
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 Registering machine
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 {
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   "kind": "Status",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   "creationTimestamp": null,
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   "apiVersion": "v1beta1",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   "status": "Failure",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   "message": "Node \"10.0.0.221\" is invalid: [status.Capacity: required value, spec.ExternalID: required value]",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   "reason": "Invalid",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   "details": {
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40     "id": "10.0.0.221",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40     "kind": "Node",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40     "causes": [
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40       {
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40         "reason": "FieldValueRequired",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40         "message": "status.Capacity: required value",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40         "field": "status.Capacity"
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40       },
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40       {
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40         "reason": "FieldValueRequired",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40         "message": "spec.ExternalID: required value",
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40         "field": "spec.ExternalID"
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40       }
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40     ]
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   },
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40   "code": 422
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 }
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 Response status:422 reason:status code 422 body:{u'status': u'Failure', u'kind': u'Status', u'code': 422, u'apiVersion': u'v1beta1', u'reason': u'Invalid', u'details': {u'kind': u'Node', u'id': u'10.0.0.221', u'causes': [{u'field': u'status.Capacity', u'reason': u'FieldValueRequired', u'message': u'status.Capacity: required value'}, {u'field': u'spec.ExternalID', u'reason': u'FieldValueRequired', u'message': u'spec.ExternalID: required value'}]}, u'message': u'Node "10.0.0.221" is invalid: [status.Capacity: required value, spec.ExternalID: required value]', u'creationTimestamp': None}
...
2015-04-06 21:23:16 INFO unit.kubernetes/0.network-relation-changed logger.go:40 RuntimeError: Unable to register machine with {'Kind': 'Minion', 'metadata': {'name': u'10.0.0.221'}, 'ID': '10.0.0.221', 'resources': {'capacity': {'mem': '4048300 K', 'cpu': 2}}, 'HostIP': '10.0.0.221'}
2015-04-06 21:23:16 INFO juju.worker.uniter.context context.go:359 handling reboot
2015-04-06 21:23:16 ERROR juju.worker.uniter.operation runhook.go:86 hook "network-relation-changed" failed: exit status 1

We will need a reference to the API and the required values to send.

mbruzek commented 9 years ago

I found some documentation here that specifies the required settings for a node (minion):

https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/docker-multinode/worker.md