Re: [HTCondor-users] Major upgrade from Singularity to Apptainer coming

[Jason Patton <jpatton@xxxxxxxxxxx>]

Stuart,

The frontend configuration was hard-coded to request 9.0.16 pilots, and it has now been switched to ask for the latest 9.0.x version. I see 9.0.17 pilots showing up now. Keep us updated if you notice that these warnings start to go away (or keep showing up!).

Jason Patton

On Mon, Oct 10, 2022 at 7:47 PM Anderson, Stuart B. <sba@xxxxxxxxxxx> wrote:

> On Oct 7, 2022, at 2:15 PM, Brian Lin <blin@xxxxxxxxxxx> wrote:
>
> On 10/6/22 17:52, Anderson, Stuart B. wrote:
>>
>>
>> [stuart.anderson@condor-f3 ~]$ condor_run -a accounting_group=cit.test -a request_disk=10m "/bin/hostname -f && condor_version"
>> acas0714.usatlas.bnl.gov
>> $CondorVersion: 9.0.16 Aug 16 2022 PackageID: 9.0.16-1.1 $
>> $CondorPlatform: X86_64-CentOS_7.9 $
>> WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV_HAS_CVMFS_IGWN_PRIVATE_DATA as environment variable will not be supported in the future, use APPTAINERENV_HAS_CVMFS_IGWN_PRIVATE_DATA instead
>> WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV_HAS_FILE_lib64_libglib_2_0_so_0 as environment variable will not be supported in the future, use APPTAINERENV_HAS_FILE_lib64_libglib_2_0_so_0 instead
>> WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV__CONDOR_SCRATCH_DIR_OUTSIDE_CONTAINER as environment variable will not be supported in the future, use APPTAINERENV__CONDOR_SCRATCH_DIR_OUTSIDE_CONTAINER instead
>> ...
>
> Those warnings are thrown for each 'SINGULARITYENV_' var that does not have a corresponding 'APPTAINERENV_' var and this was addressed in HTCondor 9.0.17 and 9.10.0 here: https://opensciencegrid.atlassian.net/browse/HTCONDOR-1137. It turned out that the factory config needed to be updated for 9.0.17 but that's done so new pilots should not have this problem. Let us know if you continue to see it on new pilots!

Brian,
    I saw some jobs run over the weekend without these warnings. However, they are back again,

[stuart.anderson@condor-f3 ~]$ condor_run -a accounting_group=cit.test -a request_disk=10m "/bin/hostname -f && condor_version"
c-212-11.aglt2.org
$CondorVersion: 9.0.16 Aug 16 2022 PackageID: 9.0.16-1.1 $
$CondorPlatform: X86_64-CentOS_7.9 $
WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV_HAS_CVMFS_IGWN_PRIVATE_DATA as environment variable will not be supported in the future, use APPTAINERENV_HAS_CVMFS_IGWN_PRIVATE_DATA instead
WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV_HAS_FILE_lib64_libglib_2_0_so_0 as environment variable will not be supported in the future, use APPTAINERENV_HAS_FILE_lib64_libglib_2_0_so_0 instead
...

Is there some way to force old pilots to exit after they are done running any current jobs and not to accept any new ones?

And is it expected that there are no 9.0.17 versions reported by the following for the LIGO/IGWN pool?

[stuart.anderson@condor-f3 ~]$ condor_status -af condorversion -pool condor-osg.ligo.caltech.edu | sort | uniq -c
 Â2174 $CondorVersion: 9.0.16 Aug 16 2022 BuildID: 601457 PackageID: 9.0.16-1 $

Thanks.

--
Stuart Anderson
sba@xxxxxxxxxxx




_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/