Group is not being set to e3sm automatically during deployment on pm-cpu

[altheaden]

During the most recent deployment of Polaris, each of the environments I deployed in /global/cfs/cdirs/e3sm/software/polaris/pm-cpu/spack/ should have been given the e3sm group but they were not. I had to run the command:

chgrp -R e3sm /global/cfs/cdirs/e3sm/software/polaris/pm-cpu/spack/

which resolved the issue. However, Polaris is supposed to take care of this automatically.

[xylar]

@altheaden, would you be willing to see if you can debug this? It's not a top priority but something not to forget about before the next deployment.

I would suggest you do a fresh spack deployment using --spack to point to a new directory in your scratch space on Perlmutter.

Here is where the group should be getting changed.
https://github.com/E3SM-Project/polaris/blob/main/deploy/bootstrap.py#L1156
Can you add some prints to find out what it's actually doing? If you rerun deployment on a directory that you've already run on, it should be relatively quick to get to the same point for further debugging.