Bug #2076
Environment variables not exported after recent changes
| Status: | Closed | Start date: | 11/04/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | R. Haschke | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
The recent changes somehow resulted in the fact that environment variables are not exported to client connections anymore. E.g. VDEMO_root is not available so that sourcing the standard component suffix fails.
History
#1 Updated by R. Haschke over 9 years ago
I cannot confirm the bug.
However, I fixed another bug, resulting in wrong component status, because the result of ssh_command's was not forwarded correctly anymore.
#2 Updated by J. Wienke over 9 years ago
When reverting back to the old state, everything works. I also opened a shell on the host and nothing like VDEMO_* existed in env.
#3 Updated by R. Haschke over 9 years ago
- Status changed from New to Feedback
#4 Updated by R. Haschke over 9 years ago
- Status changed from Feedback to Closed
Presumably a follow-up bug of the nfs issue: if the master.sh cannot be found on the remote, VDEMO_root will not be initialized
I didn't observe the bug any time.