Branch run with noresm2_5_alpha08d seems to fail during FATES initialization

[matsbn]

Brief summary of bug

I tried to make a branch run from NorESMhub/noresm3_dev_simulations#68. The simulation crashed during initialization with the cesm log mentioning allocation of already allocated array as reason for the crash.

General bug information

CTSM version you are using: ctsm5.3.11-noresm_v1

Does this bug cause significantly incorrect results in the model's science? N/A

Configurations affected: N/A

Details of bug

What seems to be the key extract from cesm.log.*:

 398: forrtl: severe (151): allocatable array is already allocated
 398: Image              PC                Routine            Line        Source             
 398: cesm.exe           00000000036626FF  Unknown               Unknown  Unknown
 398: cesm.exe           000000000281A7B8  edinitmod_mp_init         144  EDInitMod.F90
 398: cesm.exe           00000000024D3E98  clmfatesinterface        2091  clmfates_interfaceMod.F90
 398: cesm.exe           00000000024999F9  clm_initializemod         760  clm_initializeMod.F90
 398: cesm.exe           0000000002438C6B  lnd_comp_nuopc_mp         658  lnd_comp_nuopc.F90

Important details of your setup / configuration so we can reproduce the bug

All case settings are as in NorESMhub/noresm3_dev_simulations#68. The case folder is here:

/cluster/projects/nn9560k/matsbn/NorESM/cases/n1850.ne30_tn14.hybrid_wavparam_vfcor_fatessp.20250204

The run folder is here:

/cluster/work/users/matsbn/noresm/n1850.ne30_tn14.hybrid_wavparam_vfcor_fatessp.20250204/run

[rosiealice]

Hi @matsbn this does seem to already by an issue on the FATES side

NGEET/fates#1271

I will try and follow up on the plan for this asap.

[rosiealice]

@mvdebolskiy I think I remember that Mariana came across this and possibly created a workaround. Can you remember anything about that?