Issues with homestead and homestead-prov under Kubernetes #86
Comments
Yep - it'd be useful if you could provide your build logs. On our internal k8s cluster, we get the following when we run the homestead container:
Note, it might be useful to do a clean build of the Docker images, without the cache to ensure you've got a consistent set of packages. We normally build with the following command:
|
I also use --no-cache if I think there's a potential issue.
|
@blsaws Do you have the build log for the base container as well? |
Here is the base build log
|
I found out that I had a bug in my script that created the containers, and I was tagging the wrong container. I fixed it, and all is working. Closing this bug. Apologies for the noise! I'll take further issues to the list first. |
I'm having the same issue. What was the bug you had in your scripts? I've tried rebuilding with |
Me too i'm having the same issue. How did you solved it? |
Hi, I wanted to first float these issues on the clearwater list but am getting no response to list subscription requests. So reaching out here for help. I'm working on deploying clearwater-docker under Kubernetes for use in the OPNFV Models and VES projects. I'm having issues with homestead and homestead-prov crashing, and never completely coming up. It appears to be related to the snmp daemon, for which some binaries are missing. See below for the logs (output of "kubectl logs --namespace default homestead-1026420941-q3lk4 homestead", similar output for homestead-prov). I've looked into the Dockerfiles and AFAICT the issue must be somewhere in the package build process for homestead, vs the packages used for the other containers (for which this snmp issue does not occur). I have tried this with the latest (master) and stable repos.
I can provide build output for the container image as needed. Nothing unusual there, beyond a couple of errors that do not fail the build, and which are also present for the containers that do work.
From comparing the bono and homestead containers live, it's clear that there are files in /usr/share/clearwater/bin/ named clearwater-socket-factory* (a set of files) that are not present in the homestead container, as built. I believe side-effects of this error are that the homestead container never fully initializes, and the necessary DNS name for homestead not registered (as are all the other container names, even homestead-prov curiously), and thus sprout rejects registration requests as it can't find the homestead server.
Here is the log.
The text was updated successfully, but these errors were encountered: