Closed stefanbschneider closed 5 years ago
Hi, some questions: Which environment? Which instantiation? NS or slices?
Hi, some questions: Which environment?
Which instantiation? NS or slices?
Hi, I've just merged what I think is the solution to your problem. Can you please try again whenever possible and confirm me if it works for you? (It should be deployed in both pre-int and int environments).
Hi, thanks!
I just tested on int, and it still didn't work. The env var is still unchanged
# env | grep MQTT
MQTT_BROKER_PORT=1883
MQTT_BROKER_HOST=172.31.13.158
Then I think we need someone else cause I saw the request sent and I am sending the params as:
So I see no error from Portal side that I am aware off...
I just checked your service on k8s and it worked!
localadmin@k8s-master:~$ kubectl -it exec eu-5gtango-smpilot-mdc-0-1-f83d83d7-868dd8cf48-g4s9l bash
root@eu-5gtango-smpilot-mdc-0-1-f83d83d7-868dd8cf48-g4s9l:/# env | grep MQTT
MQTT_BROKER_PORT=1883
MQTT_BROKER_HOST=10.200.16.31
Not sure where I went wrong, but I guess this is solved now. I'll try again with the Portal next time and let you know if it doesn't work then.
Thanks for the quick help :)
Mmmm I think I might know... you should try reloading your Portal tab with CTRL+SHIFT/MAYUS+R... Your Portal version might be yet the old one and it did not get updated. This happens sometimes...
It seems like passing instantiation params via the portal doesn't work.
I just tested it with NS2 of the industry pilot and passed parameter "MQTT_BROKER_HOST": "10.200.16.31", which should set the env var of the instance accordingly.
Still, when checking the instantiated VNF, the env var was not set correctly:
It works fine when using
tng-cli
with the--params_file
flag.Belongs to #443