kumahq/kuma-demo

A demo app to illustrate the capabilities and advantages of Kuma. 🐻

kuma-demo's Issues

Demo Refresh Requirements

Description

• Configurable service endpoints
• Add a component that calls outside the mesh (to demo / exercise external services)
• Ensure e2e tracing is implemented in all components to show off tracing
• Add metrics to some components to demonstrate metric aggregation
• Admin Panel
  • Simulate failures
  • Switch backends?
  • Toggle debug view (show where traffic is coming from, pod metadata, headers, latency, number of retries, error codes etc...)

Not Getting 2/2 PODS for Services or Deployment

Describe the bug
After hitting command kubectl apply -f https://bit.ly/demokuma I am not seeing 2/2 pods its 1/1 always

To Reproduce
Steps to reproduce the behavior:

1. Hit kubectl apply -f https://bit.ly/demokuma
2. kubectl get pods -n kuma-demo

Result
NAME READY STATUS RESTARTS AGE
kuma-demo-app-6787b4f7f5-jcptm 1/1 Running 0 70s
kuma-demo-backend-v0-56db47c579-csscc 1/1 Running 0 70s
postgres-master-645bc44fd-ptkqm 1/1 Running 0 70s
redis-master-55fd8f6f54-sc694 1/1 Running 0 70s

Expected behavior
2/2 PODS for services or deployments

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS] MAC OS
• Kuma: [e.g. v0.3.1] - 1.3.0
• Environment [e.g. Kubernetes, Universal] - Kubernetes
• Browser [e.g. chrome, safari] - Chrome

Additional context

• Not able to hit URL kubectl apply -f https://bit.ly/demokuma due to company policies so cloned the repo locally and hitting the command with file.
• I am running kubenetes in docker way not like minikube way.

Thanks
Jaikrat

localhost:8080 empty

Forwarding from 127.0.0.1:8080 -> 8080
Forwarding from [::1]:8080 -> 8080
Forwarding from 127.0.0.1:3001 -> 3001
Forwarding from [::1]:3001 -> 3001
Handling connection for 8080
Handling connection for 8080```

but from browser:
`http://localhost:8080/auth/` 
`This localhost page can’t be found
No webpage was found for the web address: http://localhost:8080/auth/`

Kubernetes instruction clarity

In the KUBERNETES.md doc, step 6 is a little vague:

In the following steps, we will be using the pod name of the `kuma-control-plane-*************` [...]

Can we include instructions informing the user that they have to cd into their app folder now for the YAML config files? This threw me a couple times when going through the steps because I run the k8s demo in a directory other than the app/api directory so that I don't litter files everywhere.

what if some Deployment PODS do not want to inject kum-init sidecar,how to set?

apiVersion: v1
kind: Namespace
metadata:
name: kuma-demo
namespace: kuma-demo
annotations:
kuma.io/sidecar-injection: enabled

---

By default we set the namespace and add the annotation kuma.io/sidecar-injection: enabled so that each POD of the k8s namespace is injected kum-init sidecar. But what if some Deployment PODS do not want to inject kum-init sidecar,how to set?

Missing explanation of what demo does

Describe the bug
No explanation of what the demo does or why that's useful.

To Reproduce
Steps to reproduce the behavior:

1. Read the README
2. Find no explanation of what the demo is supposed to show and why that is important.

Expected behavior
A great demo explains a problem and shows the user how the software fixes that problem.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Kuma: [e.g. v0.3.1]
• Environment [e.g. Kubernetes, Universal]
• Browser [e.g. chrome, safari]

Additional context
Add any other context about the problem here.

Can not connect to the backend.

What happened?

Just start learning kuma and find it doesn't work as I expect.

logs from pod [kuma-fe]

[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargb" Error (404): "socket hang up"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargb" Error (404): "Not found"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargb" Error (404): "Not found"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargber" Error (404): "socket hang up"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargber" Error (404): "Not found"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargber" Error (404): "Not found"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargberb" Error (404): "socket hang up"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargberb" Error (404): "Not found"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargberb" Error (404): "Not found"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargb" Error (404): "socket hang up"
[2024-01-18T15:46:59.963Z] "GET /items?q=dvadafbgaasdgargasgeargb" Error (404): "Not found"
[2024-01-18T15:46:59.964Z] "GET /items?q=dvadafbgaasdgargasgeargb" Error (404): "Not found"
[2024-01-18T15:46:59.964Z] "GET /items?q=dvadafbgaasdgargasgeargberbd" Error (404): "socket hang up"
[2024-01-18T15:46:59.964Z] "GET /items?q=dvadafbgaasdgargasgeargberbd" Error (404): "Not found"
[2024-01-18T15:46:59.964Z] "GET /items?q=dvadafbgaasdgargasgeargberbd" Error (404): "Not found"

➜  ~ kumactl get traffic-permissions
MESH      NAME                  AGE
default   backend-to-postgres   10m
default   backend-to-redis      9m
default   frontend-to-backend   10m
default   kong-to-frontend      10m
➜  ~
➜  ~ kubectl get pods -n kuma-demo
NAME                                   READY   STATUS    RESTARTS   AGE
kuma-demo-backend-v0-56dd45c8d-gqvb2   2/2     Running   0          26m
postgres-master-bd8696f6c-mxzbd        2/2     Running   0          26m
redis-master-fc564bf85-hbhnz           2/2     Running   0          26m
kuma-demo-app-66468cb454-9777c         2/2     Running   0          26m
➜  ~
➜  ~ kumactl inspect dataplanes
MESH      NAME                                             TAGS                                                                                                                                                                                                                                        STATUS   LAST CONNECTED AGO   LAST UPDATED AGO   TOTAL UPDATES   TOTAL ERRORS   CERT REGENERATED AGO   CERT EXPIRATION       CERT REGENERATIONS   CERT BACKEND   SUPPORTED CERT BACKENDS   KUMA-DP VERSION   ENVOY VERSION   DEPENDENCIES VERSIONS   NOTES
default   kuma-demo-app-66468cb454-9777c.kuma-demo         app=kuma-demo-frontend env=prod k8s.kuma.io/namespace=kuma-demo k8s.kuma.io/service-name=frontend k8s.kuma.io/service-port=8080 kuma.io/protocol=http kuma.io/service=frontend_kuma-demo_svc_8080 pod-template-hash=66468cb454 version=v8   Online   26m                  9m                 29              0              22m                    2024-01-19 23:31:55   1                    ca-1           ca-1                      2.5.1             1.28.0          -
default   kuma-demo-backend-v0-56dd45c8d-gqvb2.kuma-demo   app=kuma-demo-backend env=prod k8s.kuma.io/namespace=kuma-demo k8s.kuma.io/service-name=backend k8s.kuma.io/service-port=3001 kuma.io/protocol=http kuma.io/service=backend_kuma-demo_svc_3001 pod-template-hash=56dd45c8d version=v0       Online   26m                  11m                26              0              22m                    2024-01-19 23:31:55   1                    ca-1           ca-1                      2.5.1             1.28.0          -
default   postgres-master-bd8696f6c-mxzbd.kuma-demo        app=postgres k8s.kuma.io/namespace=kuma-demo k8s.kuma.io/service-name=postgres k8s.kuma.io/service-port=5432 kuma.io/protocol=tcp kuma.io/service=postgres_kuma-demo_svc_5432 pod-template-hash=bd8696f6c                                   Online   26m                  11m                26              0              22m                    2024-01-19 23:31:55   1                    ca-1           ca-1                      2.5.1             1.28.0          -
default   redis-master-fc564bf85-hbhnz.kuma-demo           app=redis k8s.kuma.io/namespace=kuma-demo k8s.kuma.io/service-name=redis k8s.kuma.io/service-port=6379 kuma.io/protocol=tcp kuma.io/service=redis_kuma-demo_svc_6379 pod-template-hash=fc564bf85 role=master tier=backend                   Online   26m                  10m                26              0              22m                    2024-01-19 23:31:55   1                    ca-1           ca-1                      2.5.1             1.28.0          -
➜  ~

Is there anything I can do to find out what's going on?

BTW the image link in https://github.com/kumahq/kuma-demo/blob/master/kubernetes/README.md all failed.

Refresh Vagrant demo

Description

The vagrant demo is not maintained anymore but it's still pretty useful. We should make it work again!

need to update vagrant demo to 1.3.0

kumahq/kuma#2729

search bar doesn't allow space key as input

kind cluster need to be upgraded to latest kuma and kind.

Describe the bug
https://github.com/kumahq/kuma-demo/blob/master/kind/kind.sh#L4-L7
this need to be updated.

kunalsingt@kunalsingt-ubt:~/kuma-demo/kind$ sudo ./kind.sh 
64-bit platform found
Installing Kind v0.8.1
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   624  100   624    0     0    577      0  0:00:01  0:00:01 --:--:--   577
100 9900k  100 9900k    0     0  1850k      0  0:00:05  0:00:05 --:--:-- 2415k
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    10  100    10    0     0      5      0  0:00:02  0:00:01  0:00:01     5

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
ERROR: failed to list clusters: command "docker ps -a --filter label=io.x-k8s.kind.cluster=kuma --format '{{.Names}}'" failed with error: exit status 1
Command Output: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
W0904 19:48:10.975369   47688 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
W0904 19:48:14.078250   47735 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
W0904 19:48:17.182898   47763 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
W0904 19:48:20.315043   47799 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
W0904 19:48:23.501115   47840 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
W0904 19:48:26.633128   47873 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
W0904 19:48:29.751854   47911 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
W0904 19:48:32.871297   47942 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
W0904 19:48:35.966585   47982 loader.go:221] Config not found: /root/.kube/kind-kuma-config
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Waiting for the cluster to come up
c^C````

Discuss moving kuma-demo images under official kuma account

Description

Following on #159 (comment) - I believe we should move demo images under the official kuma account.

Improving Quick-Start guide for Vagrant based setup

Summary

https://kuma.io/docs/0.5.1/quickstart/universal/
Vagrant 2.2.5 with VirtualBox 5.2.42 on Windows-10, Kuma Version 0.5.1, Universal Mode

Steps To Reproduce

Followed setups listed https://kuma.io/docs/0.5.1/quickstart/universal/
During Vagrant UP, it errors out with at npm setup for "backend" service.
This is due to symlink restrictions on Windows (by default on Administrators can create symlink) as documented at https://github.com/npm/npm/issues/9901

Workaround is the do following and re-login or restart windows ::

Right click on Start→Run and launch secpol.msc.

Open Security Settings → Local Policies → User Rights Assignment and select Create symbolic links (that represents SeCreateSymbolicLinkPrivilege).
https://i.stack.imgur.com/o8J8x.png
)Double-click on the item and add yourself (or the whole Users group) to the list.
The changes will apply when you log out and log in again.

Also ssh-ing into individual VMs via Vagrant will leave you with read-only permissions and commands documented in the guide will give you permission errors and will not work. Workaround is to use "sudo" for each kuma shell commands you want to execute against.

Additional Details & Logs

Error:
backend: SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) backend: + [email protected] backend: added 243 packages from 178 contributors in 23.27s backend: npm backend: backend: WARN backend: backend No repository field. backend: npm backend: backend: WARN backend: backend No license field. backend: npm backend: backend: ERR! backend: backend: code backend: EPROTO backend: npm backend: backend: ERR! backend: backend: syscall backend: symlink backend: npm backend: backend: ERR! backend: backend: path backend: ../mime/cli.js backend: npm ERR! dest /home/vagrant/kuma-demo/backend/node_modules/.bin/mime backend: npm ERR! errno -71 backend: npm ERR! EPROTO: protocol error, symlink '../mime/cli.js' -> '/home/vagrant/kuma-demo/backend/node_modules/.bin/mime' backend: npm backend: backend: ERR! backend: A complete log of this run can be found in: backend: npm backend: backend: ERR!

how to set a global traffic permission so that k8s namespace pods cannot access k8s namespace pods

how to set a global traffic permission so that k8s namespace pods cannot access k8s namespace pods ，pods of A k8s namespace cannot access pods of B k8s namespace 。how to set in k8s yml file

---

apiVersion: kuma.io/v1alpha1
kind: TrafficPermission
mesh: default
metadata:
name: allow-all-traffic
spec:
sources:
- match:
kuma.io/service: ''
destinations:
- match:
kuma.io/service: ''

redis can not start success-

vagrant up
and See error
redis not start
and I vagrant ssh to redis vm,run script, I found script can not make directory in /home/vagrant

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Kuma: [e.g. v0.3.1]
• Environment [e.g. Kubernetes, Universal]
• Browser [e.g. chrome, safari]

Additional context
Add any other context about the problem here.

Include `LimitNOFILE` setting into all `systemd` unit files in this repo

Problem

• systemd unit files in this repository don't include LimitNOFILE setting
• it happens that systemd doesn't take into account resource limits set by ulimit
• by default systemd uses the following settings

  LimitNOFILE=4096
  LimitNOFILESoft=1024

• as a result, kuma-dp (Envoy) might crash when those limits are exceeded with an error message like this

  Mar 02 02:47:32 example-dataplane kuma-dp[3518]: 2020-03-02T02:47:32.939-0600    INFO    kuma-dp.run    stopped Dataplane (Envoy)
  Mar 02 02:47:32 example-dataplane kuma-dp[3518]: Error: signal: aborted
  Mar 02 02:47:32 example-dataplane systemd[1]: kuma-dp.service: main process exited, code=exited, status=1/FAILURE
  Mar 02 02:47:32 example-dataplane systemd[1]: Unit kuma-dp.service entered failed state.
  Mar 02 02:47:32 example-dataplane systemd[1]: kuma-dp.service failed.
  Mar 02 02:47:34 example-dataplane systemd[1]: kuma-dp.service holdoff time over, scheduling restart.
  Mar 02 02:47:34 example-dataplane systemd[1]: Stopped Kuma dataplane deployed next to the kuma-example service..
  Mar 02 02:47:34 example-dataplane systemd[1]: Started Kuma dataplane deployed next to the kuma-example service..
  

• the solution is to set LimitNOFILE setting as part of systemd unit file, e.g.

  [Unit]
  Description=Kuma dataplane deployed next to the "backend" service.
  After=network.target
  Documentation=https://kuma.io
  
  [Service]
  Environment=KUMA_DATAPLANE_MESH=default
  Environment=KUMA_DATAPLANE_NAME=backend
  Environment=KUMA_CONTROL_PLANE_API_SERVER_URL=http://kuma-cp:5681 
  Environment=KUMA_DATAPLANE_RUNTIME_TOKEN_PATH=...
  Environment=KUMA_DATAPLANE_ADMIN_PORT=9901
  ExecStart=/opt/kuma/bin/kuma-dp run
  LimitNOFILE=500000
  Restart=always
  RestartSec=1s
  # disable rate limiting on start attempts
  StartLimitIntervalSec=0
  StartLimitBurst=0
  User=vagrant
  
  [Install]
  WantedBy=multi-user.target
  

How to check effective LimitNOFILE value

Check via systemd

• Run

  systemctl show <unit name> | grep LimitNOFILE

  e.g.,

  systemctl show kuma-dp | grep LimitNOFILE
  
  LimitNOFILE=4096
  LimitNOFILESoft=1024

Check in systemd-independent manner

• Run

  cat /proc/`pgrep envoy`/limits

e.g.,

cat /proc/`pgrep envoy`/limits

Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes 
Max processes             3895                 3895                 processes 
Max open files            1024                 4096                 files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       3895                 3895                 signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us 

References

• https://fredrikaverpil.github.io/2016/04/27/systemd-and-resource-limits/
• https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Process%20Properties

vagrant install npm syscall symlink errors for backend and backend-v1

Describe the bug
Vagrant had the following errors while building the backend and backend-v1 containers.

Errors:
backend: ERR! syscall symlink
backend: npm ERR! path ../mime/cli.js
backend: npm ERR! dest /home/vagrant/kuma-demo/backend/node_modules/.bin/mime
backend: npm ERR! errno -71
backend: npm ERR! EPROTO: protocol error, symlink '../mime/cli.js' -> '/home/vagrant/kuma-demo/backend/node_modules/.bi

To Reproduce
Steps to reproduce the behavior:

1. Clone kuma-demo master branch
2. vagrant up

Fix:
Update both files:
~/vagrant/backend/app/install.sh
~/vagrant/backend-v1/app/install.sh

Change line from:
npm install

Change line to:
npm install --no-bin-links

Desktop (please complete the following information):

• OS: Windows
• Kuma: 0.7.1
• Environment: Vagrant

Connection pool for Redis & Elasticsearch

It seems that connections for Redis are created but not reused, they also seems to live long.

I deployed the app on K8S and enabled passive and active healthchecks. Then I run wrk test on backend app that communicated with Redis. Envoy has limit on 1024 connections per destination service. What happened is that backend used all 1024 connections to Redis and then active HC was failing because HC also use the same pool of 1024 connections. Effectively I had to wait for connection to be dropped or kill the pod with backend.

The same thing happened with Elastic although connections to Elastic are closed fairly quickly.

We should introduce connection pools for both dependencies, with connection limit to something about ~100.

Backend times out when connecting to the db: e.g. /items endpoint

Symptoms: No error messages, just timeout after 15s

My solution: I had to manually upgrade the lib version

npm install [email protected]

vagrant demo prometheus file is missing.

https://github.com/kumahq/kuma-demo/blob/master/vagrant/metrics/app/prometheus/prometheus.yaml#L6

this file is missing and that's why Prometheus is not able to scrape anything because the rule file is missing.

kill connection for cluster.localhost_9200.upstream_cx_active

How do I use kuma on the intranet that Can't connect to the internet . Because DP (data-plane) dynamically inject into my services pod, I cannot set up to pull DP (data-plane) docker images from my private mirror warehouse harbor.

How do I use kuma on the intranet that Can't connect to the internet . Because DP (data-plane) dynamically inject into my services pod, I cannot set up to pull DP (data-plane) docker images from my private mirror warehouse harbor.

market-items no longer exists

When trying to do a GET from http://localhost:3001/items?q= after running yarn api:elasticsearch, I receive an error stating that the market-items index doesn't exist:

{
  "msg": "[index_not_found_exception] no such index [market-items], with { resource.type=\"index_or_alias\" & resource.id=\"market-items\" & index_uuid=\"_na_\" & index=\"market-items\" }",
  "path": "/market-items/_search",
  "query": {},
  "body": "{\"size\":200,\"from\":0,\"query\":{\"query_string\":{\"default_field\":\"name\",\"query\":\"**\"}}}",
  "statusCode": 404,
  "response": "{\"error\":{\"root_cause\":[{\"type\":\"index_not_found_exception\",\"reason\":\"no such index [market-items]\",\"resource.type\":\"index_or_alias\",\"resource.id\":\"market-items\",\"index_uuid\":\"_na_\",\"index\":\"market-items\"}],\"type\":\"index_not_found_exception\",\"reason\":\"no such index [market-items]\",\"resource.type\":\"index_or_alias\",\"resource.id\":\"market-items\",\"index_uuid\":\"_na_\",\"index\":\"market-items\"},\"status\":404}"
}

Any ideas? Maybe the data import when the ES container runs isn't happening? I know we were talking about moving that function elsewhere.

grafana vagrant does not showing any metrics as its not imported.

vagrant up fails with "file not found" error

Describe the bug
vagrant up fails with "file not found" error.

To Reproduce
Steps to reproduce the behavior:
set up kuma-demo following to https://kuma.io/docs/0.7.1/quickstart/universal/ and it fails at vagrant up with "file not found" error when trying to create "postgresql" VM.
I suggest this is due to postgresql's version up from 12 to 13.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Ubuntu
• Kuma: v0.7.1
• Environment Universal

Additional context
Add any other context about the problem here.

When running vagrant up deployment errors out

What happened?

MacOS - 12.2.1
Virtual box - 6.1.32
VB extensions - 6.1.32
Vagrant - 2.2..19

So I was trying to spin up the kuma-demo but I just error out after creating the first VM. There seems no way to ssh to the VM either. Here is the output from my attempt.

How do I get the VM to run without this erroring out?

Bringing machine 'kuma-control-plane' up with 'virtualbox' provider...
Bringing machine 'redis' up with 'virtualbox' provider...
Bringing machine 'postgresql' up with 'virtualbox' provider...
Bringing machine 'metrics' up with 'virtualbox' provider...
Bringing machine 'backend' up with 'virtualbox' provider...
Bringing machine 'backend-v1' up with 'virtualbox' provider...
Bringing machine 'frontend' up with 'virtualbox' provider...
Bringing machine 'kong' up with 'virtualbox' provider...
==> kuma-control-plane: Checking if box 'ubuntu/trusty64' version '20190514.0.0' is up to date...
==> kuma-control-plane: Clearing any previously set forwarded ports...
==> kuma-control-plane: Clearing any previously set network interfaces...
==> kuma-control-plane: Preparing network interfaces based on configuration...
    kuma-control-plane: Adapter 1: nat
    kuma-control-plane: Adapter 2: hostonly
==> kuma-control-plane: Forwarding ports...
    kuma-control-plane: 22 (guest) => 2222 (host) (adapter 1)
==> kuma-control-plane: Running 'pre-boot' VM customizations...
==> kuma-control-plane: Booting VM...
==> kuma-control-plane: Waiting for machine to boot. This may take a few minutes...
    kuma-control-plane: SSH address: 127.0.0.1:2222
    kuma-control-plane: SSH username: vagrant
    kuma-control-plane: SSH auth method: private key
==> kuma-control-plane: Machine booted and ready!
[kuma-control-plane] A Virtualbox Guest Additions installation was found but no tools to rebuild or start them.
 * Stopping VirtualBox Additions
   ...done.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  acl at-spi2-core colord dconf-gsettings-backend dconf-service fontconfig
  fontconfig-config fonts-dejavu-core hicolor-icon-theme libasound2
  libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0
  libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2
  libcairo2 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra0 libcolord1
  libcolorhug1 libcups2 libdatrie1 libdconf1 libdrm-intel1 libdrm-nouveau2
  libdrm-radeon1 libexif12 libfontconfig1 libfontenc1 libgd3
  libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx
  libglapi-mesa libgphoto2-6 libgphoto2-l10n libgphoto2-port10 libgraphite2-3
  libgtk-3-0 libgtk-3-bin libgtk-3-common libgudev-1.0-0 libgusb2
  libharfbuzz0b libice6 libieee1284-3 libjasper1 libjbig0 libjpeg-turbo8
  libjpeg8 liblcms2-2 libllvm3.4 libltdl7 libnotify-bin libnotify4 libogg0
  libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpciaccess0
  libpixman-1-0 libsane libsane-common libsm6 libtdb1 libthai-data libthai0
  libtiff5 libtxc-dxtn-s2tc0 libv4l-0 libv4lconvert0 libvorbis0a
  libvorbisfile3 libvpx1 libwayland-client0 libwayland-cursor0 libx11-xcb1
  libxaw7 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0
  libxcb-render0 libxcb-shm0 libxcb-sync1 libxcomposite1 libxcursor1
  libxdamage1 libxfixes3 libxfont1 libxi6 libxinerama1 libxkbcommon0
  libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1 libxshmfence1 libxt6
  libxtst6 libxxf86vm1 notification-daemon sound-theme-freedesktop x11-common
  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common
  xserver-xorg-core
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  virtualbox-guest-dkms* virtualbox-guest-utils* virtualbox-guest-x11*
0 upgraded, 0 newly installed, 3 to remove and 1 not upgraded.
After this operation, 12.2 MB disk space will be freed.
(Reading database ... 69698 files and directories currently installed.)
Removing virtualbox-guest-dkms (4.3.40-dfsg-0ubuntu14.04.1) ...

-------- Uninstall Beginning --------
Module:  virtualbox-guest
Version: 4.3.40
Kernel:  3.13.0-170-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxguest.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.13.0-170-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxsf.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.13.0-170-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxvideo.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.13.0-170-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod.....

DKMS: uninstall completed.

------------------------------
Deleting module version: 4.3.40
completely from the DKMS tree.
------------------------------
Done.
Removing virtualbox-guest-x11 (4.3.40-dfsg-0ubuntu14.04.1) ...
Purging configuration files for virtualbox-guest-x11 (4.3.40-dfsg-0ubuntu14.04.1) ...
Removing virtualbox-guest-utils (4.3.40-dfsg-0ubuntu14.04.1) ...
Purging configuration files for virtualbox-guest-utils (4.3.40-dfsg-0ubuntu14.04.1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.15) ...
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version.
linux-headers-3.13.0-170-generic is already the newest version.
The following packages were automatically installed and are no longer required:
  acl at-spi2-core colord dconf-gsettings-backend dconf-service fontconfig
  fontconfig-config fonts-dejavu-core hicolor-icon-theme libasound2
  libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0
  libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2
  libcairo2 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra0 libcolord1
  libcolorhug1 libcups2 libdatrie1 libdconf1 libdrm-intel1 libdrm-nouveau2
  libdrm-radeon1 libexif12 libfontconfig1 libfontenc1 libgd3
  libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx
  libglapi-mesa libgphoto2-6 libgphoto2-l10n libgphoto2-port10 libgraphite2-3
  libgtk-3-0 libgtk-3-bin libgtk-3-common libgudev-1.0-0 libgusb2
  libharfbuzz0b libice6 libieee1284-3 libjasper1 libjbig0 libjpeg-turbo8
  libjpeg8 liblcms2-2 libllvm3.4 libltdl7 libnotify-bin libnotify4 libogg0
  libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpciaccess0
  libpixman-1-0 libsane libsane-common libsm6 libtdb1 libthai-data libthai0
  libtiff5 libtxc-dxtn-s2tc0 libv4l-0 libv4lconvert0 libvorbis0a
  libvorbisfile3 libvpx1 libwayland-client0 libwayland-cursor0 libx11-xcb1
  libxaw7 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0
  libxcb-render0 libxcb-shm0 libxcb-sync1 libxcomposite1 libxcursor1
  libxdamage1 libxfixes3 libxfont1 libxi6 libxinerama1 libxkbcommon0
  libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1 libxshmfence1 libxt6
  libxtst6 libxxf86vm1 notification-daemon sound-theme-freedesktop x11-common
  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common
  xserver-xorg-core
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only
Installing Virtualbox Guest Additions 6.1.32 - guest version is 4.3.40
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.32 Guest Additions for Linux........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 3.13.0-170-generic.
 Adding system startup for /etc/init.d/vboxadd ...
   /etc/rc0.d/K90vboxadd -> ../init.d/vboxadd
   /etc/rc1.d/K90vboxadd -> ../init.d/vboxadd
   /etc/rc6.d/K90vboxadd -> ../init.d/vboxadd
   /etc/rc2.d/S10vboxadd -> ../init.d/vboxadd
   /etc/rc3.d/S10vboxadd -> ../init.d/vboxadd
   /etc/rc4.d/S10vboxadd -> ../init.d/vboxadd
   /etc/rc5.d/S10vboxadd -> ../init.d/vboxadd
 Adding system startup for /etc/init.d/vboxadd-service ...
   /etc/rc0.d/K65vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc1.d/K65vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc6.d/K65vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc2.d/S35vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc3.d/S35vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc4.d/S35vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc5.d/S35vboxadd-service -> ../init.d/vboxadd-service
Building the VirtualBox Guest Additions kernel modules.  This may take a while.
To build modules for other installed kernels, run
  /sbin/rcvboxadd quicksetup <version>
or
  /sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Unmounting Virtualbox Guest Additions ISO from: /mnt
==> kuma-control-plane: Checking for guest additions in VM...
==> kuma-control-plane: Setting hostname...
==> kuma-control-plane: Configuring and enabling network interfaces...
==> kuma-control-plane: Mounting shared folders...
    kuma-control-plane: /vagrant => /Users/jasmor/Documents/Code/temp/kuma-demo/vagrant
==> kuma-control-plane: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> kuma-control-plane: flag to force provisioning. Provisioners marked to run always will still run.
==> kuma-control-plane: Running provisioner: await_kuma-cp (shell)...
    kuma-control-plane: Running: /var/folders/4t/q11wg0bd25l9sx4pmn3h4z700000gp/T/vagrant-shell20220223-10584-j65kyu.sh
    kuma-control-plane: try #1:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #2:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #3:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #4:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #5:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #6:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #7:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #8:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #9:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #10:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #11:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #12:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #13:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #14:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #15:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #16:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #17:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #18:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #19:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #20:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #21:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #22:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #23:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #24:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
^C==> kuma-control-plane: Waiting for cleanup before exiting...

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.