search

DUNE-DAQ / nanorc

2 stars 2 forks source link

env vars not passed to daq applications in the current --k8s development environment #86

Closed ron003 closed 2 years ago

ron003 commented 2 years ago

Pierre has confirmed on the daq-ccm channel that the env.vars. are currently not being passed correctly

tapperad commented 2 years ago

This is linked to the issue on changes to boot.json for k8s -- trivial when that's completed.

tapperad commented 2 years ago

@ron003 Will this solve this second of your pocket issues in the Triage category?

https://github.com/DUNE-DAQ/pocket/issues/18

ron003 commented 2 years ago

I don't think it will solve the issue, but there will be a workaround as long as the TRACE_FILE env can be set. In order to solve it, there should be an attempt to strip the host prefix to the shared area from the TRACE_FILE path before passing it to the container environment.

plasorak commented 2 years ago

I think this is done too, I'll let Ron reopen the issue if something still needs to be fixed.

plasorak commented 2 years ago

Hi @ron003 going back to this, is it not possible for a developper who wants to do TRACE debugging to get on the pod? The following will get your a bash shell in the pod:

kubectl exec --stdin --tty the_pod_name -- /bin/bash

And then setup dunedaq from there and do traces?

ron003 commented 2 years ago

This issue is about the environment variables... In order for the application to do TRACEing, at least one of the "TRACE activating" environment variables must be set in it's environment (i.e before the application executes the TLOG debug statements) So, logging into the pod after the application has started (if that is what you're talking about) would be too late.