Workflow run 'GreptimeDB Nightly Build' failed

[github-actions[bot]]

@GreptimeTeam/db-approver New failure: https://github.com/GreptimeTeam/greptimedb/actions/runs/9752761879

[github-actions[bot]]

@GreptimeTeam/db-approver New failure: https://github.com/GreptimeTeam/greptimedb/actions/runs/9752761879

[zyy17]

The error message:

#7 [2/3] RUN yum install -y epel-release     openssl     openssl-devel      centos-release-scl      rh-python38      rh-python38-python-devel
#7 0.140 Loaded plugins: fastestmirror, ovl
#7 0.215 Determining fastest mirrors
#7 0.227 Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=container error was
#7 0.227 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"
#7 0.229 
#7 0.229 
#7 0.229  One of the configured repositories failed (Unknown),
#7 0.229  and yum doesn't have enough cached data to continue. At this point the only
#7 0.229  safe thing yum can do is fail. There are a few ways to work "fix" this:
#7 0.229 
#7 0.229      1. Contact the upstream for the repository and get them to fix the problem.
#7 0.229 
#7 0.229      2. Reconfigure the baseurl/etc. for the repository, to point to a working
#7 0.229         upstream. This is most often useful if you are using a newer
#7 0.229         distribution release than is supported by the repository (and the
#7 0.229         packages for the previous distribution release still work).
#7 0.229 
#7 0.229      3. Run the command with the repository temporarily disabled
#7 0.229             yum --disablerepo=<repoid> ...
#7 0.229 
#7 0.229      4. Disable the repository permanently, so yum won't use it by default. Yum
#7 0.229         will then just ignore the repository until you permanently enable it
#7 0.229         again or use --enablerepo for temporary usage:
#7 0.229 
#7 0.229             yum-config-manager --disable <repoid>
#7 0.229         or
#7 0.229             subscription-manager repos --disable=<repoid>
#7 0.229 
#7 0.229      5. Configure the failing repository to be skipped, if it is unavailable.
#7 0.229         Note that yum will try to contact the repo. when it runs most commands,
#7 0.229         so will have to try and fail each time (and thus. yum will be be much
#7 0.229         slower). If it is a very temporary problem though, this is often a nice
#7 0.229         compromise:
#7 0.229 
#7 0.229             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
#7 0.229 
#7 0.229 Cannot find a valid baseurl for repo: base/7/x86_64
#7 ERROR: process "/bin/sh -c yum install -y epel-release     openssl     openssl-devel      centos-release-scl      rh-python38      rh-python38-python-devel" did not complete successfully: exit code: 1
------
 > [2/3] RUN yum install -y epel-release     openssl     openssl-devel      centos-release-scl      rh-python38      rh-python38-python-devel:
0.229 
0.229      5. Configure the failing repository to be skipped, if it is unavailable.
0.229         Note that yum will try to contact the repo. when it runs most commands,
0.229         so will have to try and fail each time (and thus. yum will be be much
0.229         slower). If it is a very temporary problem though, this is often a nice
0.229         compromise:
0.229 
0.229             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
0.229 
0.229 Cannot find a valid baseurl for repo: base/7/x86_64

Seems the mirrorlist.centos.org is not a valid service for centos:7 image.

[github-actions[bot]]

@GreptimeTeam/db-approver Back to success: https://github.com/GreptimeTeam/greptimedb/actions/runs/9756147957