[Question] is there any way to snapshot and recreate the cluster somewhere else

Just a quick thought.
Is there any way to take the entire cluster and provision somewhere else.
Suppose I've one cluster where I run all my apps. If I want to move it to somewhere, I can take a docker snapshot of the images, and re-run in the other machines. But if I have some local storage (local-path-provisioner) and load balancer(which will have some bridge network) will it work?

Hi @rjshrjndrn , that's a good question :grimacing:
k3d itself does not handle any state at all, so there's not much we can do to make it work easier.
However, if you use the local-path-provisioner without a bind mount into k3d (i.e. you don't store the stuff outside of docker's scope), then a snapshot of the docker volume could work.
For the LB I'm not sure, which one you're talking about: a LoadBalancer external to k3d or running inside k3d/k3s?
I've never done something like this, so I cannot really be of help here :grimacing:
However, I suggest you to join the community in slack and post your question there to get some more responses.
Join slack here: https://slack.rancher.io/ and head over to https://rancher-users.slack.com (we also have a #k3d channel there)

For the load balancer, my bad. We can access it with docker ip, or we can expose it as NodePort and then docker port forward.
But I faced one weird issue.
Created a cluster(single node) took docker commit <id> and ran it on another machine, which has docker.
This contains only nginx container and type LoadBalancer svc.
Cluster creation was with
❮ k3d create --server-arg --no-deploy --server-arg traefik --name nginx-test --image rancher/k3s:v0.8.1
But..
❯ docker run rjshrjndrn/k3d-nginx:latest
time="2019-11-13T13:58:07.984960557Z" level=info msg="Starting k3s v0.8.1 (d116e74a)"
time="2019-11-13T13:58:08.600055887Z" level=info msg="Running kube-apiserver --advertise-port=6443 --allow-privileged=true --api-audiences=unknown --authorization-mode=Node,RBAC --basic-auth-file=/var/lib/rancher/k3s/server/cred/passwd --bind-address=<IP_ADDRESS> --cert-dir=/var/lib/rancher/k3s/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction --insecure-port=0 --kubelet-client-certificate=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.key --proxy-client-cert-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/k3s/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6444 --service-account-issuer=k3s --service-account-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-cluster-ip-range=<IP_ADDRESS>/16 --tls-cert-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
I1113 13:58:08.600738       1 server.go:517] external host was not specified, using <IP_ADDRESS>
I1113 13:58:08.601082       1 server.go:148] Version: v1.14.6-k3s.1
I1113 13:58:09.163804       1 plugins.go:158] Loaded 9 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,MutatingAdmissionWebhook.
I1113 13:58:09.163819       1 plugins.go:161] Loaded 6 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,ValidatingAdmissionWebhook,ResourceQuota.
E1113 13:58:09.164756       1 prometheus.go:138] failed to register depth metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.164800       1 prometheus.go:150] failed to register adds metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.164880       1 prometheus.go:162] failed to register latency metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.164954       1 prometheus.go:174] failed to register work_duration metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.165023       1 prometheus.go:189] failed to register unfinished_work_seconds metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.165065       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric admission_quota_controller: duplicate metrics collector registration attempted
I1113 13:58:09.165082       1 plugins.go:158] Loaded 9 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,MutatingAdmissionWebhook.
I1113 13:58:09.165090       1 plugins.go:161] Loaded 6 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,ValidatingAdmissionWebhook,ResourceQuota.
I1113 13:58:09.189945       1 master.go:218] Using reconciler: lease
W1113 13:58:09.275759       1 genericapiserver.go:315] Skipping API batch/v2alpha1 because it has no resources.
W1113 13:58:09.289242       1 genericapiserver.go:315] Skipping API node.k8s.io/v1alpha1 because it has no resources.
E1113 13:58:09.325919       1 prometheus.go:138] failed to register depth metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.325985       1 prometheus.go:150] failed to register adds metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.326080       1 prometheus.go:162] failed to register latency metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.326159       1 prometheus.go:174] failed to register work_duration metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.326199       1 prometheus.go:189] failed to register unfinished_work_seconds metric admission_quota_controller: duplicate metrics collector registration attempted
E1113 13:58:09.326235       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric admission_quota_controller: duplicate metrics collector registration attempted
I1113 13:58:09.326253       1 plugins.go:158] Loaded 9 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,MutatingAdmissionWebhook.
I1113 13:58:09.326272       1 plugins.go:161] Loaded 6 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,ValidatingAdmissionWebhook,ResourceQuota.
time="2019-11-13T13:58:09.332949843Z" level=info msg="Running kube-scheduler --bind-address=<IP_ADDRESS> --kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --leader-elect=false --port=10251 --secure-port=0"
time="2019-11-13T13:58:09.334902938Z" level=info msg="Running kube-controller-manager --allocate-node-cidrs=true --bind-address=<IP_ADDRESS> --cluster-cidr=<IP_ADDRESS>/16 --cluster-signing-cert-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --cluster-signing-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --kubeconfig=/var/lib/rancher/k3s/server/cred/controller.kubeconfig --leader-elect=false --port=10252 --root-ca-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --secure-port=0 --service-account-private-key-file=/var/lib/rancher/k3s/server/tls/service.key --use-service-account-credentials=true"
I1113 13:58:09.335769       1 secure_serving.go:116] Serving securely on <IP_ADDRESS>:6444
I1113 13:58:09.335859       1 apiservice_controller.go:94] Starting APIServiceRegistrationController
I1113 13:58:09.335902       1 cache.go:32] Waiting for caches to sync for APIServiceRegistrationController controller
I1113 13:58:09.336070       1 crd_finalizer.go:242] Starting CRDFinalizer
I1113 13:58:09.337212       1 available_controller.go:320] Starting AvailableConditionController
I1113 13:58:09.337427       1 cache.go:32] Waiting for caches to sync for AvailableConditionController controller
I1113 13:58:09.337693       1 autoregister_controller.go:139] Starting autoregister controller
I1113 13:58:09.337705       1 cache.go:32] Waiting for caches to sync for autoregister controller
I1113 13:58:09.337708       1 customresource_discovery_controller.go:203] Starting DiscoveryController
I1113 13:58:09.337749       1 naming_controller.go:284] Starting NamingConditionController
I1113 13:58:09.337783       1 establishing_controller.go:73] Starting EstablishingController
I1113 13:58:09.346816       1 crdregistration_controller.go:112] Starting crd-autoregister controller
I1113 13:58:09.346963       1 controller_utils.go:1027] Waiting for caches to sync for crd-autoregister controller
I1113 13:58:09.362646       1 server.go:142] Version: v1.14.6-k3s.1
I1113 13:58:09.363056       1 defaults.go:87] TaintNodesByCondition is enabled, PodToleratesNodeTaints predicate is mandatory
I1113 13:58:09.368688       1 controllermanager.go:143] Version: v1.14.6-k3s.1
I1113 13:58:09.369803       1 deprecated_insecure_serving.go:51] Serving insecurely on [::]:10252
W1113 13:58:09.375914       1 authorization.go:47] Authorization is disabled
W1113 13:58:09.376377       1 authentication.go:55] Authentication is disabled
I1113 13:58:09.376658       1 deprecated_insecure_serving.go:49] Serving healthz insecurely on [::]:10251
E1113 13:58:09.434525       1 controller.go:147] Unable to perform initial Kubernetes service initialization: Service "kubernetes" is invalid: spec.clusterIP: Invalid value: "<IP_ADDRESS>": cannot allocate resources of type serviceipallocations at this time
E1113 13:58:09.436192       1 controller.go:152] Unable to remove old endpoints from kubernetes service: StorageError: key not found, Code: 1, Key: /registry/masterleases/<IP_ADDRESS>, ResourceVersion: 0, AdditionalErrorMsg:
I1113 13:58:09.437666       1 cache.go:39] Caches are synced for AvailableConditionController controller
I1113 13:58:09.437975       1 cache.go:39] Caches are synced for autoregister controller
I1113 13:58:09.447493       1 controller_utils.go:1034] Caches are synced for crd-autoregister controller
I1113 13:58:09.447494       1 cache.go:39] Caches are synced for APIServiceRegistrationController controller
E1113 13:58:09.470014       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope
E1113 13:58:09.470123       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list resource "replicationcontrollers" in API group "" at the cluster scope
E1113 13:58:09.470311       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list resource "persistentvolumeclaims" in API group "" at the cluster scope
E1113 13:58:09.470523       1 reflector.go:126] k8s.io/kubernetes/cmd/kube-scheduler/app/server.go:223: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list resource "pods" in API group "" at the cluster scope
E1113 13:58:09.470937       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.ReplicaSet: replicasets.apps is forbidden: User "system:kube-scheduler" cannot list resource "replicasets" in API group "apps" at the cluster scope
E1113 13:58:09.471131       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list resource "persistentvolumes" in API group "" at the cluster scope
E1113 13:58:09.473595       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list resource "nodes" in API group "" at the cluster scope
E1113 13:58:09.473693       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list resource "statefulsets" in API group "apps" at the cluster scope
time="2019-11-13T13:58:09.473797990Z" level=info msg="Creating CRD listenerconfigs.k3s.cattle.io"
E1113 13:58:09.475805       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list resource "services" in API group "" at the cluster scope
E1113 13:58:09.480527       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.StorageClass: storageclasses.storage.k8s.io is forbidden: User "system:kube-scheduler" cannot list resource "storageclasses" in API group "storage.k8s.io" at the cluster scope
time="2019-11-13T13:58:09.487790046Z" level=info msg="Creating CRD addons.k3s.cattle.io"
time="2019-11-13T13:58:09.492697568Z" level=info msg="Creating CRD helmcharts.helm.cattle.io"
time="2019-11-13T13:58:09.504774176Z" level=info msg="Waiting for CRD listenerconfigs.k3s.cattle.io to become available"
E1113 13:58:09.512215       1 autoregister_controller.go:193] v1.k3s.cattle.io failed with : apiservices.apiregistration.k8s.io "v1.k3s.cattle.io" already exists
E1113 13:58:09.514556       1 autoregister_controller.go:193] v1.k3s.cattle.io failed with : apiservices.apiregistration.k8s.io "v1.k3s.cattle.io" already exists
time="2019-11-13T13:58:10.011424325Z" level=info msg="Done waiting for CRD listenerconfigs.k3s.cattle.io to become available"
time="2019-11-13T13:58:10.011466763Z" level=info msg="Waiting for CRD addons.k3s.cattle.io to become available"
I1113 13:58:10.347160       1 storage_scheduling.go:109] created PriorityClass system-node-critical with value<PHONE_NUMBER>
I1113 13:58:10.350399       1 storage_scheduling.go:109] created PriorityClass system-cluster-critical with value<PHONE_NUMBER>
I1113 13:58:10.350422       1 storage_scheduling.go:118] all system priority classes are created successfully or already exist.
I1113 13:58:10.356633       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/cluster-admin
I1113 13:58:10.359583       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:discovery
I1113 13:58:10.362467       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:basic-user
I1113 13:58:10.365196       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:public-info-viewer
I1113 13:58:10.367851       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/admin
I1113 13:58:10.370740       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/edit
I1113 13:58:10.373666       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/view
I1113 13:58:10.377642       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:aggregate-to-admin
I1113 13:58:10.382051       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:aggregate-to-edit
I1113 13:58:10.385701       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:aggregate-to-view
I1113 13:58:10.388648       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:heapster
I1113 13:58:10.392789       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:node
I1113 13:58:10.395829       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:node-problem-detector
I1113 13:58:10.398552       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:node-proxier
I1113 13:58:10.401169       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:kubelet-api-admin
I1113 13:58:10.403728       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:node-bootstrapper
I1113 13:58:10.406799       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:auth-delegator
I1113 13:58:10.410020       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:kube-aggregator
I1113 13:58:10.412736       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:kube-controller-manager
I1113 13:58:10.415604       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:kube-scheduler
I1113 13:58:10.418145       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:kube-dns
I1113 13:58:10.420858       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:persistent-volume-provisioner
I1113 13:58:10.423906       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:csi-external-attacher
I1113 13:58:10.427486       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:aws-cloud-provider
I1113 13:58:10.430301       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:certificates.k8s.io:certificatesigningrequests:nodeclient
I1113 13:58:10.432925       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:certificates.k8s.io:certificatesigningrequests:selfnodeclient
I1113 13:58:10.435365       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:volume-scheduler
I1113 13:58:10.438157       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:csi-external-provisioner
I1113 13:58:10.446547       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:attachdetach-controller
I1113 13:58:10.452400       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:clusterrole-aggregation-controller
I1113 13:58:10.458345       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:cronjob-controller
I1113 13:58:10.464105       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:daemon-set-controller
I1113 13:58:10.469471       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:deployment-controller
I1113 13:58:10.472971       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:disruption-controller
E1113 13:58:10.473707       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope
E1113 13:58:10.475813       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list resource "replicationcontrollers" in API group "" at the cluster scope
I1113 13:58:10.477168       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:endpoint-controller
I1113 13:58:10.479907       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:expand-controller
I1113 13:58:10.482540       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:generic-garbage-collector
E1113 13:58:10.483936       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list resource "persistentvolumeclaims" in API group "" at the cluster scope
I1113 13:58:10.485779       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:horizontal-pod-autoscaler
E1113 13:58:10.487501       1 reflector.go:126] k8s.io/kubernetes/cmd/kube-scheduler/app/server.go:223: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list resource "pods" in API group "" at the cluster scope
I1113 13:58:10.489024       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:job-controller
E1113 13:58:10.489074       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.ReplicaSet: replicasets.apps is forbidden: User "system:kube-scheduler" cannot list resource "replicasets" in API group "apps" at the cluster scope
I1113 13:58:10.492818       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:namespace-controller
E1113 13:58:10.494483       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list resource "persistentvolumes" in API group "" at the cluster scope
E1113 13:58:10.495819       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list resource "nodes" in API group "" at the cluster scope
I1113 13:58:10.496564       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:node-controller
E1113 13:58:10.497618       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list resource "statefulsets" in API group "apps" at the cluster scope
E1113 13:58:10.498918       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list resource "services" in API group "" at the cluster scope
I1113 13:58:10.499955       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:persistent-volume-binder
I1113 13:58:10.502470       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:pod-garbage-collector
I1113 13:58:10.505023       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:replicaset-controller
I1113 13:58:10.508484       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:replication-controller
I1113 13:58:10.512142       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:resourcequota-controller
time="2019-11-13T13:58:10.514065451Z" level=info msg="Done waiting for CRD addons.k3s.cattle.io to become available"
time="2019-11-13T13:58:10.514555948Z" level=info msg="Waiting for CRD helmcharts.helm.cattle.io to become available"
E1113 13:58:10.514453       1 reflector.go:126] k8s.io/client-go/informers/factory.go:130: Failed to list *v1.StorageClass: storageclasses.storage.k8s.io is forbidden: User "system:kube-scheduler" cannot list resource "storageclasses" in API group "storage.k8s.io" at the cluster scope
I1113 13:58:10.516051       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:route-controller
I1113 13:58:10.518516       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:service-account-controller
I1113 13:58:10.520996       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:service-controller
I1113 13:58:10.523903       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:statefulset-controller
I1113 13:58:10.562986       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:ttl-controller
I1113 13:58:10.604484       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:certificate-controller
I1113 13:58:10.644181       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:pvc-protection-controller
I1113 13:58:10.684497       1 storage_rbac.go:191] created clusterrole.rbac.authorization.k8s.io/system:controller:pv-protection-controller
I1113 13:58:10.725989       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/cluster-admin
I1113 13:58:10.764097       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:discovery
I1113 13:58:10.803611       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:basic-user
I1113 13:58:10.843511       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:public-info-viewer
I1113 13:58:10.885465       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:node-proxier
I1113 13:58:10.924590       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:kube-controller-manager
I1113 13:58:10.963153       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:kube-dns
I1113 13:58:11.003768       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:kube-scheduler
time="2019-11-13T13:58:11.018787717Z" level=info msg="Done waiting for CRD helmcharts.helm.cattle.io to become available"
time="2019-11-13T13:58:11.035675471Z" level=info msg="Writing static file: /var/lib/rancher/k3s/server/static/charts/traefik-1.76.1.tgz"
time="2019-11-13T13:58:11.036130433Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/coredns.yaml"
time="2019-11-13T13:58:11.036292928Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/rolebindings.yaml"
E1113 13:58:11.036577       1 prometheus.go:138] failed to register depth metric k3s.cattle.io/v1, Kind=Addon: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=Addon_depth", help: "(Deprecated) Current depth of workqueue: k3s.cattle.io/v1, Kind=Addon", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=Addon_depth" is not a valid metric name
E1113 13:58:11.036624       1 prometheus.go:150] failed to register adds metric k3s.cattle.io/v1, Kind=Addon: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=Addon_adds", help: "(Deprecated) Total number of adds handled by workqueue: k3s.cattle.io/v1, Kind=Addon", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=Addon_adds" is not a valid metric name
E1113 13:58:11.036694       1 prometheus.go:162] failed to register latency metric k3s.cattle.io/v1, Kind=Addon: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=Addon_queue_latency", help: "(Deprecated) How long an item stays in workqueuek3s.cattle.io/v1, Kind=Addon before being requested.", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=Addon_queue_latency" is not a valid metric name
E1113 13:58:11.036744       1 prometheus.go:174] failed to register work_duration metric k3s.cattle.io/v1, Kind=Addon: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=Addon_work_duration", help: "(Deprecated) How long processing an item from workqueuek3s.cattle.io/v1, Kind=Addon takes.", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=Addon_work_duration" is not a valid metric name
E1113 13:58:11.036785       1 prometheus.go:189] failed to register unfinished_work_seconds metric k3s.cattle.io/v1, Kind=Addon: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=Addon_unfinished_work_seconds", help: "(Deprecated) How many seconds of work k3s.cattle.io/v1, Kind=Addon has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=Addon_unfinished_work_seconds" is not a valid metric name
E1113 13:58:11.036818       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric k3s.cattle.io/v1, Kind=Addon: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=Addon_longest_running_processor_microseconds", help: "(Deprecated) How many microseconds has the longest running processor for k3s.cattle.io/v1, Kind=Addon been running.", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=Addon_longest_running_processor_microseconds" is not a valid metric name
E1113 13:58:11.036871       1 prometheus.go:214] failed to register retries metric k3s.cattle.io/v1, Kind=Addon: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=Addon_retries", help: "(Deprecated) Total number of retries handled by workqueue: k3s.cattle.io/v1, Kind=Addon", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=Addon_retries" is not a valid metric name
I1113 13:58:11.043384       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:aws-cloud-provider
time="2019-11-13T13:58:11.043623178Z" level=error msg="Update cert unable to convert string to cert: Unable to split cert into two parts"
time="2019-11-13T13:58:11.043726635Z" level=info msg="Listening on :6443"
I1113 13:58:11.050440       1 controller.go:606] quota admission added evaluator for: listenerconfigs.k3s.cattle.io
E1113 13:58:11.057242       1 prometheus.go:138] failed to register depth metric k3s.cattle.io/v1, Kind=ListenerConfig: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=ListenerConfig_depth", help: "(Deprecated) Current depth of workqueue: k3s.cattle.io/v1, Kind=ListenerConfig", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=ListenerConfig_depth" is not a valid metric name
E1113 13:58:11.057303       1 prometheus.go:150] failed to register adds metric k3s.cattle.io/v1, Kind=ListenerConfig: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=ListenerConfig_adds", help: "(Deprecated) Total number of adds handled by workqueue: k3s.cattle.io/v1, Kind=ListenerConfig", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=ListenerConfig_adds" is not a valid metric name
E1113 13:58:11.057869       1 prometheus.go:162] failed to register latency metric k3s.cattle.io/v1, Kind=ListenerConfig: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=ListenerConfig_queue_latency", help: "(Deprecated) How long an item stays in workqueuek3s.cattle.io/v1, Kind=ListenerConfig before being requested.", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=ListenerConfig_queue_latency" is not a valid metric name
E1113 13:58:11.058078       1 prometheus.go:174] failed to register work_duration metric k3s.cattle.io/v1, Kind=ListenerConfig: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=ListenerConfig_work_duration", help: "(Deprecated) How long processing an item from workqueuek3s.cattle.io/v1, Kind=ListenerConfig takes.", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=ListenerConfig_work_duration" is not a valid metric name
E1113 13:58:11.058564       1 prometheus.go:189] failed to register unfinished_work_seconds metric k3s.cattle.io/v1, Kind=ListenerConfig: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=ListenerConfig_unfinished_work_seconds", help: "(Deprecated) How many seconds of work k3s.cattle.io/v1, Kind=ListenerConfig has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=ListenerConfig_unfinished_work_seconds" is not a valid metric name
E1113 13:58:11.059057       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric k3s.cattle.io/v1, Kind=ListenerConfig: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=ListenerConfig_longest_running_processor_microseconds", help: "(Deprecated) How many microseconds has the longest running processor for k3s.cattle.io/v1, Kind=ListenerConfig been running.", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=ListenerConfig_longest_running_processor_microseconds" is not a valid metric name
E1113 13:58:11.059504       1 prometheus.go:214] failed to register retries metric k3s.cattle.io/v1, Kind=ListenerConfig: descriptor Desc{fqName: "k3s.cattle.io/v1, Kind=ListenerConfig_retries", help: "(Deprecated) Total number of retries handled by workqueue: k3s.cattle.io/v1, Kind=ListenerConfig", constLabels: {}, variableLabels: []} is invalid: "k3s.cattle.io/v1, Kind=ListenerConfig_retries" is not a valid metric name
I1113 13:58:11.080789       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:volume-scheduler
I1113 13:58:11.123777       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:node
I1113 13:58:11.164998       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:attachdetach-controller
I1113 13:58:11.204166       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:clusterrole-aggregation-controller
I1113 13:58:11.244476       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:cronjob-controller
I1113 13:58:11.283346       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:daemon-set-controller
I1113 13:58:11.324688       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:deployment-controller
I1113 13:58:11.362813       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:disruption-controller
I1113 13:58:11.405463       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:endpoint-controller
I1113 13:58:11.443265       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:expand-controller
I1113 13:58:11.481282       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:generic-garbage-collector
I1113 13:58:11.522742       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:horizontal-pod-autoscaler
time="2019-11-13T13:58:11.560725615Z" level=info msg="Starting k3s.cattle.io/v1, Kind=Addon controller"
I1113 13:58:11.565094       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:job-controller
I1113 13:58:11.576375       1 controller.go:606] quota admission added evaluator for: serviceaccounts
I1113 13:58:11.600777       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:namespace-controller
I1113 13:58:11.635810       1 controller.go:606] quota admission added evaluator for: deployments.extensions
I1113 13:58:11.648333       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:node-controller
time="2019-11-13T13:58:11.661532561Z" level=info msg="Node token is available at /var/lib/rancher/k3s/server/node-token"
time="2019-11-13T13:58:11.662182936Z" level=info msg="To join node to cluster: k3s agent -s https://<IP_ADDRESS>:6443 -t ${NODE_TOKEN}"
time="2019-11-13T13:58:11.663767486Z" level=info msg="Starting k3s.cattle.io/v1, Kind=ListenerConfig controller"
time="2019-11-13T13:58:11.664444525Z" level=error msg="Update cert unable to convert string to cert: Unable to split cert into two parts"
I1113 13:58:11.666887       1 leaderelection.go:217] attempting to acquire leader lease  kube-system/k3s...
I1113 13:58:11.681696       1 leaderelection.go:227] successfully acquired lease kube-system/k3s
E1113 13:58:11.685163       1 prometheus.go:138] failed to register depth metric /v1, Kind=Node: descriptor Desc{fqName: "/v1, Kind=Node_depth", help: "(Deprecated) Current depth of workqueue: /v1, Kind=Node", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Node_depth" is not a valid metric name
E1113 13:58:11.685224       1 prometheus.go:150] failed to register adds metric /v1, Kind=Node: descriptor Desc{fqName: "/v1, Kind=Node_adds", help: "(Deprecated) Total number of adds handled by workqueue: /v1, Kind=Node", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Node_adds" is not a valid metric name
E1113 13:58:11.685509       1 prometheus.go:162] failed to register latency metric /v1, Kind=Node: descriptor Desc{fqName: "/v1, Kind=Node_queue_latency", help: "(Deprecated) How long an item stays in workqueue/v1, Kind=Node before being requested.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Node_queue_latency" is not a valid metric name
E1113 13:58:11.686117       1 prometheus.go:174] failed to register work_duration metric /v1, Kind=Node: descriptor Desc{fqName: "/v1, Kind=Node_work_duration", help: "(Deprecated) How long processing an item from workqueue/v1, Kind=Node takes.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Node_work_duration" is not a valid metric name
E1113 13:58:11.686189       1 prometheus.go:189] failed to register unfinished_work_seconds metric /v1, Kind=Node: descriptor Desc{fqName: "/v1, Kind=Node_unfinished_work_seconds", help: "(Deprecated) How many seconds of work /v1, Kind=Node has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Node_unfinished_work_seconds" is not a valid metric name
E1113 13:58:11.686234       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric /v1, Kind=Node: descriptor Desc{fqName: "/v1, Kind=Node_longest_running_processor_microseconds", help: "(Deprecated) How many microseconds has the longest running processor for /v1, Kind=Node been running.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Node_longest_running_processor_microseconds" is not a valid metric name
E1113 13:58:11.686407       1 prometheus.go:214] failed to register retries metric /v1, Kind=Node: descriptor Desc{fqName: "/v1, Kind=Node_retries", help: "(Deprecated) Total number of retries handled by workqueue: /v1, Kind=Node", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Node_retries" is not a valid metric name
E1113 13:58:11.686946       1 prometheus.go:138] failed to register depth metric batch/v1, Kind=Job: descriptor Desc{fqName: "batch/v1, Kind=Job_depth", help: "(Deprecated) Current depth of workqueue: batch/v1, Kind=Job", constLabels: {}, variableLabels: []} is invalid: "batch/v1, Kind=Job_depth" is not a valid metric name
E1113 13:58:11.686988       1 prometheus.go:150] failed to register adds metric batch/v1, Kind=Job: descriptor Desc{fqName: "batch/v1, Kind=Job_adds", help: "(Deprecated) Total number of adds handled by workqueue: batch/v1, Kind=Job", constLabels: {}, variableLabels: []} is invalid: "batch/v1, Kind=Job_adds" is not a valid metric name
E1113 13:58:11.687514       1 prometheus.go:162] failed to register latency metric batch/v1, Kind=Job: descriptor Desc{fqName: "batch/v1, Kind=Job_queue_latency", help: "(Deprecated) How long an item stays in workqueuebatch/v1, Kind=Job before being requested.", constLabels: {}, variableLabels: []} is invalid: "batch/v1, Kind=Job_queue_latency" is not a valid metric name
E1113 13:58:11.687720       1 prometheus.go:174] failed to register work_duration metric batch/v1, Kind=Job: descriptor Desc{fqName: "batch/v1, Kind=Job_work_duration", help: "(Deprecated) How long processing an item from workqueuebatch/v1, Kind=Job takes.", constLabels: {}, variableLabels: []} is invalid: "batch/v1, Kind=Job_work_duration" is not a valid metric name
E1113 13:58:11.687787       1 prometheus.go:189] failed to register unfinished_work_seconds metric batch/v1, Kind=Job: descriptor Desc{fqName: "batch/v1, Kind=Job_unfinished_work_seconds", help: "(Deprecated) How many seconds of work batch/v1, Kind=Job has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.", constLabels: {}, variableLabels: []} is invalid: "batch/v1, Kind=Job_unfinished_work_seconds" is not a valid metric name
E1113 13:58:11.687966       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric batch/v1, Kind=Job: descriptor Desc{fqName: "batch/v1, Kind=Job_longest_running_processor_microseconds", help: "(Deprecated) How many microseconds has the longest running processor for batch/v1, Kind=Job been running.", constLabels: {}, variableLabels: []} is invalid: "batch/v1, Kind=Job_longest_running_processor_microseconds" is not a valid metric name
E1113 13:58:11.688050       1 prometheus.go:214] failed to register retries metric batch/v1, Kind=Job: descriptor Desc{fqName: "batch/v1, Kind=Job_retries", help: "(Deprecated) Total number of retries handled by workqueue: batch/v1, Kind=Job", constLabels: {}, variableLabels: []} is invalid: "batch/v1, Kind=Job_retries" is not a valid metric name
E1113 13:58:11.688371       1 prometheus.go:138] failed to register depth metric helm.cattle.io/v1, Kind=HelmChart: descriptor Desc{fqName: "helm.cattle.io/v1, Kind=HelmChart_depth", help: "(Deprecated) Current depth of workqueue: helm.cattle.io/v1, Kind=HelmChart", constLabels: {}, variableLabels: []} is invalid: "helm.cattle.io/v1, Kind=HelmChart_depth" is not a valid metric name
E1113 13:58:11.688439       1 prometheus.go:150] failed to register adds metric helm.cattle.io/v1, Kind=HelmChart: descriptor Desc{fqName: "helm.cattle.io/v1, Kind=HelmChart_adds", help: "(Deprecated) Total number of adds handled by workqueue: helm.cattle.io/v1, Kind=HelmChart", constLabels: {}, variableLabels: []} is invalid: "helm.cattle.io/v1, Kind=HelmChart_adds" is not a valid metric name
E1113 13:58:11.688666       1 prometheus.go:162] failed to register latency metric helm.cattle.io/v1, Kind=HelmChart: descriptor Desc{fqName: "helm.cattle.io/v1, Kind=HelmChart_queue_latency", help: "(Deprecated) How long an item stays in workqueuehelm.cattle.io/v1, Kind=HelmChart before being requested.", constLabels: {}, variableLabels: []} is invalid: "helm.cattle.io/v1, Kind=HelmChart_queue_latency" is not a valid metric name
E1113 13:58:11.688956       1 prometheus.go:174] failed to register work_duration metric helm.cattle.io/v1, Kind=HelmChart: descriptor Desc{fqName: "helm.cattle.io/v1, Kind=HelmChart_work_duration", help: "(Deprecated) How long processing an item from workqueuehelm.cattle.io/v1, Kind=HelmChart takes.", constLabels: {}, variableLabels: []} is invalid: "helm.cattle.io/v1, Kind=HelmChart_work_duration" is not a valid metric name
E1113 13:58:11.690166       1 prometheus.go:189] failed to register unfinished_work_seconds metric helm.cattle.io/v1, Kind=HelmChart: descriptor Desc{fqName: "helm.cattle.io/v1, Kind=HelmChart_unfinished_work_seconds", help: "(Deprecated) How many seconds of work helm.cattle.io/v1, Kind=HelmChart has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.", constLabels: {}, variableLabels: []} is invalid: "helm.cattle.io/v1, Kind=HelmChart_unfinished_work_seconds" is not a valid metric name
E1113 13:58:11.690255       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric helm.cattle.io/v1, Kind=HelmChart: descriptor Desc{fqName: "helm.cattle.io/v1, Kind=HelmChart_longest_running_processor_microseconds", help: "(Deprecated) How many microseconds has the longest running processor for helm.cattle.io/v1, Kind=HelmChart been running.", constLabels: {}, variableLabels: []} is invalid: "helm.cattle.io/v1, Kind=HelmChart_longest_running_processor_microseconds" is not a valid metric name
E1113 13:58:11.690372       1 prometheus.go:214] failed to register retries metric helm.cattle.io/v1, Kind=HelmChart: descriptor Desc{fqName: "helm.cattle.io/v1, Kind=HelmChart_retries", help: "(Deprecated) Total number of retries handled by workqueue: helm.cattle.io/v1, Kind=HelmChart", constLabels: {}, variableLabels: []} is invalid: "helm.cattle.io/v1, Kind=HelmChart_retries" is not a valid metric name
E1113 13:58:11.690802       1 prometheus.go:138] failed to register depth metric /v1, Kind=Service: descriptor Desc{fqName: "/v1, Kind=Service_depth", help: "(Deprecated) Current depth of workqueue: /v1, Kind=Service", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Service_depth" is not a valid metric name
E1113 13:58:11.691133       1 prometheus.go:150] failed to register adds metric /v1, Kind=Service: descriptor Desc{fqName: "/v1, Kind=Service_adds", help: "(Deprecated) Total number of adds handled by workqueue: /v1, Kind=Service", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Service_adds" is not a valid metric name
E1113 13:58:11.691233       1 prometheus.go:162] failed to register latency metric /v1, Kind=Service: descriptor Desc{fqName: "/v1, Kind=Service_queue_latency", help: "(Deprecated) How long an item stays in workqueue/v1, Kind=Service before being requested.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Service_queue_latency" is not a valid metric name
E1113 13:58:11.691292       1 prometheus.go:174] failed to register work_duration metric /v1, Kind=Service: descriptor Desc{fqName: "/v1, Kind=Service_work_duration", help: "(Deprecated) How long processing an item from workqueue/v1, Kind=Service takes.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Service_work_duration" is not a valid metric name
E1113 13:58:11.691332       1 prometheus.go:189] failed to register unfinished_work_seconds metric /v1, Kind=Service: descriptor Desc{fqName: "/v1, Kind=Service_unfinished_work_seconds", help: "(Deprecated) How many seconds of work /v1, Kind=Service has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Service_unfinished_work_seconds" is not a valid metric name
E1113 13:58:11.691379       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric /v1, Kind=Service: descriptor Desc{fqName: "/v1, Kind=Service_longest_running_processor_microseconds", help: "(Deprecated) How many microseconds has the longest running processor for /v1, Kind=Service been running.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Service_longest_running_processor_microseconds" is not a valid metric name
E1113 13:58:11.691450       1 prometheus.go:214] failed to register retries metric /v1, Kind=Service: descriptor Desc{fqName: "/v1, Kind=Service_retries", help: "(Deprecated) Total number of retries handled by workqueue: /v1, Kind=Service", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Service_retries" is not a valid metric name
E1113 13:58:11.691732       1 prometheus.go:138] failed to register depth metric /v1, Kind=Pod: descriptor Desc{fqName: "/v1, Kind=Pod_depth", help: "(Deprecated) Current depth of workqueue: /v1, Kind=Pod", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Pod_depth" is not a valid metric name
E1113 13:58:11.691815       1 prometheus.go:150] failed to register adds metric /v1, Kind=Pod: descriptor Desc{fqName: "/v1, Kind=Pod_adds", help: "(Deprecated) Total number of adds handled by workqueue: /v1, Kind=Pod", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Pod_adds" is not a valid metric name
E1113 13:58:11.691888       1 prometheus.go:162] failed to register latency metric /v1, Kind=Pod: descriptor Desc{fqName: "/v1, Kind=Pod_queue_latency", help: "(Deprecated) How long an item stays in workqueue/v1, Kind=Pod before being requested.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Pod_queue_latency" is not a valid metric name
E1113 13:58:11.692256       1 prometheus.go:174] failed to register work_duration metric /v1, Kind=Pod: descriptor Desc{fqName: "/v1, Kind=Pod_work_duration", help: "(Deprecated) How long processing an item from workqueue/v1, Kind=Pod takes.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Pod_work_duration" is not a valid metric name
E1113 13:58:11.692315       1 prometheus.go:189] failed to register unfinished_work_seconds metric /v1, Kind=Pod: descriptor Desc{fqName: "/v1, Kind=Pod_unfinished_work_seconds", help: "(Deprecated) How many seconds of work /v1, Kind=Pod has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Pod_unfinished_work_seconds" is not a valid metric name
E1113 13:58:11.692378       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric /v1, Kind=Pod: descriptor Desc{fqName: "/v1, Kind=Pod_longest_running_processor_microseconds", help: "(Deprecated) How many microseconds has the longest running processor for /v1, Kind=Pod been running.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Pod_longest_running_processor_microseconds" is not a valid metric name
E1113 13:58:11.692470       1 prometheus.go:214] failed to register retries metric /v1, Kind=Pod: descriptor Desc{fqName: "/v1, Kind=Pod_retries", help: "(Deprecated) Total number of retries handled by workqueue: /v1, Kind=Pod", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Pod_retries" is not a valid metric name
E1113 13:58:11.692793       1 prometheus.go:138] failed to register depth metric /v1, Kind=Endpoints: descriptor Desc{fqName: "/v1, Kind=Endpoints_depth", help: "(Deprecated) Current depth of workqueue: /v1, Kind=Endpoints", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Endpoints_depth" is not a valid metric name
E1113 13:58:11.692840       1 prometheus.go:150] failed to register adds metric /v1, Kind=Endpoints: descriptor Desc{fqName: "/v1, Kind=Endpoints_adds", help: "(Deprecated) Total number of adds handled by workqueue: /v1, Kind=Endpoints", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Endpoints_adds" is not a valid metric name
E1113 13:58:11.692915       1 prometheus.go:162] failed to register latency metric /v1, Kind=Endpoints: descriptor Desc{fqName: "/v1, Kind=Endpoints_queue_latency", help: "(Deprecated) How long an item stays in workqueue/v1, Kind=Endpoints before being requested.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Endpoints_queue_latency" is not a valid metric name
E1113 13:58:11.693015       1 prometheus.go:174] failed to register work_duration metric /v1, Kind=Endpoints: descriptor Desc{fqName: "/v1, Kind=Endpoints_work_duration", help: "(Deprecated) How long processing an item from workqueue/v1, Kind=Endpoints takes.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Endpoints_work_duration" is not a valid metric name
E1113 13:58:11.693119       1 prometheus.go:189] failed to register unfinished_work_seconds metric /v1, Kind=Endpoints: descriptor Desc{fqName: "/v1, Kind=Endpoints_unfinished_work_seconds", help: "(Deprecated) How many seconds of work /v1, Kind=Endpoints has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Endpoints_unfinished_work_seconds" is not a valid metric name
E1113 13:58:11.693171       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric /v1, Kind=Endpoints: descriptor Desc{fqName: "/v1, Kind=Endpoints_longest_running_processor_microseconds", help: "(Deprecated) How many microseconds has the longest running processor for /v1, Kind=Endpoints been running.", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Endpoints_longest_running_processor_microseconds" is not a valid metric name
E1113 13:58:11.693403       1 prometheus.go:214] failed to register retries metric /v1, Kind=Endpoints: descriptor Desc{fqName: "/v1, Kind=Endpoints_retries", help: "(Deprecated) Total number of retries handled by workqueue: /v1, Kind=Endpoints", constLabels: {}, variableLabels: []} is invalid: "/v1, Kind=Endpoints_retries" is not a valid metric name
I1113 13:58:11.694351       1 controller.go:606] quota admission added evaluator for: addons.k3s.cattle.io
I1113 13:58:11.702864       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:persistent-volume-binder
I1113 13:58:11.728584       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:pod-garbage-collector
I1113 13:58:11.764111       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:replicaset-controller
I1113 13:58:11.802825       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:replication-controller
I1113 13:58:11.844563       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:resourcequota-controller
I1113 13:58:11.883887       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:route-controller
time="2019-11-13T13:58:11.917193433Z" level=info msg="Wrote kubeconfig /output/kubeconfig.yaml"
time="2019-11-13T13:58:11.917242516Z" level=info msg="Run: k3s kubectl"
time="2019-11-13T13:58:11.917268181Z" level=info msg="k3s is up and running"
I1113 13:58:11.920909       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:service-account-controller
I1113 13:58:11.964406       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:service-controller
I1113 13:58:12.005056       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:statefulset-controller
I1113 13:58:12.043881       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:ttl-controller
I1113 13:58:12.083238       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:certificate-controller
I1113 13:58:12.126041       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:pvc-protection-controller
I1113 13:58:12.162644       1 storage_rbac.go:219] created clusterrolebinding.rbac.authorization.k8s.io/system:controller:pv-protection-controller
I1113 13:58:12.200475       1 controller.go:606] quota admission added evaluator for: roles.rbac.authorization.k8s.io
I1113 13:58:12.209204       1 storage_rbac.go:250] created role.rbac.authorization.k8s.io/extension-apiserver-authentication-reader in kube-system
I1113 13:58:12.242908       1 storage_rbac.go:250] created role.rbac.authorization.k8s.io/system:controller:bootstrap-signer in kube-system
I1113 13:58:12.281786       1 storage_rbac.go:250] created role.rbac.authorization.k8s.io/system:controller:cloud-provider in kube-system
I1113 13:58:12.324142       1 storage_rbac.go:250] created role.rbac.authorization.k8s.io/system:controller:token-cleaner in kube-system
I1113 13:58:12.364269       1 storage_rbac.go:250] created role.rbac.authorization.k8s.io/system::leader-locking-kube-controller-manager in kube-system
I1113 13:58:12.404064       1 storage_rbac.go:250] created role.rbac.authorization.k8s.io/system::leader-locking-kube-scheduler in kube-system
I1113 13:58:12.408701       1 controller_utils.go:1027] Waiting for caches to sync for scheduler controller
I1113 13:58:12.449829       1 storage_rbac.go:250] created role.rbac.authorization.k8s.io/system:controller:bootstrap-signer in kube-public
I1113 13:58:12.480240       1 controller.go:606] quota admission added evaluator for: rolebindings.rbac.authorization.k8s.io
I1113 13:58:12.487971       1 storage_rbac.go:280] created rolebinding.rbac.authorization.k8s.io/system::extension-apiserver-authentication-reader in kube-system
I1113 13:58:12.509290       1 controller_utils.go:1034] Caches are synced for scheduler controller
I1113 13:58:12.522022       1 storage_rbac.go:280] created rolebinding.rbac.authorization.k8s.io/system::leader-locking-kube-controller-manager in kube-system
I1113 13:58:12.563005       1 storage_rbac.go:280] created rolebinding.rbac.authorization.k8s.io/system::leader-locking-kube-scheduler in kube-system
I1113 13:58:12.604489       1 storage_rbac.go:280] created rolebinding.rbac.authorization.k8s.io/system:controller:bootstrap-signer in kube-system
I1113 13:58:12.644172       1 storage_rbac.go:280] created rolebinding.rbac.authorization.k8s.io/system:controller:cloud-provider in kube-system
I1113 13:58:12.684558       1 storage_rbac.go:280] created rolebinding.rbac.authorization.k8s.io/system:controller:token-cleaner in kube-system
time="2019-11-13T13:58:12.698266973Z" level=info msg="Starting helm.cattle.io/v1, Kind=HelmChart controller"
I1113 13:58:12.722258       1 storage_rbac.go:280] created rolebinding.rbac.authorization.k8s.io/system:controller:bootstrap-signer in kube-public
time="2019-11-13T13:58:12.774708223Z" level=info msg="Logging containerd to /var/lib/rancher/k3s/agent/containerd/containerd.log"
time="2019-11-13T13:58:12.775186865Z" level=info msg="Running containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd"
time="2019-11-13T13:58:12.777463838Z" level=info msg="Waiting for containerd startup: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial unix /run/k3s/containerd/containerd.sock: connect: no such file or directory""
W1113 13:58:12.796574       1 lease.go:222] Resetting endpoints for master service "kubernetes" to [<IP_ADDRESS>]
I1113 13:58:12.797854       1 controller.go:606] quota admission added evaluator for: endpoints
time="2019-11-13T13:58:13.199453234Z" level=info msg="Starting batch/v1, Kind=Job controller"
I1113 13:58:13.694962       1 controller_utils.go:1027] Waiting for caches to sync for tokens controller
time="2019-11-13T13:58:13.780908680Z" level=info msg="module br_netfilter was already loaded"
time="2019-11-13T13:58:13.781360519Z" level=warning msg="failed to write value 1 at /proc/sys/net/bridge/bridge-nf-call-iptables: open /proc/sys/net/bridge/bridge-nf-call-iptables: read-only file system"
I1113 13:58:13.795352       1 controller_utils.go:1034] Caches are synced for tokens controller
I1113 13:58:13.819755       1 controllermanager.go:453] Started "ttl"
I1113 13:58:13.820533       1 ttl_controller.go:116] Starting TTL controller
I1113 13:58:13.820588       1 controller_utils.go:1027] Waiting for caches to sync for TTL controller
time="2019-11-13T13:58:13.835868792Z" level=info msg="Connecting to proxy" url="wss://<IP_ADDRESS>:6443/v1-k3s/connect"
time="2019-11-13T13:58:13.838046797Z" level=info msg="Handling backend connection request [dfd4e2c06458]"
time="2019-11-13T13:58:13.839973213Z" level=warning msg="Disabling CPU quotas due to missing cpu.cfs_period_us"
time="2019-11-13T13:58:13.842738947Z" level=info msg="Running kubelet --address=<IP_ADDRESS> --allow-privileged=true --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cert-dir=/var/lib/rancher/k3s/agent/kubelet/pki --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/k3s/agent/client-ca.crt --cluster-dns=<IP_ADDRESS> --cluster-domain=cluster.local --cni-bin-dir=/bin --cni-conf-dir=/var/lib/rancher/k3s/agent/etc/cni/net.d --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --cpu-cfs-quota=false --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=<IP_ADDRESS> --hostname-override=dfd4e2c06458 --kubeconfig=/var/lib/rancher/k3s/agent/kubelet.kubeconfig --kubelet-cgroups=/systemd --node-labels=node-role.kubernetes.io/master=true --read-only-port=0 --resolv-conf=/etc/resolv.conf --root-dir=/var/lib/rancher/k3s/agent/kubelet --runtime-cgroups=/systemd --seccomp-profile-root=/var/lib/rancher/k3s/agent/kubelet/seccomp --serialize-image-pulls=false --tls-cert-file=/var/lib/rancher/k3s/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/k3s/agent/serving-kubelet.key"
Flag --allow-privileged has been deprecated, will be removed in a future version
W1113 13:58:13.843248       1 server.go:216] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.
W1113 13:58:13.846092       1 options.go:265] unknown 'kubernetes.io' or 'k8s.io' labels specified with --node-labels: [node-role.kubernetes.io/master]
W1113 13:58:13.846131       1 options.go:266] in 1.16, --node-labels in the 'kubernetes.io' namespace must begin with an allowed prefix (kubelet.kubernetes.io, node.kubernetes.io) or be in the specifically allowed set (beta.kubernetes.io/arch, beta.kubernetes.io/instance-type, beta.kubernetes.io/os, failure-domain.beta.kubernetes.io/region, failure-domain.beta.kubernetes.io/zone, failure-domain.kubernetes.io/region, failure-domain.kubernetes.io/zone, kubernetes.io/arch, kubernetes.io/hostname, kubernetes.io/instance-type, kubernetes.io/os)
I1113 13:58:13.846819       1 server.go:399] Version: v1.14.6-k3s.1
W1113 13:58:13.847031       1 options.go:265] unknown 'kubernetes.io' or 'k8s.io' labels specified with --node-labels: [node-role.kubernetes.io/master]
W1113 13:58:13.847063       1 options.go:266] in 1.16, --node-labels in the 'kubernetes.io' namespace must begin with an allowed prefix (kubelet.kubernetes.io, node.kubernetes.io) or be in the specifically allowed set (beta.kubernetes.io/arch, beta.kubernetes.io/instance-type, beta.kubernetes.io/os, failure-domain.beta.kubernetes.io/region, failure-domain.beta.kubernetes.io/zone, failure-domain.kubernetes.io/region, failure-domain.kubernetes.io/zone, kubernetes.io/arch, kubernetes.io/hostname, kubernetes.io/instance-type, kubernetes.io/os)
time="2019-11-13T13:58:13.854437518Z" level=info msg="waiting for node dfd4e2c06458: nodes "dfd4e2c06458" not found"
W1113 13:58:13.858841       1 fs.go:218] stat failed on /dev/sda4 with error: no such file or directory
W1113 13:58:13.865797       1 proxier.go:485] Failed to read file /lib/modules/5.3.10-arch1-1/modules.builtin with error open /lib/modules/5.3.10-arch1-1/modules.builtin: no such file or directory. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1113 13:58:13.874725       1 proxier.go:498] Failed to load kernel module ip_vs with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1113 13:58:13.876350       1 info.go:52] Couldn't collect info from any of the files in "/etc/machine-id,/var/lib/dbus/machine-id"
I1113 13:58:13.877148       1 server.go:595] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
I1113 13:58:13.877748       1 controllermanager.go:453] Started "persistentvolume-expander"
I1113 13:58:13.877870       1 container_manager_linux.go:261] container manager verified user specified cgroup-root exists: []
I1113 13:58:13.877893       1 container_manager_linux.go:266] Creating Container Manager object based on Node Config: {RuntimeCgroupsName:/systemd SystemCgroupsName: KubeletCgroupsName:/systemd ContainerRuntime:remote CgroupsPerQOS:true CgroupRoot:/ CgroupDriver:cgroupfs KubeletRootDir:/var/lib/rancher/k3s/agent/kubelet ProtectKernelDefaults:false NodeAllocatableConfig:{KubeReservedCgroupName: SystemReservedCgroupName: EnforceNodeAllocatable:map[pods:{}] KubeReserved:map[] SystemReserved:map[] HardEvictionThresholds:[{Signal:imagefs.available Operator:LessThan Value:{Quantity: Percentage:0.05} GracePeriod:0s MinReclaim:} {Signal:nodefs.available Operator:LessThan Value:{Quantity: Percentage:0.05} GracePeriod:0s MinReclaim:}]} QOSReserved:map[] ExperimentalCPUManagerPolicy:none ExperimentalCPUManagerReconcilePeriod:10s ExperimentalPodPidsLimit:-1 EnforceCPULimits:false CPUCFSQuotaPeriod:100ms}
I1113 13:58:13.878057       1 container_manager_linux.go:286] Creating device plugin manager: true
I1113 13:58:13.878171       1 state_mem.go:36] [cpumanager] initializing new in-memory state store
I1113 13:58:13.879252       1 expand_controller.go:147] Starting expand controller
I1113 13:58:13.879500       1 controller_utils.go:1027] Waiting for caches to sync for expand controller
W1113 13:58:13.879482       1 proxier.go:498] Failed to load kernel module ip_vs_rr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1113 13:58:13.880999       1 proxier.go:498] Failed to load kernel module ip_vs_wrr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1113 13:58:13.883558       1 proxier.go:498] Failed to load kernel module ip_vs_sh with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1113 13:58:13.884590       1 proxier.go:498] Failed to load kernel module nf_conntrack with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
time="2019-11-13T13:58:13.900979485Z" level=info msg="Starting /v1, Kind=Node controller"
W1113 13:58:13.947496       1 node.go:113] Failed to retrieve node info: nodes "dfd4e2c06458" not found
I1113 13:58:13.947565       1 server_others.go:147] Using iptables Proxier.
F1113 13:58:13.948672       1 server.go:475] unable to create proxier: can't set sysctl net/ipv4/conf/all/route_localnet: open /proc/sys/net/ipv4/conf/all/route_localnet: read-only file system
time="2019-11-13T13:58:14.036866294Z" level=info msg="Starting /v1, Kind=Service controller"

You can close the issue, if you find it out of scope. Just wanted to share a thought


TTS actions fail sometimes with Snapcast because of KeyError

What version of Music Assistant has the issue?
2.3.0b27
What version of the Home Assistant Integration have you got installed?
2024.9.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
WHen using TTS services like tts.speak or tts.cloud_say this sometimes works, and sometimes fails with a KeyError message in the log.
In some cases a small part of the announcement chime can be heard, sometimes not at all.
How to reproduce
Using external snapcast server:
From developer actions perform the following action:
      - action: tts.cloud_say
        data:
          message: "Test bericht"
          language: nl-NL
          entity_id: "media_player.pi_kitchen"

Music Providers

tts.speak
tts.cloud_say

Player Providers
Using the non-bundled external snapcast server addon: https://github.com/Art-Ev/addon-snapserver.
Full log output
Relevant part of MA log:
2024-09-29 16:12:03.954 INFO (MainThread) [music_assistant.streams] Start Queue Flow stream for Queue pi-kitchen - crossfade: False
2024-09-29 16:12:04.197 INFO (MainThread) [music_assistant.streams] Finished Queue Flow stream for Queue pi-kitchen
2024-09-29 16:12:25.495 INFO (MainThread) [music_assistant.streams] Start Queue Flow stream for Queue pi-kitchen - crossfade: False
2024-09-29 16:12:33.448 INFO (MainThread) [music_assistant.players] Playback announcement to player pi-kitchen (with pre-announce: True): http://<IP_ADDRESS>:8123/api/tts_proxy/eff31259f48d074b591698ccd947d46d6883e7ee_nl-nl_6e8b81ac47_cloud.mp3

Additional information
This issue was not there in previous (not sure exactly what versions) versions of MA. I have used TTS successfully with exactly the same setup before, leading me te believe a change in the MA beta's caused this behavior somehow.
HA Log:
Logger: homeassistant
Source: components/snapcast/media_player.py:144
First occurred: 3:53:38 PM (26 occurrences)
Last logged: 4:12:39 PM

    Error doing job: Task exception was never retrieved (None)
    Error doing job: Fatal error: protocol.data_received() call failed. (None)
    Error doing job: Exception in callback Entity._async_write_ha_state_from_call_soon_threadsafe() (None)

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 960, in async_update_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/snapcast/media_player.py", line 144, in state
    return STREAM_STATUS.get(self._group.stream_status)
                             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/snapcast/control/group.py", line 54, in stream_status
    return self._server.stream(self.stream).status
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/snapcast/control/server.py", line 272, in stream
    return self._streams[stream_identifier]
           ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
KeyError: 'MusicAssistant--5031'

What version of Home Assistant Core are your running
2024.9.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

@SantiagoSotoC

But you are using the home assistant snapcast integration for TTL ?

I am indeed using the default home assistant snapcast integration. The media_player that I'm using for my TTS action is the snapcast media_player entity that Music Assistant created:

Ok you can’t do that. If you want to use Music Assistant and its features then you only use MA. That means using the MA entities and MA service calls for announcments

The docs say that the TTS action is supported? See the bottom of this page:
https://music-assistant.io/faq/massannounce/?h=tts
Also, it has worked fine for me for many months..

Ok sorry there is confusion here. Santiago asked if you were using the “HA Snapcast Integration” and you said yes. Why did you say you are using that but then say you are using the MA entities?
I see you are using an external Snapcast Server. If you do have the HA integration installed then the question is why? Additionally, have you tried testing with the HA integration disabled?

It is not a problem to have snapcast integration in ha. But modifying streams by hand can be.
I was  asking because in one of the logs you post it looks like you are using the media player of the snapcast integration in home assistant.
I'm going to test if TTl works in the latest beta

I'm only using the MA generated entities for the TTS actions, not the entities from the snapcast integration.
I just did some more testing, and the same KeyError also happens when using the mass.play_announcement service, on some files only! WTF..
This one works every single time (even though the volume seems to be set to 15 rather than 5, maybe some caching going on?):
action: mass.play_announcement
target:
  entity_id: media_player.pi_kitchen
data:
  url: https://homeassistant.mydomain.com/local/sounds/merol.mp3
  use_pre_announce: true
  announce_volume: 5

And this one never works, even though the file is there:
action: mass.play_announcement
target:
  entity_id: media_player.pi_kitchen
data:
  url: https://homeassistant.mydomain.com/local/sounds/triple_airhorn.mp3
  use_pre_announce: true
  announce_volume: 5

With again the same error on the second file:
Logger: homeassistant
Source: components/snapcast/media_player.py:272
First occurred: 12:38:06 PM (43 occurrences)
Last logged: 10:47:44 PM
Error doing job: Task exception was never retrieved (None)

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 960, in async_update_ha_state
  self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
  self.__async_calculate_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
  state = self._stringify_state(available)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
  if (state := self.state) is None:
               ^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/snapcast/media_player.py", line 272, in state
  return STREAM_STATUS.get(self._client.group.stream_status)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/snapcast/control/group.py", line 54, in stream_status
  return self._server.stream(self.stream).status
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/snapcast/control/server.py", line 272, in stream
  return self._streams[stream_identifier]
         ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
KeyError: 'MusicAssistant--5087'

Sorry I can't recreate this. If it isn't too big can you share the airhorn file or supply the URL where it came from so I can try that. I have tried text messages and audio files via URL to single and grouped Snacast players and that worked fine.

This line in the home assistant log looks very strange to me:
Source: components/snapcast/media_player.py

You are right. That is a HA error not MA. @freakshock88 Are you sure media_player.pi_kitchen is the MA entity?

Yes I'm pretty sure ;)
See image:

Did some more testing.
I disabled the snapcast integration entirely.
This makes the error not show up in the HA log, so you guys are right that error seems to come from the snapcast integration, even though the trigger is a TTS action sent to the mediaplayer of the MA interation.
However the main problem, that the TTS messages only work sometimes is still there.
There is now now no error at all in the HA log or in the MA log unfortunately.
I do see the volume increase in the MA UI everytime I initiate the TTS action, but theres no sound.
Perhaps that is a problem in my snapcast client?

Most likely it has to do with this, https://github.com/music-assistant/hass-music-assistant/issues/2690#issuecomment-2387013659.

Keeping open to see if the fix for 2690 fixes this as well.

@freakshock88 Has this been fixed in beta 33?

I think my issue was actually the issue as outlined in #2690, as in short TTS messages still fail. But longer messages playback successfully consistently. I think you can close this issue, but I will keep following #2690 for a possible fix for short TTS/audio clips.

I think my issue was actually the issue as outlined in #2690, as in short TTS messages still fail. But longer messages playback successfully consistently. I will close this issue, but I will keep following #2690 for a possible fix for short TTS/audio clips.

In a next beta may have a temporary solution for that, it is a patch I hope it is only for a few betas.


Write contribution guide and list coding conventions

We need a guideline for developers from outside the core development team for how to contribute:

how to do the PR
list of coding conventions, e.g., docstring style, black code formatting, lfs etc.
...

See https://github.com/orgs/mackelab/teams/lfi.
Also - package __author__, file copyright statements, license.


Add ability to change colours in user preference

Let's add fields where users can change colours in settings
Plus pls revert to previous colours 😄

alpha value for primary color is really bad :/
i've changed light text (silver color) for something more "clean" (#f8f4f6), it was used on .active class

so you mean user can change these 3 variables from settings?

Closing for #3134


Proxy for HTTP/3?

Question
tusd documentation states:

HTTP/3 and QUIC is currently not supported without the use of an external proxy.

Is that the same as a reverse proxy mentioned further down?
Has there been any experience using LiteSpeed as a proxy for tusd, or would Nginx be a better choice?  Is the example Nginx configuration (tusd/examples/nginx.conf) suitable for Nginx configurations with HTTP/3?
Would you be able to suggest and describe in high level terms what the complete solution would look like if it were restricted to only HTTP/3 uploads (for network congestion relief reasons)?

Is that the same as a reverse proxy mentioned further down?

Yes, that's what is meant.

Has there been any experience using LiteSpeed as a proxy for tusd, or would Nginx be a better choice?

I haven't experimented with H3 at all, so I'm afraid I can not help you much with those questions. But in general, the reverse proxy should accept the H3 requests and forward them as HTTP/1.1 or H2 to tusd. As said, I didn't try this yet, but I doubt the configuration would be complicated in the proxy.

Closing this issue due to inactivity. Feel free to leave a comment if you want to continue the discussion :)


Springboot and maven dependencies error

I have a sample spring boot app to deploy in my system which is throwing me following error.I tried cleaning up the maven files from cache still struck with the issue. Can anyone help me with this. Following is the error I Get
(Project build error: Non-resolvable parent POM for com.broad.gateway:com-
gateway:0.0.1-SNAPSHOT: Could not transfer artifact
org.springframework.boot:spring-boot-starter-parent:pom:2.0.2.RELEASE from/to
central (https://repo.maven.apache.org/maven2): connect timed out and
'parent.relativePath' points at no local POM)

No, as I said I am trying to run my sample app in my local but facing Maven POM error

I apologize, "a sample spring boot app" is a bit confusing. I see now that you are trying to set up Hygieia locally.
Are you running mvn clean install form the Hygieia root directory?

I am sorry , could you tell me what do you mean by 'hygieia'?
I downloaded a sample app from  (https://projects.spring.io/spring- boot/): which installed my dependencies required to run my springboot application. Now when I am trying to run that it is throwing following error
Project build error: Non-resolvable parent POM for com.broad.gateway:com-gateway:0.0.1-SNAPSHOT: Failure to transfer org.springframework.boot:spring-boot-starter-parent:pom:2.0.2.RELEASE from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.0.2.RELEASE from/to central (https://repo.maven.apache.org/maven2): connect timed out and 'parent.relativePath' points at no local POM

@AnanyaSreepathi  Closing this because your issue is not related to Hygieia.


Documentation - Hook configuration

In the documentation, the suggested code to be added to the hooks file is invalid.
Currently it is:
export handle = auth.authHandle
export getSession = auth.getAuthSession
however I believe it should be
import { auth } from '$lib/lucia';
export const handle = auth.handleAuth;
export const getSession = auth.getAuthSession;
You are missing the const for the variables, and also the auth handler is handleAuth rather than authHandle.

That is how it is explained here: https://www.youtube.com/watch?v=Y98KipzwVdM

Thanks for bringing up the issue! Fixed with #14


is it possible to do VoD streaming ?

Hi,
I want to do HLS streaming with recorded and existing videos from server to browser using HLS protocol.
Is this possible to stream existing videos from server folder to client browser using HLS video .. ??
If so, please let me know the configuration to do VoD streaming.
Thanks In Advance,
Sam

No
Maybe you can try nginx-vod-module

Quick question is why cant we serve the files in mp4 forma which is there as a recording.Any restrictions using js on this?


How do I configure my debugger adapter?

There are these "preconfigured" adapters that I can install. I would instead like to configure my own adapter. In my case, I have lldb-vscode-12 installed via the apt repository at apt.llvm.org.

It's not really setup to easily allow that right now but you can create a simple plugin with something like the following (if the transport is over stdio). You also need a .python-version file with 3.8 so its gets run in the correct plugin-host.
from Debugger.modules.debugger import adapter

class LLDBVSCode(adapter.AdapterConfiguration):
	@property
	def type(self):
		return "lldb-vscode"

	async def start(self, log, configuration):
		command = ['lldb-vscode']
		return adapter.StdioTransport(log, command)

	@property
	def installed_version(self):
		return '0.0'

https://github.com/daveleroy/sublime_debugger/tree/master/modules/debugger/adapters has some more advanced configurations.
Just a warning the interface is likely to change in the near future.

The plugin picks up my adapter class, but after playing with it for a while I can only get this in the debugger console:
error: ld-2.27.so 0x7fffffff0005c587: adding range [0x1469a-0x1470a) which has a base that is less than the function's low P
C 0x14e10. Please file a bug and attach the file at the start of this error message

this is printed three more times with different memory addresses.
configuration in my .sublime-project:
	"debugger_configurations" : [
		{
			"name" : "launch tests",
			"request" : "launch",
			"type" : "lldb-12",
			"program": "${folder}/test",
		}
	]

I have placed the adapter class in Packages/User/lldb.py
from Debugger.modules.debugger import adapter

class Lldb12(adapter.AdapterConfiguration):
	@property
	def type(self):
		return "lldb-12"

	async def start(self, log, configuration):
		return adapter.StdioTransport(log, ["lldb-vscode-12"])

	@property
	def installed_version(self):
		return '0.0'

Note that this executable does exist:
raoul@raoul-Latitude-5500 ~ [127]> lldb-vscode-12 --help
OVERVIEW: LLDB VSCode

USAGE: lldb-vscode-12 options

OPTIONS:
  -g                  Alias for --wait-for-debugger
  --help              Prints out the usage information for the LLDB VSCode tool.
  -h                  Alias for --help
  --port <port>       Communicate with the lldb-vscode tool over the defined port.
  -p <value>          Alias for --port
  --wait-for-debugger Pause the program at startup.

EXAMPLES:
  The debug adapter can be started in two modes.

  Running lldb-vscode without any arguments will start communicating with the
  parent over stdio. Passing a port number causes lldb-vscode to start listening
  for connections on that port.

    lldb-vscode -p <port>

  Passing --wait-for-debugger will pause the process at startup and wait for a
  debugger to attach to the process.

    lldb-vscode -g

Ah, I can also reproduce that ld error when running the file with lldb in the terminal, so we're getting somewhere :)

I think the only thing I suggest is make sure you are using the -g flag and check that any debug information that is generated is actually new.
You might want to try with llvm 11 (stable) unless there is a reason use the dev branch of llvm.

I got it to work in the end. Turns out it runs the target process just fine.
This is definitely a cool package, but I have some thoughts about UX improvements. If you like, I can open a new issue for it.

Awesome!
Yeah go ahead and open an issue for them.


tympanic membrane terms

Add:
tympanic membrane retraction (child of abnormal tympanic membrane morphology MP:0006018)
DEF: a condition in which a segment of the tympanic membrane (eardrum) collapses inwards towards the middle ear space and lies more medially (deeper) than its normal position; the retracted segment is often known as a retraction pocket
SYN: eardrum retraction
SYN: retracted eardrum
SYN: retracted tympanic membrane
https://en.wikipedia.org/wiki/Tympanic_membrane_retraction
http://allearseducation.org/resources/Tutorial-10-Retractions.pdf
J:131873 J:85263
tympanic membrane perforation
DEF: a hole or tear in the tympanic membrane (eardrum)
SYN: eardrum perforation
SYN: perforated eardrum
SYN: perforated tympanic membrane
SYN: ruptured eardrum
SYN: tympanic membrane rupture
https://www.emedicinehealth.com/perforated_eardrum/article_em.htm
J:113445

tympanic membrane retraction MP:0030413
tympanic membrane perforation MP:0030414


[BUG] When taking a synchronous exception, bit 6 (sync_exc_seen) should be set in the CPUCTRL CSR (0x7C0)

Bug Description
With the updated reference model, running debug_test with USE_ISS=YES, the reference model sets bit 6 sync_exc_seen in the cpuctrl (0x7c0) register.
This CSR is not implemented in the RTL, but it is in the CVE2 spec.

@christian-herber-nxp , do we want this RTL register? is it only for simulation? if so we can do "ifndef SYNTHESIS", or do we want to remove it from the ISS?


Request: Flink connector enhancements

What needs to be done?

Upgrade Flink version
The version of Flink in the pinot project pom should be updated from 1.14.6 to the latest version of Flink, 1.18.1.

Authentication
The org.apache.pinot.controller.helix.ControllerRequestClient does not currently accept an org.apache.pinot.spi.auth.AuthProvider.
Similarly, the org.apache.pinot.connector.flink.sink.PinotSinkFunction<T> does not accept an AuthProvider.

Error handling
Verify that the underlying SegmentWriter handles errors appending records to a segment and that errors propagate correctly to the Flink runtime.  Check that the SegmentUploader handles transmission errors and propagates these correctly.

Schema and Data Type Mapping
Correctly convert types from Flink timestamps with timezones to the Pinot equivalent.  See this comment.
Double / decimal conversions - see this comment.

Nice to haves:

Segment size parameter
Currently segmentFlushMaxNumRecords controls when the segment is flushed according to the number of ingested rows.  A dual to this could be desiredSegmentSize that could be used to flush segments when the number of bytes approaches or exceeds a size threshold.

Checkpoint support
Understanding the limitations behind only supporting Batch mode execution in Flink.  Can the current segment writer be serialized and is there support for resuming from the serialized state?

Connector assembly
Packaging the connector as a single assembly with shaded dependencies so that it can be used within the FlinkSQL environment.  This is done in other connectors such as Delta Lake, Google BigQuery etc.

Other questions:

Is it possible to upload directly to a deep store and push metadata to the controller, or do we need the controller to implement the two-phase commit protocol?

Why the feature is needed
Our particular use case involves using pre-aggregation before ingestion into Pinot using Apache Datasketches.  These are serialized as binary and can be in the order of megabytes.  These are appended to a Delta Lake.  The idea is to stream records continuously from the Delta Lake using the Flink Delta Connector and have fine grained control over Pinot Segment generation.  These segments are to be uploaded directly to Pinot.   Our Pinot controllers are secured using Basic Authentication.
It is possible to clone and modify the existing connector and make modifications but some of these enhancements might benefit other users and discussing here is better.
Initial idea/proposal
Discuss the points above and collaborate on implementation.

@davecromberge Does FlinkDeltaConnector emit CDC (change data capture) stream? How does it going to handle records update or delete? In other words, what would be the strategy to sync data between delta lake and pinot using Flink Delta Connector?

@snleee we do not plan to support CDC directly through this interface.  This issue is more about using Flink to build segments and upload them directly to the controller with the intention of giving the user more control over the ingestion process.
Whilst a delta lake might support the operations you mention, we only currently support INSERT/append through our connector.  In some sense, we are tackling this problem in increments - eventually we will have to consider the delta lake semantics and synchronise the state between Pinot and the Delta lake by one of the two methods you describe.  However, this is out of scope for the issue here which is narrowed to Flink and Pinot.  It is entirely possible that this could fall away if there was enough segment / input file lineage to make the sync a reality - which could even be done via a spark job which optimises the delta lake and applies mutation.  For our use case having the building blocks in place allows us to replay the INSERT operations from the delta lake from a given checkpoint / version into Pinot should we need to rebuild a table from scratch.

this PR bumps the Flink version to 1.19.0
https://github.com/apache/pinot/pull/12659

There are two more enhancements that can be considered:

[Modernization] Flink Unified connector API refactoring for Pinot sink(ref)
[Optimization] Upload segments via URI(via HDFS uri).


feat: module tests and lint

Description
I added:

A test that checks if the module works when the developer wants the module to create the bucket and provides a name
A test that checks if the module works when the developer provides an existing s3 bucket
A .yml workflow to check the format of the terraform files

note that dummy.txt is not deleted yet

note that dummy.txt is not deleted yet

strange, to me appears it is going to be deleted


Balaji<EMAIL_ADDRESS>Hexagonal Architecture Implementation

Checked in only the required java files
Removed unrelated Files from the Project
Formatted the code using Eclipse formatter

Closing the Pull request for further review


I'd like to add a backword time feature

I want to contribute and make a feature where you can open a timer that shows how much time is left before the day ends, it could be used as a occasion (new year or something like that) timer that shows how much time is left before another day begins.
@param-code let me know what you think

Sure.

I want to contribute and make a feature where you can open a timer that shows how much time is left before the day ends, it could be used as a occasion (new year or something like that) timer that shows how much time is left before another day begins.
@param-code let me know what you think

All the Best!!

it may take some time now, the whole code has been changed with the new theme


Subscribing to events with particular property value from Actors

Is it possible to subscribe from Actors to the events with particular property value?
The example:
PersonActor should susbcribe to events that have PersonId of this PersonActor and I don't want other PersonActor instances with different PersonId values to receive this message. Or maybe it's a bad practice and PersonActor should have method instead of receiving message?

Hi, this is not possible in the current code. But I do take pull requests. Do you mean something like a Subscription filter in Azure Service Bus Subscriptions?
Let's see if there's a library that provides this functionality for .net objects.

@loekd - yep that's the kind of thing we were thinking too. @pavelbaykov89 and I are evaluating the library as a starting position for a project and we would be happy to contribute if we go with it.

That would be great!

I think this request have to be carefully weighed to make sure it is in the scope of this solution. The solution space is messaging infrastructure. The decimation of events by pub-sub should be agnostic of any domain knowledge unless it is based on a primitive predicate. That will make it domain agnostic.
Filtering assumes knowledge. Knowledge should be encapsulated in the Domain Model. Messaging infrastructure by definition is not Domain.
These are just thoughts...

agreed, the subscriber would need to specify the properties to filter on in a generalized manner.


Error downloading account name

Hi trying to log on and it keeps saying error in account name
Debug log
03-04-2017 5:56]
Error: attempted to get items for the non existant league ''
Current leagues are:
Exception details :
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Procurement.ViewModel.StashViewModel.getAvailableItems()
[03-04-2017 5:56] Application Version: Procurement 1.11.0
[03-04-2017 5:56]
CurrentCulture: en-US
CurrentUICulture: en-US
Operating System: Microsoft Windows NT 6.2.9200.0
Current League:
[03-04-2017 5:56] System.NullReferenceException: Object reference not set to an instance of an object.
at Procurement.ViewModel.InventoryViewModel..ctor(InventoryView inventoryView)
at Procurement.View.InventoryView..ctor()
at Procurement.ViewModel.ScreenController.<>c.b__33_0()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
[03-04-2017 15:04] POEApi.Infrastructure.LogonFailedException: Incorrect session id
at POEApi.Transport.HttpTransport.Authenticate(String email, SecureString password, Boolean useSessionID)
at POEApi.Model.POEModel.Authenticate(String email, SecureString password, Boolean offline, Boolean useSessionID)
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.b__0()
at System.Threading.Tasks.Task.Execute()
[03-04-2017 15:06] POEApi.Infrastructure.LogonFailedException: Incorrect session id
at POEApi.Transport.HttpTransport.Authenticate(String email, SecureString password, Boolean useSessionID)
at POEApi.Model.POEModel.Authenticate(String email, SecureString password, Boolean offline, Boolean useSessionID)
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.b__0()
at System.Threading.Tasks.Task.Execute()
[03-04-2017 15:06] POEApi.Infrastructure.LogonFailedException: Incorrect session id
at POEApi.Transport.HttpTransport.Authenticate(String email, SecureString password, Boolean useSessionID)
at POEApi.Model.POEModel.Authenticate(String email, SecureString password, Boolean offline, Boolean useSessionID)
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.b__0()
at System.Threading.Tasks.Task.Execute()
[03-04-2017 15:06] Error downloading account name, exception details: System.ApplicationException: Unable to deserialize object
at POEApi.Model.POEModel.GetProperObjectFromTransport[T](Stream networkData)
at POEApi.Model.POEModel.GetAccountName()
[03-04-2017 15:06] System.Exception: Error downloading account name, details logged to DebugInfo.log. Please open a ticket at https://github.com/Stickymaddness/Procurement/issues and include your DebugInfo.log
at POEApi.Model.POEModel.GetAccountName()
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.b__0()
at System.Threading.Tasks.Task.Execute()
[03-04-2017 15:07] Error downloading account name, exception details: System.ApplicationException: Unable to deserialize object
at POEApi.Model.POEModel.GetProperObjectFromTransport[T](Stream networkData)
at POEApi.Model.POEModel.GetAccountName()
[03-04-2017 15:07] System.Exception: Error downloading account name, details logged to DebugInfo.log. Please open a ticket at https://github.com/Stickymaddness/Procurement/issues and include your DebugInfo.log
at POEApi.Model.POEModel.GetAccountName()
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.b__0()
at System.Threading.Tasks.Task.Execute()
[03-04-2017 15:07] Error downloading account name, exception details: System.ApplicationException: Unable to deserialize object
at POEApi.Model.POEModel.GetProperObjectFromTransport[T](Stream networkData)
at POEApi.Model.POEModel.GetAccountName()
[03-04-2017 15:07] System.Exception: Error downloading account name, details logged to DebugInfo.log. Please open a ticket at https://github.com/Stickymaddness/Procurement/issues and include your DebugInfo.log
at POEApi.Model.POEModel.GetAccountName()
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.b__0()
at System.Threading.Tasks.Task.Execute()
[03-04-2017 15:09] Error downloading account name, exception details: System.ApplicationException: Unable to deserialize object
at POEApi.Model.POEModel.GetProperObjectFromTransport[T](Stream networkData)
at POEApi.Model.POEModel.GetAccountName()
[03-04-2017 15:09] System.Exception: Error downloading account name, details logged to DebugInfo.log. Please open a ticket at https://github.com/Stickymaddness/Procurement/issues and include your DebugInfo.log
at POEApi.Model.POEModel.GetAccountName()
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.b__0()
at System.Threading.Tasks.Task.Execute()

Resolved
Figured it out

If you wouldn't mind closing this issue - thanks,


⚠ SceneTime has degraded performance

In 19976c7, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1656 ms

Resolved: SceneTime performance has improved in 746c0e1 after 19 minutes.


Apply Add Uri Property

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.