Kuryr-kubernetes services throws Dummy exception while creating a POD
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
Invalid
|
Undecided
|
Ilya Chukhnakov |
Bug Description
1.Created two node devstack k8s with kuryr setup.
2.The kubectl get nodes shows node to be ready
vagrant@
NAME STATUS AGE
container1 Ready 3h
container2 Ready 3h
vagrant@
3.now tried creating the pod ,During the creation of the pod kuryr-kubernetes service throws below given error
4.On this error tried applying the review https:/
Logs:
=====
ERROR in kuyr-kubernetes.log
-------
09T08:30:29Z'}], u'containerStat
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:03:42.492 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:04:34.404 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
2016-11-09 11:07:22.071 24242 ERROR kuryr_kubernete
I am attaching the local.conf used for the same
Master:
---------------
[[local|localrc]]
GIT_BASE=https:/
enable_plugin kuryr-kubernetes \
https:/
# If you do not want stacking to clone new versions of the enabled services,
# like for example when you did local modifications and need to ./unstack.sh
# and ./stack.sh again, uncomment the following
RECLONE="yes"
HOST_IP=
# Log settings for better readability
LOGFILE=
LOG_COLOR=False
# If you want the screen tabs logged in a specific location, you can use:
# SCREEN_
# Credentials
ADMIN_PASSWORD=pass
DATABASE_
RABBIT_
SERVICE_
SERVICE_TOKEN=pass
# Enable Keystone v3
IDENTITY_
# In pro of speed and being lightweight, we will be explicit in regards to
# which services we enable
ENABLED_SERVICES=""
# Neutron services
enable_service neutron
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-svc
# Keystone
enable_service key
# dependencies
enable_service mysql
enable_service rabbit
# By default use all the services from the kuryr-kubernetes plugin
# Docker
# ======
# If you already have docker configured, running and with its socket writable
# by the stack user, you can omit the following line.
enable_service docker
# Etcd
# ====
# The default is for devstack to run etcd for you. You can select the image and
# version of it by uncommenting and modifying the following defaults.
# KURYR_ETCD_
# KURYR_ETCD_
#
# You can select the listening and advertising client and peering Etcd
# addresses by uncommenting and changing from the following defaults:
# KURYR_ETCD_
# KURYR_ETCD_
# KURYR_ETCD_
# KURYR_ETCD_
#
# If you already have etcd configured and running, you can just comment out
enable_service etcd
# then uncomment and set the following line:
# KURYR_ETCD_
# Kubernetes
# ==========
#
# Kubernetes is run from the hyperkube docker image
# If you already have a Kubernetes deployment, you can use it instead and omit
# enabling the Kubernetes service (except Kubelet, which must be run by
# devstack so that it uses our development CNI driver.
#
# The default is, again, for devstack to run the Kubernetes services:
enable_service kubernetes-api
enable_service kubernetes-
enable_service kubernetes-
# We use hyperkube to run the services. You can select the hyperkube image and/
# or version by uncommenting and setting the following ENV vars different
# to the following defaults:
# KURYR_HYPERKUBE
# KURYR_HYPERKUBE
#
# If you have the 8080 port already bound to another service, you will need to
# have kubernetes API server bind to another port. In order to do that,
# uncomment and set a different port number in:
# KURYR_K8S_
#
# If you want to test with a different range for the Cluster IPs uncomment and
# set the following ENV var to a different CIDR
# KURYR_K8S_
#
# If, however, you are reusing an existing deployment, you should uncomment and
# set an ENV var so that the Kubelet devstack runs can find the API server:
# KURYR_K8S_API_URL="http://
#
# Kubelet
# =======
#
# Kubelet should almost invariably be run by devstack
enable_service kubelet
# You can specify a different location for the hyperkube binary that will be
# extracted from the hyperkube container into the Host filesystem:
# KURYR_HYPERKUBE
#
# NOTE: KURYR_HYPERKUBE
# the selected binary for the Kubelet.
# Kuryr watcher
# =============
#
# Just like the Kubelet, you'll want to have the watcher enabled. It is the
# part of the codebase that connects to the Kubernetes API server to read the
# resource events and convert them to Neutron actions
enable_service kuryr-kubernetes
minion:
-----===
[[local|localrc]]
GIT_BASE=https:/
enable_plugin kuryr-kubernetes \
https:/
# If you do not want stacking to clone new versions of the enabled services,
# like for example when you did local modifications and need to ./unstack.sh
# and ./stack.sh again, uncomment the following
RECLONE="yes"
RABBIT_
Q_HOST=
HOST_IP=
DATA_IP=
KEYSTONE_
KEYSTONE_
MULTI_HOST=1
# Log settings for better readability
LOGFILE=
LOG_COLOR=False
# If you want the screen tabs logged in a specific location, you can use:
# SCREEN_
# Credentials
ADMIN_PASSWORD=pass
DATABASE_
RABBIT_
SERVICE_
SERVICE_TOKEN=pass
# Enable Keystone v3
IDENTITY_
# In pro of speed and being lightweight, we will be explicit in regards to
# which services we enable
ENABLED_SERVICES=""
# Neutron services
#enable_service neutron
enable_service q-agt
#enable_service q-dhcp
#enable_service q-l3
#enable_service q-svc
# Keystone
enable_service key
# dependencies
#enable_service mysql
enable_service rabbit
# By default use all the services from the kuryr-kubernetes plugin
# Docker
# ======
# If you already have docker configured, running and with its socket writable
# by the stack user, you can omit the following line.
enable_service docker
# Etcd
# ====
# The default is for devstack to run etcd for you. You can select the image and
# version of it by uncommenting and modifying the following defaults.
# KURYR_ETCD_
# KURYR_ETCD_
#
# You can select the listening and advertising client and peering Etcd
# addresses by uncommenting and changing from the following defaults:
# KURYR_ETCD_
# KURYR_ETCD_
# KURYR_ETCD_
# KURYR_ETCD_
#
# If you already have etcd configured and running, you can just comment out
enable_service etcd
# then uncomment and set the following line:
# KURYR_ETCD_
# Kubernetes
# ==========
#
# Kubernetes is run from the hyperkube docker image
# If you already have a Kubernetes deployment, you can use it instead and omit
# enabling the Kubernetes service (except Kubelet, which must be run by
# devstack so that it uses our development CNI driver.
#
# The default is, again, for devstack to run the Kubernetes services:
#enable_service kubernetes-api
#enable_service kubernetes-
#enable_service kubernetes-
# We use hyperkube to run the services. You can select the hyperkube image and/
# or version by uncommenting and setting the following ENV vars different
# to the following defaults:
# KURYR_HYPERKUBE
# KURYR_HYPERKUBE
#
# If you have the 8080 port already bound to another service, you will need to
# have kubernetes API server bind to another port. In order to do that,
# uncomment and set a different port number in:
# KURYR_K8S_
#
# If you want to test with a different range for the Cluster IPs uncomment and
# set the following ENV var to a different CIDR
# KURYR_K8S_
#
# If, however, you are reusing an existing deployment, you should uncomment and
# set an ENV var so that the Kubelet devstack runs can find the API server:
KURYR_K8S_API_URL="http://
#
# Kubelet
# =======
#
# Kubelet should almost invariably be run by devstack
enable_service kubelet
# You can specify a different location for the hyperkube binary that will be
# extracted from the hyperkube container into the Host filesystem:
# KURYR_HYPERKUBE
#
# NOTE: KURYR_HYPERKUBE
# the selected binary for the Kubelet.
# Kuryr watcher
# =============
#
# Just like the Kubelet, you'll want to have the watcher enabled. It is the
# part of the codebase that connects to the Kubernetes API server to read the
# resource events and convert them to Neutron actions
enable_service kuryr-kubernetes
Changed in kuryr-kubernetes: | |
assignee: | nobody → Ilya Chukhnakov (ichukhnakov) |
status: | New → In Progress |
This is an expected behaviour. kuryr-kubernetes is currently under development. The version you are running does not implement specific handlers but uses a stub DummyHandler to test the logging/retrying aspects of the event handling process. These exceptions will go away once [1] is merged (note, however, that [1] only implements the controller-side of pod port handling and until the CNI driver is implemented, it will still produce some exceptions).
[1] https:/ /review. openstack. org/#/c/ 376044