v7r3: $DIRAC/etc to $DIRAC/diracos/etc

[marianne013]

In order to simulate the use cases we typically see, we test the use of dirac-* commands in our standard certification tests.
This currently fails in our cloud tests:

2021-11-19 13:20:05 UTC Framework [139980649228096] DEBUG: dirac.cfg should be at /mnt/dirac/diracos/etc/dirac.cfg
2021-11-19 13:20:05 UTC Framework [139980649228096] WARN: Can't load /mnt/dirac/diracos/etc/dirac.cfg file
2021-11-19 13:20:05 UTC Framework [139980649228096] DEBUG: Updating configuration internals
Parsing command line
Running without remote configuration
Trying to load Resources.LogBackends.StdoutBackend
Trying to load DIRAC.Resources.LogBackends.StdoutBackend
2021-11-19 13:20:05 UTC dirac-proxy-info [139980649228096] FATAL: Missing mandatory local configuration option /DIRAC/Setup
2021-11-19 13:20:05 UTC dirac-proxy-info [139980649228096] ERROR: There were errors when loading configuration

@sfayer would like to enquire:
Can we get an official statement whether the move from $DIRAC/etc to
$DIRAC/diracos/etc was actually intentional?

Was it ?

[marianne013]

@chrisburr @atsareg
Sorry to come back to this, but I am now completely confused.
In older versions I cna get around this by making a symlink. The newer version mounts the diracos dir from outside the container as read-only, so I can't. How is this meant to work (the first order goal is to make DIRAC tools available to the user on the cloud).

[marianne013]

I've just rerun my tests from before Christmas, and at least with the ExtraPilotOptions set to --userEnvVariables DIRACSYSCONFIG:::../../pilot.cfg it now seems to work everywhere. It's really hard to develop against an unversioned target ....