Installation fails on Ubuntu 20.04 #4317

bxiiiiii · 2022-07-04T07:12:15Z

Describe the bug

Installation fails on Ubuntu 20.04
To Reproduce

I am using the Installation from the documentation until using sudo velad install

Screenshots

FogDong · 2022-07-04T07:13:33Z

cc @chivalryq

bxiiiiii · 2022-07-04T07:15:39Z

What more information is needed?

chivalryq · 2022-07-04T07:30:28Z

Cluster is ready. You can run this to check the vela-core deployment status.

export KUBECONFIG=$(velad kubeconfig --host)
kubectl get deploy -n vela-system -o yaml kubevela-vela-core

@bxiiiiii

bxiiiiii · 2022-07-04T07:32:52Z

Error from server (NotFound): deployments.apps "kubevela-vela-core" not found

bxiiiiii · 2022-07-04T07:41:19Z

chivalryq · 2022-07-04T07:42:43Z

Oh, sorry, installation fails at "pre-install" stage.

Try get jobs at pre-install stage:

kubectl get job -A

kubectl get job kubevela-vela-core-cluster-gateway-tls-secret-create -o yaml -n vela-system

kubectl get job kubevela-vela-core-cluster-gateway-tls-secret-patch -o yaml -n vela-system

bxiiiiii · 2022-07-04T07:46:50Z

chivalryq · 2022-07-04T07:46:52Z

Actually you can try

velad uninstall and velad install again to see if it is reproducable.
or
vela install --version=1.4.5

chivalryq · 2022-07-04T07:47:45Z

try kubectl get job -n vela-system -o yaml kubevela-vela-core-admission-create

bxiiiiii · 2022-07-04T08:30:38Z

其实你可以试试

velad uninstall并velad install再次查看它是否可重现。
或者

vela install --version=1.4.5

still fails

bxiiiiii · 2022-07-04T08:31:19Z

尝试kubectl get job -n vela-system -o yaml kubevela-vela-core-admission-create

chivalryq · 2022-07-04T08:33:48Z

Sorry but you didn't show all the infomation of kubectl get job, could you paste all as text? @bxiiiiii

bxiiiiii · 2022-07-04T08:44:13Z

抱歉，您没有显示的所有信息kubectl get job，您可以将所有信息都粘贴为文本吗？@bxiiiiii

No resources found in default namespace.

bxiiiiii · 2022-07-04T08:46:02Z

when using kubectl get job -A

NAMESPACE NAME COMPLETIONS DURATION AGE
kube-system helm-install-traefik-crd 0/1 33m 33m
kube-system helm-install-traefik 0/1 33m 33m
vela-system kubevela-vela-core-admission-create 0/1 33m 33m

chivalryq · 2022-07-04T08:55:43Z

Sorry, I shorten the command, I mean can you paste all information of

kubectl get job -n vela-system -o yaml kubevela-vela-core-admission-create

bxiiiiii · 2022-07-04T09:07:23Z

apiVersion: batch/v1
kind: Job
metadata:
annotations:
helm.sh/hook: pre-install,pre-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
creationTimestamp: "2022-07-04T08:10:37Z"
labels:
app: vela-core-admission-create
app.kubernetes.io/instance: kubevela
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: vela-core
app.kubernetes.io/version: v1.4.3
helm.sh/chart: vela-core-v1.4.3
name: kubevela-vela-core-admission-create
namespace: vela-system
resourceVersion: "600"
uid: c1ed86a7-757a-4632-8484-72cdac16c968
spec:
backoffLimit: 6
completions: 1
parallelism: 1
selector:
matchLabels:
controller-uid: c1ed86a7-757a-4632-8484-72cdac16c968
template:
metadata:
creationTimestamp: null
labels:
app: vela-core-admission-create
app.kubernetes.io/instance: kubevela
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: vela-core
app.kubernetes.io/version: v1.4.3
controller-uid: c1ed86a7-757a-4632-8484-72cdac16c968
helm.sh/chart: vela-core-v1.4.3
job-name: kubevela-vela-core-admission-create
name: kubevela-vela-core-admission-create
spec:
containers:
- args:
- create
- --host=vela-core-webhook,vela-core-webhook.vela-system.svc
- --namespace=vela-system
- --secret-name=kubevela-vela-core-admission
- --key-name=tls.key
- --cert-name=tls.crt
image: oamdev/kube-webhook-certgen:v2.4.1
imagePullPolicy: IfNotPresent
name: create
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
restartPolicy: OnFailure
schedulerName: default-scheduler
securityContext:
runAsGroup: 2000
runAsNonRoot: true
runAsUser: 2000
serviceAccount: kubevela-vela-core-admission
serviceAccountName: kubevela-vela-core-admission
terminationGracePeriodSeconds: 30
status:
active: 1
startTime: "2022-07-04T08:10:37Z"

chivalryq · 2022-07-04T09:24:36Z

What about kubectl describe job -n vela-system kubevela-vela-core-admission-create?

bxiiiiii · 2022-07-04T09:26:47Z

kubectl describe job -n vela-system kubevela-vela-core-admission-create

Name: kubevela-vela-core-admission-create
Namespace: vela-system
Selector: controller-uid=c1ed86a7-757a-4632-8484-72cdac16c968
Labels: app=vela-core-admission-create
app.kubernetes.io/instance=kubevela
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=vela-core
app.kubernetes.io/version=v1.4.3
helm.sh/chart=vela-core-v1.4.3
Annotations: helm.sh/hook: pre-install,pre-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
Parallelism: 1
Completions: 1
Start Time: Mon, 04 Jul 2022 16:10:37 +0800
Pods Statuses: 1 Running / 0 Succeeded / 0 Failed
Pod Template:
Labels: app=vela-core-admission-create
app.kubernetes.io/instance=kubevela
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=vela-core
app.kubernetes.io/version=v1.4.3
controller-uid=c1ed86a7-757a-4632-8484-72cdac16c968
helm.sh/chart=vela-core-v1.4.3
job-name=kubevela-vela-core-admission-create
Service Account: kubevela-vela-core-admission
Containers:
create:
Image: oamdev/kube-webhook-certgen:v2.4.1
Port:
Host Port:
Args:
create
--host=vela-core-webhook,vela-core-webhook.vela-system.svc
--namespace=vela-system
--secret-name=kubevela-vela-core-admission
--key-name=tls.key
--cert-name=tls.crt
Environment:
Mounts:
Volumes:
Events:

bxiiiiii · 2022-07-04T09:28:46Z

kubectl describe job -n vela-system kubevela-vela-core-admission-create

Name: kubevela-vela-core-admission-create Namespace: vela-system Selector: controller-uid=c1ed86a7-757a-4632-8484-72cdac16c968 Labels: app=vela-core-admission-create app.kubernetes.io/instance=kubevela app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=vela-core app.kubernetes.io/version=v1.4.3 helm.sh/chart=vela-core-v1.4.3 Annotations: helm.sh/hook: pre-install,pre-upgrade helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded Parallelism: 1 Completions: 1 Start Time: Mon, 04 Jul 2022 16:10:37 +0800 Pods Statuses: 1 Running / 0 Succeeded / 0 Failed Pod Template: Labels: app=vela-core-admission-create app.kubernetes.io/instance=kubevela app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=vela-core app.kubernetes.io/version=v1.4.3 controller-uid=c1ed86a7-757a-4632-8484-72cdac16c968 helm.sh/chart=vela-core-v1.4.3 job-name=kubevela-vela-core-admission-create Service Account: kubevela-vela-core-admission Containers: create: Image: oamdev/kube-webhook-certgen:v2.4.1 Port: Host Port: Args: create --host=vela-core-webhook,vela-core-webhook.vela-system.svc --namespace=vela-system --secret-name=kubevela-vela-core-admission --key-name=tls.key --cert-name=tls.crt Environment: Mounts: Volumes: Events:

Port / Host Port / Evironment / Mounts / Volumes / Event are none

chivalryq · 2022-07-04T09:31:44Z

The pod is running, check the pod status:

kubectl get pod -n vela-system

and replace the pod name in following command.

kubectl get pod -n vela-system kubevela-vela-core-admission-create-xxxxx -oyaml
kubectl describe pod -n vela-system kubevela-vela-core-admission-create-xxxxx

Also a tip: GitHub support Markdown syntax, try wrap code like

``` yaml
yaml here
```

bxiiiiii · 2022-07-04T09:39:31Z

The pod is running, check the pod status:
kubectl get pod -n vela-system
and
kubectl get pod -n vela-system kubevela-vela-core-admission-create-xxxxx -oyaml
kubectl describe pod -n vela-system kubevela-vela-core-admission-create-xxxxx
Also a tip: GitHub support Markdown syntax, try wrap code like

yaml yaml here

kubectl get pod -n vela-system

NAME                                        READY   STATUS    RESTARTS   AGE
kubevela-vela-core-admission-create-s644k   0/1     Pending   0          82m

kubectl get pod -n vela-system kubevela-vela-core-admission-create-s644k -oyaml

apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: "2022-07-04T08:10:37Z"
  generateName: kubevela-vela-core-admission-create-
  labels:
    app: vela-core-admission-create
    app.kubernetes.io/instance: kubevela
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: vela-core
    app.kubernetes.io/version: v1.4.3
    controller-uid: c1ed86a7-757a-4632-8484-72cdac16c968
    helm.sh/chart: vela-core-v1.4.3
    job-name: kubevela-vela-core-admission-create
  name: kubevela-vela-core-admission-create-s644k
  namespace: vela-system
  ownerReferences:
  - apiVersion: batch/v1
    blockOwnerDeletion: true
    controller: true
    kind: Job
    name: kubevela-vela-core-admission-create
    uid: c1ed86a7-757a-4632-8484-72cdac16c968
  resourceVersion: "599"
  uid: b1dff55e-2c3f-41e0-959e-7ffcf5525801
spec:
  containers:
  - args:
    - create
    - --host=vela-core-webhook,vela-core-webhook.vela-system.svc
    - --namespace=vela-system
    - --secret-name=kubevela-vela-core-admission
    - --key-name=tls.key
    - --cert-name=tls.crt
    image: oamdev/kube-webhook-certgen:v2.4.1
    imagePullPolicy: IfNotPresent
    name: create
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-pctzl
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: OnFailure
  schedulerName: default-scheduler
  securityContext:
    runAsGroup: 2000
    runAsNonRoot: true
    runAsUser: 2000
  serviceAccount: kubevela-vela-core-admission
  serviceAccountName: kubevela-vela-core-admission
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - name: kube-api-access-pctzl
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          items:
          - key: ca.crt
            path: ca.crt
          name: kube-root-ca.crt
      - downwardAPI:
          items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
            path: namespace
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2022-07-04T08:10:37Z"
    message: '0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/disk-pressure:
      }, that the pod didn''t tolerate.'
    reason: Unschedulable
    status: "False"
    type: PodScheduled
  phase: Pending
  qosClass: BestEffort

kubectl describe pod -n vela-system kubevela-vela-core-admission-create-s644k

Name:           kubevela-vela-core-admission-create-s644k
Namespace:      vela-system
Priority:       0
Node:           <none>
Labels:         app=vela-core-admission-create
                app.kubernetes.io/instance=kubevela
                app.kubernetes.io/managed-by=Helm
                app.kubernetes.io/name=vela-core
                app.kubernetes.io/version=v1.4.3
                controller-uid=c1ed86a7-757a-4632-8484-72cdac16c968
                helm.sh/chart=vela-core-v1.4.3
                job-name=kubevela-vela-core-admission-create
Annotations:    <none>
Status:         Pending
IP:             
IPs:            <none>
Controlled By:  Job/kubevela-vela-core-admission-create
Containers:
  create:
    Image:      oamdev/kube-webhook-certgen:v2.4.1
    Port:       <none>
    Host Port:  <none>
    Args:
      create
      --host=vela-core-webhook,vela-core-webhook.vela-system.svc
      --namespace=vela-system
      --secret-name=kubevela-vela-core-admission
      --key-name=tls.key
      --cert-name=tls.crt
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-pctzl (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  kube-api-access-pctzl:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  88m   default-scheduler  0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate.

charlie0129 · 2022-07-04T10:25:55Z

1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate.

Do you have enough disk space available? If not, find a way to reclaim free space.

bxiiiiii · 2022-07-04T10:59:37Z

1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate.

Do you have enough disk space available? If not, find a way to reclaim free space.

got it.

chivalryq · 2022-07-05T13:24:18Z

Closing since we have found the problem. Feel free to reopen it if you still have problems about VelaD installation @bxiiiiii :D

FogDong added the needs more info the issue is not clear and more information need to be added label Jul 4, 2022

chivalryq added bot/question the bot will close with standard question message and add label type/question and removed needs more info the issue is not clear and more information need to be added labels Jul 5, 2022

chivalryq closed this as completed Jul 5, 2022

charlie0129 mentioned this issue Jul 27, 2022

Self-nominate @charlie0129 as approver kubevela/community#58

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Installation fails on Ubuntu 20.04 #4317

Installation fails on Ubuntu 20.04 #4317

bxiiiiii commented Jul 4, 2022

FogDong commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022 •

edited

Loading

bxiiiiii commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022 •

edited

Loading

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022

chivalryq commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022 •

edited

Loading

bxiiiiii commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022 •

edited

Loading

chivalryq commented Jul 4, 2022 •

edited

Loading

bxiiiiii commented Jul 4, 2022

charlie0129 commented Jul 4, 2022 •

edited

Loading

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 5, 2022 •

edited

Loading

Installation fails on Ubuntu 20.04 #4317

Installation fails on Ubuntu 20.04 #4317

Comments

bxiiiiii commented Jul 4, 2022

FogDong commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022 • edited Loading

bxiiiiii commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022 • edited Loading

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022

chivalryq commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022 • edited Loading

bxiiiiii commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022

bxiiiiii commented Jul 4, 2022 • edited Loading

chivalryq commented Jul 4, 2022 • edited Loading

bxiiiiii commented Jul 4, 2022

charlie0129 commented Jul 4, 2022 • edited Loading

bxiiiiii commented Jul 4, 2022

chivalryq commented Jul 5, 2022 • edited Loading

chivalryq commented Jul 4, 2022 •

edited

Loading

chivalryq commented Jul 4, 2022 •

edited

Loading

chivalryq commented Jul 4, 2022 •

edited

Loading

bxiiiiii commented Jul 4, 2022 •

edited

Loading

chivalryq commented Jul 4, 2022 •

edited

Loading

charlie0129 commented Jul 4, 2022 •

edited

Loading

chivalryq commented Jul 5, 2022 •

edited

Loading