时间戳

首页 > 解决方案 > 关系状态为待处理

acumos - 关系状态为待处理

问题描述

当我部署 Acumos 时，使用命令“bash oneclick_deploy.sh 2>&1 | tee aio_deploy.log”它不成功并打印出“nexus status is Pending”</p>

①我使用了一个现有的k8s集群：Minikube

②命令“bash system-integration/AIO/setup_prereqs.sh k8s localhost $USER generic 2>&1 | tee aio_prep.log”运行成功

kubectl 获取 pods --all-namespaces

master@ubuntu:/home$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                  READY   STATUS    RESTARTS   AGE
acumos        nexus-5b577d94f8-hqxxl                0/1     Pending   0          18m
kube-system   coredns-6967fb4995-p2sjh              1/1     Running   3          3d20h
kube-system   coredns-6967fb4995-p57ml              1/1     Running   3          3d20h
kube-system   etcd-minikube                         1/1     Running   0          5h14m
kube-system   kube-addon-manager-minikube           1/1     Running   2          3d20h
kube-system   kube-apiserver-minikube               1/1     Running   0          5h14m
kube-system   kube-controller-manager-minikube      1/1     Running   2          5h14m
kube-system   kube-proxy-2wqqp                      1/1     Running   1          3d20h
kube-system   kube-scheduler-minikube               1/1     Running   2          3d20h
kube-system   kubernetes-dashboard-95564f4f-wrjgj   1/1     Running   2          3d20h
kube-system   storage-provisioner                   1/1     Running   2          3d20h
kube-system   tiller-deploy-75f5747884-5rnmc        1/1     Running   0          5h8m

kubectl 描述 -n acumos pod nexus-5b577d94f8-hqxxl

master@ubuntu:/home$ kubectl describe -n acumos pod nexus-5b577d94f8-hqxxl
Name:           nexus-5b577d94f8-hqxxl
Namespace:      acumos
Priority:       0
Node:           <none>
Labels:         app=nexus
                pod-template-hash=5b577d94f8
Annotations:    <none>
Status:         Pending
IP:             
Controlled By:  ReplicaSet/nexus-5b577d94f8
Containers:
  nexus:
    Image:       sonatype/nexus:3.9.0
    Ports:       8081/TCP, 8082/TCP
    Host Ports:  0/TCP, 0/TCP
    Environment:
      log_level:  DEBUG
    Mounts:
      /maven/logs from logs (rw)
      /nexus-data from nexus-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-r6d6c (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  logs:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  logs
    ReadOnly:   false
  nexus-data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  nexus-data
    ReadOnly:   false
  default-token-r6d6c:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-r6d6c
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  47s (x2 over 47s)  default-scheduler  pod has unbound immediate PersistentVolumeClaims

这个问题困扰了我很长时间，一直没有解决。如果有人能指导我如何解决这个问题，我将不胜感激。

标签： acumos

解决方案

我可以帮你调试，但请注意我们没有在 minikube 环境中测试过这些工具。Minikube 与单节点 (AIO) k8s 集群的不同之处在于它可能无法正常工作；另请注意，您可以使用脚本https://github.com/acumos/system-integration/blob/master/tools/setup_k8s.sh创建单节点集群（在 Ubuntu 或 Centos 上）。

但是对于您的 minikube 案例，pod 状态的“待处理”状态通常意味着 PV 尚未准备好分配给 PVC。这可能是 minikube 的副作用。“kubectl get pv”的结果是什么？

推荐阅读