As described in the issue, recent tests of the master branch (production) revealed that the glidein startup failed. While these changes were already introduced in an ongoing PR for the development branch, these were not merged into the production branch since I was of the opinion that once the PR gets merged to development, the production would also be synced, which later Marco explained is not true (it's the other way around actually).
The test revealed that the production branch resulted in failing glideins with the message lsb_release: command not found because /usr/bin/lsb_release utility was not installed on the EL9 ITB CE where the changes for issue #371 was tested. It was confirmed by Marco that lsb_release is in epel repository and therefore, we should not count on it to be installed/available in the target CE where GlideinWMS code runs to start the glidein(s).
Fixes #423.
As described in the issue, recent tests of the
masterbranch (production) revealed that the glidein startup failed. While these changes were already introduced in an ongoing PR for the development branch, these were not merged into the production branch since I was of the opinion that once the PR gets merged to development, the production would also be synced, which later Marco explained is not true (it's the other way around actually).The test revealed that the production branch resulted in failing glideins with the message
lsb_release: command not foundbecause/usr/bin/lsb_releaseutility was not installed on the EL9 ITB CE where the changes for issue #371 was tested. It was confirmed by Marco thatlsb_releaseis inepelrepository and therefore, we should not count on it to be installed/available in the target CE where GlideinWMS code runs to start the glidein(s).