Marian first reported this issue. On update to 4.0.2 esmond failed because no SECRET KEY was set in django settings.py file. This was because the host in question was pointing at SCL and had a different version of python27 than we provided. The same issue occurred on ESnet. I was able to confirm on a VM not using SCL that the latest RPM works fine.
Marian first reported this issue. On update to 4.0.2 esmond failed because no SECRET KEY was set in django settings.py file. This was because the host in question was pointing at SCL and had a different version of python27 than we provided. The same issue occurred on ESnet. I was able to confirm on a VM not using SCL that the latest RPM works fine.