https://www.umh.app logo
Join Discord
Powered by
Issue: DFC "ERROR:...unable to infer
# umh-support
t
Issue: DFC "ERROR:...unable to infer component type: mqtt"
Just trying to do a simple MQTT to MQTT bridge in a DFC, and I was getting this...
I also get it when I use the MQTT to Kafka bridge example template....
b
Post the config.yaml if you can
t
quick easy way to get that?
b
Working on that rn
kubectl get pods -n united-manufacturing-hub
Try to find the pod that is running that config.yaml
t
error: You must be logged in to the server (the server has asked for the client to provide credentials)
b
Ah one second
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
That sets your kubectl config, since k3s uses a different location that k8s
t
error: error loading config file "/etc/rancher/k3s/k3s.yaml": open /etc/rancher/k3s/k3s.yaml: permission denied
b
sudo?
t
I'm trying to kubectrl get pods....it says kbectl command not found when I do sudo
b
sudo KUBECONFIG=/etc/rancher/k3s/k3s.yaml kubectl get pods -n united-manufacturing-hub
Your user doesn't have permission to set the kubeconfig. This will open a SU shell, set the kubeconfig map, and then run the get command.
t
still sudo no kubectl
j
Yes, it is a known issue in the newest version 😦
Once I discovered this, this is where I said we need to stop delivering new features
Super easy fix
But we had team event today altogether
So we could not work on it
Tomorrow first thing
For the kubectl, check out the commands in the documentation
Sudo $(which kubectl) get pods etc etc
b
There is some user settings that are preventing you from allowing ur current ssh shell to not be allowed to set the kubeconfig path. SU also doesn't have kubectl added to its PATH. Forgot about all this.
t
so my list of items 1. sensorconnect not making it to DB 2. tag names being separated by both $ and . for some reason, but the ui for the query reflects all $ 3. The above issue for the DFC custom mqtt
j
All of our enterprise customers are notified already to not upgrade until further notice, we are doing a deep dive session with some changes in our release process to prevent this from happening again
2 and 3 I saw today already open PRs
1 we need to investigate
b
Glad to be breaking things for y'all over there to fix 🙂
PreviousNext
Powered by