[ci] r-package (ubuntu-latest, clang, R 3.6, cmake) job fails when downloading GPG key

[jameslamb]

Description

The r-package (ubuntu-latest, clang, R3.6, cmake) CI job is failing across several PRs, with the following error

Executing: /tmp/apt-key-gpghome.TJXpN45yKk/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys E298A3A825C0D65DFD57CBB651716619E084DAB9
gpg: keyserver receive failed: Cannot assign requested address

Reproducible example

I've observed this failure over several commits over the last few days. Manually re-running tended to help, but today I saw it fail 3 times in a row: https://github.com/microsoft/LightGBM/actions/runs/5848902304/job/15859758034?pr=6037.

Maybe the decreasing effectiveness of retries means the issue is related to somme change in GitHub Actions that was gradually rolled out over the last few days, and maybe now most/all workflow runs are running under whatever conditions cause this to fail? I'm not sure.

I was also able to reproduce this locally, like this:

docker run --rm -it ubuntu:18.04 bash

apt-get update -y
apt-get install --no-install-recommends -y \
    ca-certificates \
    dirmngr \
    gpg \
    gpg-agent \
    software-properties-common \
    sudo

sudo apt-key adv \
    --keyserver keyserver.ubuntu.com \
    --recv-keys E298A3A825C0D65DFD57CBB651716619E084DAB9

That uses the same container image the job uses

LightGBM/.github/workflows/r_package.yml

Lines 42 to 47 in 5c9e61d

	- os: ubuntu-latest
	task: r-package
	compiler: gcc
	r_version: 3.6
	build_type: cmake
	container: 'ubuntu:18.04'

And similar code to what's running when the job breaks

LightGBM/.ci/test_r_package.sh

Lines 38 to 41 in 5c9e61d

	if [[ $OS_NAME == "linux" ]]; then
	sudo apt-key adv \
	--keyserver keyserver.ubuntu.com \
	--recv-keys E298A3A825C0D65DFD57CBB651716619E084DAB9 || exit -1

Environment info

LightGBM version or commit hash: multiple PRs in recent days (after 5c9e61d)

Additional Comments

This looks similar to what's documented in usbarmory/usbarmory-debian-base_image#9. That issue suggests that it has something to do with mixed support for IPv6 in the tools involved in downloading and using that GPG key.

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.