gdas_arch_tar_gdasocean_analysis error #4158
Description
What is wrong?
In rt17 for stream2, one of the gads_arch_tar_gdasocean_analysis jobs failed 3 times before succeeding.
The full logs can be found here:
/lfs/h2/emc/gfstemp/emc.global/comroot/rt17_upd03_stream2/logs/2024081306/gdas_arch_tar_gdasocean_analysis*
HTAR: HTAR SUCCESSFUL
[connecting to hpsscore1.fairmont.rdhpcs.noaa.gov/1217]
ERROR: htar_LFW_Thread: (line 2679,lfwthread 0) file gdas.20240813/06/conf/backup_tarballs.yaml:size changed from 156 to 154
###WARNING htar returned non-zero exit status.
72 = /apps/prod/hpss/bin/htar -c -v -P -f /2year/NCEPDEV/emc-global/emc.glopara/WCOSS2/GFSv17/rt17_upd03_stream2/2024081306/gdasocean_analysis.tar gdas.20240813/06/analysis/ocean/gdas.t06z.ocninc.nc gdas.20240813/06/analysis/ice/20240813.030000.cice_model_anl.res.nc gdas.20240813/06/analysis/ocean/gdas.t06z.ocn.incr.nc gdas.20240813/06/analysis/ocean/gdas.t06z.ice.incr.nc gdas.20240813/06/bmatrix/ocean/gdas.t06z.ocean.bkgerr_parametric_stddev.nc gdas.20240813/06/bmatrix/ice/gdas.t06z.ice.bkgerr_parametric_stddev.nc gdas.20240813/06/bmatrix/ocean/gdas.t06z.ocean.recentering_error.nc gdas.20240813/06/bmatrix/ocean/gdas.t06z.ocean.steric_explained_variance.nc gdas.20240813/06/conf/gdas.t06z.soca_setcorscales.yaml gdas.20240813/06/conf/gdas.t06z.soca_chgres.yaml gdas.20240813/06/conf/gdas.t06z.soca_diagb.yaml gdas.20240813/06/conf/gdas.t06z.gridgen.yaml gdas.20240813/06/conf/gdas.t06z.soca_vtscales.yaml gdas.20240813/06/conf/gdas.t06z.soca_ensweights.yaml gdas.20240813/06/conf/gdas.t06z.bmat_fields_metadata.yaml gdas.20240813/06/conf/obsop_name_map.yaml gdas.20240813/06/conf/gdas.t06z.obsop_name_map.yaml gdas.20240813/06/conf/backup_tarballs.yaml gdas.20240813/06/conf/var.yaml gdas.20240813/06/conf/gdas.t06z.soca_ensb.yaml gdas.20240813/06/conf/gdas.t06z.snowanlvar.yaml gdas.20240813/06/conf/gdas.t06z.soca_parameters_diffusion_vt.yaml gdas.20240813/06/conf/gdas.t06z.soca_parameters_diffusion_hz.yaml gdas.20240813/06/conf/fields_metadata.yaml gdas.20240813/06/conf/soca_incpostproc.yaml gdas.20240813/06/analysis/ocean/diags/insitu_temp_surface_drifter.nc gdas.20240813/06/analysis/ocean/diags/sss_smos_l2.nc gdas.20240813/06/analysis/ocean/diags/insitu_salt_profile_argo.nc gdas.20240813/06/analysis/ocean/diags/icec_amsr2_north.nc gdas.20240813/06/analysis/ocean/diags/sst_viirs_npp_l3u.nc gdas.20240813/06/analysis/ocean/diags/icec_amsr2_south.nc gdas.20240813/06/analysis/ocean/diags/sss_smap_l2.nc gdas.20240813/06/analysis/ocean/diags/sst_avhrrf_mb_l3u.nc gdas.20240813/06/analysis/ocean/diags/sst_avhrrf_mc_l3u.nc gdas.20240813/06/analysis/ocean/diags/sst_viirs_n20_l3u.nc gdas.20240813/06/analysis/ocean/diags/insitu_temp_profile_argo.nc gdas.20240813/06/analysis/ocean/diags/sst_viirs_n21_l3u.nc
Unlike #4155 I don't see any log files being archived in the log but I do see this:
https://github.com/NOAA-EMC/global-workflow/blob/develop/parm/archive/gdasocean_analysis.yaml.j2#L39
which might need an explicit list instead of *
What should have happened?
Tar files should be created without issue.
What machines are impacted?
WCOSS2
What global-workflow hash are you using?
https://github.com/JessicaMeixner-NOAA/global-workflow/tree/retrotest17update but i suspect I'll see this in develop too.
Steps to reproduce
We were running C1152 cases under gfsv17, but I suspect other cases should run into this.
Additional information
Tagging @guillaumevernieres @AndrewEichmann-NOAA @CatherineThomas-NOAA @RuiyuSun
Do you have a proposed solution?
Make an explicit list of conf files that are desired to be archived or check dependencies. @guillaumevernieres - can you help with creating the explicit list of conf files you want archived?
Metadata
Metadata
Assignees
Labels
Type
Projects
Status