Nikhil Reddy
08/18/2022, 8:10 AMjuanlu
The script orchest is installed in '/home/ubuntu/.local/bin' which is not on PATH
pip
without sudo
permissions and also without ~/.local/bin
on the PATH. what installation instructions are you following?Nikhil Reddy
08/18/2022, 9:02 AMjuanlu
export PATH=~/.local/bin:$PATH
, then exec $SHELL
, and then rerun the install command?sudo pip install
⚠️ , which can potentially destabilize your system)Nikhil Reddy
08/18/2022, 10:20 AM&& bash convenience_install.shStarting minikube... * minikube v1.26.1 on Ubuntu 20.04 (xen/amd64) * Using the docker driver based on existing profile X The requested memory allocation of 7948MiB does not leave room for system overhead (total system memory: 7948MiB). You may face stability issues. * Suggestion: Start minikube with less memory allocated: 'minikube start --memory=2200mb' X The requested memory allocation of 7948MiB does not leave room for system overhead (total system memory: 7948MiB). You may face stability issues. * Suggestion: Start minikube with less memory allocated: 'minikube start --memory=2200mb' ! You cannot change the CPUs for an existing minikube cluster. Please first delete the cluster. X The requested memory allocation of 7948MiB does not leave room for system overhead (total system memory: 7948MiB). You may face stability issues. * Suggestion: Start minikube with less memory allocated: 'minikube start --memory=2200mb' * Starting control plane node minikube in cluster minikube * Pulling base image ... * Restarting existing docker container for "minikube" ... * Preparing Kubernetes v1.24.3 on Docker 20.10.17 ... * Verifying Kubernetes components... - Using image gcr.io/k8s-minikube/storage-provisioner:v5 - Using image k8s.gcr.io/ingress-nginx/controller:v1.2.1 - Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1 - Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1 * Verifying ingress addon... * Enabled addons: storage-provisioner, default-storageclass, ingress * kubectl not found. If you need it, try: 'minikube kubectl -- get pods -A' * Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default Requirement already up-to-date: orchest-cli in ./.local/lib/python3.8/site-packages (0.5.1) Requirement already satisfied, skipping upgrade: kubernetes>=21.7.0 in ./.local/lib/python3.8/site-packages (from orchest-cli) (24.2.0) Requirement already satisfied, skipping upgrade: click>=8.0.0 in ./.local/lib/python3.8/site-packages (from orchest-cli) (8.1.3) Requirement already satisfied, skipping upgrade: requests in /usr/lib/python3/dist-packages (from orchest-cli) (2.22.0) Requirement already satisfied, skipping upgrade: PyYAML in /usr/lib/python3/dist-packages (from orchest-cli) (5.3.1) Requirement already satisfied, skipping upgrade: requests-oauthlib in ./.local/lib/python3.8/site-packages (from kubernetes>=21.7.0->orchest-cli) (1.3.1) Requirement already satisfied, skipping upgrade: google-auth>=1.0.1 in ./.local/lib/python3.8/site-packages (from kubernetes>=21.7.0->orchest-cli) (2.10.0) Requirement already satisfied, skipping upgrade: websocket-client!=0.40.0,!=0.41.,!=0.42.,>=0.32.0 in ./.local/lib/python3.8/site-packages (from kubernetes>=21.7.0->orchest-cli) (1.3.3) Requirement already satisfied, skipping upgrade: six>=1.9.0 in /usr/lib/python3/dist-packages (from kubernetes>=21.7.0->orchest-cli) (1.14.0) Requirement already satisfied, skipping upgrade: setuptools>=21.0.0 in /usr/lib/python3/dist-packages (from kubernetes>=21.7.0->orchest-cli) (45.2.0) Requirement already satisfied, skipping upgrade: certifi>=14.05.14 in /usr/lib/python3/dist-packages (from kubernetes>=21.7.0->orchest-cli) (2019.11.28) Requirement already satisfied, skipping upgrade: urllib3>=1.24.2 in /usr/lib/python3/dist-packages (from kubernetes>=21.7.0->orchest-cli) (1.25.8) Requirement already satisfied, skipping upgrade: python-dateutil>=2.5.3 in ./.local/lib/python3.8/site-packages (from kubernetes>=21.7.0->orchest-cli) (2.8.2) Requirement already satisfied, skipping upgrade: oauthlib>=3.0.0 in /usr/lib/python3/dist-packages (from requests-oauthlib->kubernetes>=21.7.0->orchest-cli) (3.1.0) Requirement already satisfied, skipping upgrade: rsa<5,>=3.1.4; python_version >= "3.6" in ./.local/lib/python3.8/site-packages (from google-auth>=1.0.1->kubernetes>=21.7.0->orchest-cli) (4.9) Requirement already satisfied, skipping upgrade: cachetools<6.0,>=2.0.0 in ./.local/lib/python3.8/site-packages (from google-auth>=1.0.1->kubernetes>=21.7.0->orchest-cli) (5.2.0) Requirement already satisfied, skipping upgrade: pyasn1-modules>=0.2.1 in /usr/lib/python3/dist-packages (from google-auth>=1.0.1->kubernetes>=21.7.0->orchest-cli) (0.2.1) Requirement already satisfied, skipping upgrade: pyasn1>=0.1.3 in /usr/lib/python3/dist-packages (from rsa<5,>=3.1.4; python_version >= "3.6"->google-auth>=1.0.1->kubernetes>=21.7.0->orchest-cli) (0.4.2) Installing the Orchest Controller to manage the Orchest Cluster... Failed to install the Orchest Controller, retrying in 5 seconds... Failed to install the Orchest Controller, retrying in 10 seconds... Failed to install the Orchest Controller, retrying in 20 seconds... Setting up the Orchest Cluster... 🏁 Initializing 🏁 Deploying Third Parties 🏃 Deploying Orchest Control Plane 🙅 Failed to install. Traceback (most recent call last): File "/home/ubuntu/.local/bin/orchest", line 8, in <module> sys.exit(cli()) File "/home/ubuntu/.local/lib/python3.8/site-packages/click/core.py", line 1130, in call return self.main(*args, **kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/home/ubuntu/.local/lib/python3.8/site-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/home/ubuntu/.local/lib/python3.8/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/home/ubuntu/.local/lib/python3.8/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/orchestcli/cli.py", line 234, in install cmds.install( File "/home/ubuntu/.local/lib/python3.8/site-packages/orchestcli/cmds.py", line 395, in install _display_spinner(ClusterStatus.INITIALIZING, ClusterStatus.RUNNING) File "/home/ubuntu/.local/lib/python3.8/site-packages/orchestcli/cmds.py", line 1470, in _display_spinner resp = thread.get() File "/usr/lib/python3.8/multiprocessing/pool.py", line 771, in get raise self._value File "/usr/lib/python3.8/multiprocessing/pool.py", line 125, in worker result = (True, func(*args, **kwds)) File "/home/ubuntu/.local/lib/python3.8/site-packages/kubernetes/client/api_client.py", line 180, in __call_api response_data = self.request( File "/home/ubuntu/.local/lib/python3.8/site-packages/kubernetes/client/api_client.py", line 373, in request return self.rest_client.GET(url, File "/home/ubuntu/.local/lib/python3.8/site-packages/kubernetes/client/rest.py", line 240, in GET return self.request("GET", url, File "/home/ubuntu/.local/lib/python3.8/site-packages/kubernetes/client/rest.py", line 234, in request raise ApiException(http_resp=r) kubernetes.client.exceptions.ApiException: (504) Reason: Gateway Timeout HTTP response headers: HTTPHeaderDict({'Audit-Id': '6557dba1-b5e2-4238-adc8-5f47a5b7ef68', 'Cache-Control': 'no-cache, private', 'Date': 'Thu, 18 Aug 2022 101533 GMT', 'Content-Length': '152', 'Content-Type': 'text/plain; charset=utf-8'}) HTTP response body: {"metadata":{},"status":"Failure","message":"Timeout: request did not complete within the allotted timeout","reason":"Timeout","details":{},"code":504} ubuntu@ip-172-31-3-55:~$ minikube ip 192.168.49.2 ubuntu@ip-172-31-3-55:~$
juanlu
Nikhil Reddy
08/18/2022, 10:28 AMjuanlu
minikube logs --file=log.txt
and attach here the resulting log.txt
Yannick
kubernetes.client.exceptions.ApiException: (504)
Reason: Gateway Timeout
I think the installation still went through, just the CLI couldn't update the spinner to reflect the status of the cluster as the cluster became unreachable for some time. Definitely something we can improve on.
You can run orchest status
to see what the status is of your cluster, which I expect to be Running
orchest-cli
. Thanks for error log @Nikhil Reddy 😸Nikhil Reddy
08/18/2022, 11:05 AMYannick