v1.20/stable : failing to install addons on utf <> ascii locale issue
See original GitHub issueHi there,
Trying to install new 1.20 to implement the keda addon. But, it fails before. (the used procedure works fine with v1.19)
It seems to be related to a utf <> ascii locale issue
Snap install goes fine:
microk8s v1.20.0 1864 1.20/stable canonical* classic
microk8s is running
high-availability: no
datastore master nodes: 127.0.0.1:19001
datastore standby nodes: none
addons:
enabled:
ha-cluster # Configure high availability on the current node
disabled:
ambassador # Ambassador API Gateway and Ingress
cilium # SDN, fast with full network policy
dashboard # The Kubernetes dashboard
dns # CoreDNS
fluentd # Elasticsearch-Fluentd-Kibana logging and monitoring
gpu # Automatic enablement of Nvidia CUDA
helm # Helm 2 - the package manager for Kubernetes
helm3 # Helm 3 - Kubernetes package manager
host-access # Allow Pods connecting to Host services smoothly
ingress # Ingress controller for external access
istio # Core Istio service mesh services
jaeger # Kubernetes Jaeger operator with its simple config
keda # Kubernetes-based Event Driven Autoscaling
knative # The Knative framework on Kubernetes.
kubeflow # Kubeflow for easy ML deployments
linkerd # Linkerd is a service mesh for Kubernetes and other frameworks
metallb # Loadbalancer for your Kubernetes cluster
metrics-server # K8s Metrics Server for API access to service metrics
multus # Multus CNI enables attaching multiple network interfaces to pods
portainer # Portainer UI for your Kubernetes cluster
prometheus # Prometheus operator for monitoring and logging
rbac # Role-Based Access Control for authorisation
registry # Private image registry exposed on localhost:32000
storage # Storage class; allocates storage from host directory
traefik # traefik Ingress controller for external access
This runs on a GCE Ubuntu instance : ubuntu-2004-focal-v20201211
as per Google’s naming
Linux microk8s-keda 5.4.0-1032-gcp #34-Ubuntu SMP Wed Dec 9 17:23:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
When it goes to addons install:
microk8s enable storage | tee -a "$REPORT"
microk8s enable dns | tee -a "$REPORT"
microk8s enable helm3 | tee -a "$REPORT"
microk8s enable rbac | tee -a "$REPORT"
microk8s enable dashboard | tee -a "$REPORT"
microk8s status --wait-ready
GCE’s Ubuntu says:
Traceback (most recent call last):
File "/snap/microk8s/1864/scripts/wrappers/enable.py", line 43, in <module>
enable(prog_name='microk8s enable')
File "/snap/microk8s/1864/usr/lib/python3/dist-packages/click/core.py", line 716, in __call__
return self.main(*args, **kwargs)
File "/snap/microk8s/1864/usr/lib/python3/dist-packages/click/core.py", line 675, in main
_verify_python3_env()
File "/snap/microk8s/1864/usr/lib/python3/dist-packages/click/_unicodefun.py", line 119, in _verify_python3_env
'mitigation steps.' + extra)
RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Either run this under Python 2 or consult http://click.pocoo.org/python3/ for mitigation steps.
This system supports the C.UTF-8 locale which is recommended.
You might be able to resolve your issue by exporting the
following environment variables:
export LC_ALL=C.UTF-8
export LANG=C.UTF-8
Click discovered that you exported a UTF-8 locale
but the locale system could not pick up from it because
it does not exist. The exported locale is "C.UTF-8" but it
is not supported
Traceback (most recent call last):
File "/snap/microk8s/1864/scripts/wrappers/enable.py", line 43, in <module>
enable(prog_name='microk8s enable')
File "/snap/microk8s/1864/usr/lib/python3/dist-packages/click/core.py", line 716, in __call__
return self.main(*args, **kwargs)
File "/snap/microk8s/1864/usr/lib/python3/dist-packages/click/core.py", line 675, in main
_verify_python3_env()
File "/snap/microk8s/1864/usr/lib/python3/dist-packages/click/_unicodefun.py", line 119, in _verify_python3_env
'mitigation steps.' + extra)
RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Either run this under Python 2 or consult http://click.pocoo.org/python3/ for mitigation steps.
Let me know if additional Ubuntu config info is needed to understand the issue.
Didier
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Issues - GitHub
Hi there, Trying to install new 1.20 to implement the keda addon. ... v1.20/stable : failing to install addons on utf <> ascii...
Read more >Ruby error UTF-8 to ASCII - Stack Overflow
1 Answer 1 · No dice. · Check your LC_CTYPE and LANG environment variables. · Well, I don't think it'll fix the problem...
Read more >UTF-8 and Unicode FAQ for Unix/Linux
All you need to know to use Unicode/UTF-8 on Unix and Linux systems. ... Unicode now replaces ASCII, ISO 8859 and EUC at...
Read more >Is it possible to set "locale" of a Windows application to UTF-8?
I think it is a bug, because the programmers may use English and ignore testing non-English text display issues. I don't think the...
Read more >The Unicode HOWTO: Locale setup
When encoded using UTF-8, non-ASCII characters will never be encoded using null ... --enable-add-ons # make # make check # make info #...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I see. 1.20
enable
command has moved to using python. Previously on bash. Using python gave more features that are clunky and difficult to implement in bash. While what i mentioned above is purely my opinion, we can always check with @ktsakalozos and @knkski what they think. Reopening the issue for more discussion.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.