In beats CI we see already exists errors:
but still moves on
Also in elastic-agent-poc repo:
15:40:43 configmap/agent-node-datastreams created
15:40:43 Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": daemonsets.apps "elastic-agent" already exists
15:40:43 Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": clusterrolebindings.rbac.authorization.k8s.io "elastic-agent" already exists
15:40:43 Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": rolebindings.rbac.authorization.k8s.io "elastic-agent" already exists
15:40:43 Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": rolebindings.rbac.authorization.k8s.io "elastic-agent-kubeadm-config" already exists
15:40:43 Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": clusterroles.rbac.authorization.k8s.io "elastic-agent" already exists
15:40:43 Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": roles.rbac.authorization.k8s.io "elastic-agent" already exists
15:40:43 Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": roles.rbac.authorization.k8s.io "elastic-agent-kubeadm-config" already exists
15:40:43 Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": serviceaccounts "elastic-agent" already exists
but doesn't move on.
The error seems to be that managed agent is being deployed right after the standalone one and there is conflict in the names, @ChrsMark can you help here?
In beats CI we see
already existserrors:but still moves on
Also in
elastic-agent-pocrepo:but doesn't move on.
The error seems to be that managed agent is being deployed right after the standalone one and there is conflict in the names, @ChrsMark can you help here?