Lab 15.1 Step 13 | Helm Install
After running " helm --debug install stable/mariad --set master.persistence.enabled=false --set slave.persistence.enabled=false" i receive the errror "failed install prepare step: no available release name found"
From the logs:
kubectl -n kube-system logs tiller-deploy-58c4d6d4f7-4dwrv
[main] 2018/10/02 12:38:16 Starting Tiller v2.7.0 (tls=false)
[main] 2018/10/02 12:38:16 GRPC listening on :44134
[main] 2018/10/02 12:38:16 Probes listening on :44135
[main] 2018/10/02 12:38:16 Storage driver is ConfigMap
[main] 2018/10/02 12:38:16 Max history per release is 0
[tiller] 2018/10/02 12:43:57 preparing install for
[storage] 2018/10/02 12:43:57 getting release "olfactory-whippet.v1"
[storage/driver] 2018/10/02 12:44:27 get: failed to get "olfactory-whippet.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/olfactory-whippet.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:44:27 info: generated name olfactory-whippet is taken. Searching again.
[storage] 2018/10/02 12:44:27 getting release "sad-possum.v1"
[storage/driver] 2018/10/02 12:44:57 get: failed to get "sad-possum.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/sad-possum.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:44:57 info: generated name sad-possum is taken. Searching again.
[storage] 2018/10/02 12:44:57 getting release "agile-meerkat.v1"
[storage/driver] 2018/10/02 12:45:27 get: failed to get "agile-meerkat.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/agile-meerkat.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:45:27 info: generated name agile-meerkat is taken. Searching again.
[storage] 2018/10/02 12:45:27 getting release "ornery-toad.v1"
[storage/driver] 2018/10/02 12:45:57 get: failed to get "ornery-toad.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/ornery-toad.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:45:57 info: generated name ornery-toad is taken. Searching again.
[storage] 2018/10/02 12:45:57 getting release "punk-clownfish.v1"
[storage/driver] 2018/10/02 12:46:27 get: failed to get "punk-clownfish.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/punk-clownfish.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:46:27 info: generated name punk-clownfish is taken. Searching again.
[tiller] 2018/10/02 12:46:27 warning: No available release names found after 5 tries
[tiller] 2018/10/02 12:46:27 failed install prepare step: no available release name found
[tiller] 2018/10/02 12:49:20 preparing install for
[storage] 2018/10/02 12:49:20 getting release "kind-newt.v1"
[storage/driver] 2018/10/02 12:49:50 get: failed to get "kind-newt.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/kind-newt.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:49:50 info: generated name kind-newt is taken. Searching again.
[storage] 2018/10/02 12:49:50 getting release "reeling-penguin.v1"
[storage/driver] 2018/10/02 12:50:20 get: failed to get "reeling-penguin.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/reeling-penguin.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:50:20 info: generated name reeling-penguin is taken. Searching again.
[storage] 2018/10/02 12:50:20 getting release "guilded-grizzly.v1"
[storage/driver] 2018/10/02 12:50:50 get: failed to get "guilded-grizzly.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/guilded-grizzly.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:50:50 info: generated name guilded-grizzly is taken. Searching again.
[storage] 2018/10/02 12:50:50 getting release "solitary-whippet.v1"
[storage/driver] 2018/10/02 12:51:20 get: failed to get "solitary-whippet.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/solitary-whippet.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:51:20 info: generated name solitary-whippet is taken. Searching again.
[storage] 2018/10/02 12:51:20 getting release "bumptious-marmot.v1"
[storage/driver] 2018/10/02 12:51:50 get: failed to get "bumptious-marmot.v1": Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps/bumptious-marmot.v1: dial tcp 10.96.0.1:443: i/o timeout
[tiller] 2018/10/02 12:51:50 info: generated name bumptious-marmot is taken. Searching again.
[tiller] 2018/10/02 12:51:50 warning: No available release names found after 5 tries
[tiller] 2018/10/02 12:51:50 failed install prepare step: no available release name found
Comments
-
also...get an error when attempting to delete the helm chart
helm delete tiller my-release stable/mariadb
Error: Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps?labelSelector=NAME=tiller,OWNER=TILLER: dial tcp 10.96.0.1:443: i/o timeout0 -
Hi,
In your install step above, I think there is a typo:helm --debug install stable/mariad
it should be:
helm --debug install stable/mariadb
Regards,
-Chris0 -
Thanks Chris. Same issue when corrected.
helm --debug install stable/mariadb --set master.persistence.enabled=false --set slave.persistence.enabled=false
[debug] Created tunnel using local port: '34234'[debug] SERVER: "localhost:34234"
[debug] Original chart version: ""
[debug] Fetched stable/mariadb to /root/.helm/cache/archive/mariadb-5.0.7.tgz[debug] CHART PATH: /root/.helm/cache/archive/mariadb-5.0.7.tgz
Error: no available release name found
0 -
Are you installing the chart as root? That may be an issue, if helm was installed and setup as another user.
0 -
root@k8s-lfs258-01:~# helm home
/root/.helm0 -
I have not installed and used kubectl and helm as root. I'd have to try that to see if it reproduces the issue you are seeing.
0 -
Hello,
This looks like an RBAC issue. When you ran the patch command after helm init did you get any output or errors? Ensure all the curly braces {} and single quotes are properly typed. Here is the command to help, after the paste ensure the single quotes are not changed to back-quotes:
kubectl -n kube-system patch deployment tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'
Regards,
0 -
Still no luck this is the only task thus far that hasn't worked as prescribed.
Do i need to add the tiller service account to the helm init command?
root@k8s-lfs258-01:~# kubectl -n kube-system patch deployment tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'
deployment.extensions/tiller-deploy patchedroot@k8s-lfs258-01:~# helm init --upgrade
$HELM_HOME has been configured at /root/.helm.Tiller (the Helm server-side component) has been upgraded to the current version.
Happy Helming!
root@k8s-lfs258-01:~# helm --debug install stable/mariadb --set master.persistence.enabled=false --set slave.persistence.enabled=false
[debug] Created tunnel using local port: '34084'[debug] SERVER: "localhost:34084"
[debug] Original chart version: ""
[debug] Fetched stable/mariadb to /root/.helm/cache/archive/mariadb-5.0.7.tgz[debug] CHART PATH: /root/.helm/cache/archive/mariadb-5.0.7.tgz
Error: no available release name found
root@k8s-lfs258-01:~# kubectl get clusterrolebindings | grep tiller
tiller-cluster-rule 6hroot@k8s-lfs258-01:~# kubectl describe clusterrolebindings tiller
Name: tiller-cluster-rule
Labels:
Annotations:
Role:
Kind: ClusterRole
Name: cluster-admin
Subjects:
Kind Name Namespace
---- ---- ---------
ServiceAccount tiller kube-system0 -
It looks like a connection issue from helm to the kube-apiserver. If not RBAC then an issue with other authentication, or networking misconfiguration I would suspect. I have just run the steps as a regular student user, the same I used for the rest of the steps. I know the .kube/config file works that way. The lab works as expected, so the software hasn't broken (which can happen with dynamic projects).
This is most likely tied to a network issue if not RBAC nor having a proper config file. For example I see in your errors requests going to port 443, not 6443 which is where the API server listens.
Did all the previous commands work?
Have you been able to exec into a pod and run commands?
Are you running Calico, did you edit anything there?What I would try next:
1) Run the lab as the non-root user I used for the rest of the labs.2) Check that there are no firewalls on any of the nodes or between the nodes that would block traffic.
3) Were there any previous steps you did extra or not do to get here? Same OS, version, software used etc? Errors before this issue?
Regards,
0 -
I found solution on web:
https://github.com/helm/helm/issues/3347
https://serverfault.com/questions/931061/helm-i-o-timeout-kubernetesThis problem happens when working with virtualbox based kubernetes.
I installed kubernetes on PC directly and there was not this problem.
Solution for Virtualbox based kubernetes is, to replace 192.168.0.0 in calico.yaml with 172.16.0.0/16 before initialize with kubeadm init, then run command
kubeadm init --pod-network-cidr 172.16.0.0/16also all confguration at home dir needed to clear which clears also all depndencies
and copy this changed calico.yaml to home before run command kubectl apply -f calico.yamlthen join with worker computers
That is all, it works for me!0 -
Hello,
If using VirtualBox please ensure that all the various network interfaces are set to allow all traffic. By default VirtualBox limits the traffic, which may be why you are not seeing the 192.168.0.0 traffic.
Regards,
0
Categories
- All Categories
- 207 LFX Mentorship
- 207 LFX Mentorship: Linux Kernel
- 735 Linux Foundation IT Professional Programs
- 339 Cloud Engineer IT Professional Program
- 167 Advanced Cloud Engineer IT Professional Program
- 66 DevOps Engineer IT Professional Program
- 132 Cloud Native Developer IT Professional Program
- 122 Express Training Courses
- 122 Express Courses - Discussion Forum
- 5.9K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 66 LFC131 Class Forum
- 39 LFD102 Class Forum
- 221 LFD103 Class Forum
- 17 LFD110 Class Forum
- 33 LFD121 Class Forum
- 17 LFD133 Class Forum
- 6 LFD134 Class Forum
- 17 LFD137 Class Forum
- 70 LFD201 Class Forum
- 3 LFD210 Class Forum
- 2 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 1 LFD233 Class Forum
- 3 LFD237 Class Forum
- 23 LFD254 Class Forum
- 689 LFD259 Class Forum
- 109 LFD272 Class Forum
- 3 LFD272-JP クラス フォーラム
- 10 LFD273 Class Forum
- 109 LFS101 Class Forum
- LFS111 Class Forum
- 2 LFS112 Class Forum
- 1 LFS116 Class Forum
- 3 LFS118 Class Forum
- 3 LFS142 Class Forum
- 3 LFS144 Class Forum
- 3 LFS145 Class Forum
- 1 LFS146 Class Forum
- 2 LFS147 Class Forum
- 8 LFS151 Class Forum
- 1 LFS157 Class Forum
- 14 LFS158 Class Forum
- 5 LFS162 Class Forum
- 1 LFS166 Class Forum
- 3 LFS167 Class Forum
- 1 LFS170 Class Forum
- 1 LFS171 Class Forum
- 2 LFS178 Class Forum
- 2 LFS180 Class Forum
- 1 LFS182 Class Forum
- 4 LFS183 Class Forum
- 30 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 2 LFS201-JP クラス フォーラム
- 17 LFS203 Class Forum
- 117 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 50 LFS241 Class Forum
- 43 LFS242 Class Forum
- 37 LFS243 Class Forum
- 13 LFS244 Class Forum
- 1 LFS245 Class Forum
- 45 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 145 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 6 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 116 LFS260 Class Forum
- 154 LFS261 Class Forum
- 41 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 23 LFS267 Class Forum
- 18 LFS268 Class Forum
- 29 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 7 LFW111 Class Forum
- 257 LFW211 Class Forum
- 178 LFW212 Class Forum
- 12 SKF100 Class Forum
- SKF200 Class Forum
- 791 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 98 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 754 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 147 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 351 Ubuntu
- 465 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 91 Linux Security
- 78 Network Management
- 101 System Management
- 47 Web Management
- 56 Mobile Computing
- 17 Android
- 28 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 366 Off Topic
- 114 Introductions
- 171 Small Talk
- 20 Study Material
- 534 Programming and Development
- 293 Kernel Development
- 223 Software Development
- 1.1K Software
- 212 Applications
- 182 Command Line
- 3 Compiling/Installing
- 405 Games
- 311 Installation
- 79 All In Program
- 79 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)