Error center

Problem description: The build step fails to clone the code and reports the following error: Repository path not found, please check if the repository path is correct...

Solution: This issue can occur if the user who configured the pipeline's code source has left the organization or has had their permissions revoked. Verify that the account authorized by the service connection has the required permissions to clone the code repository.

Problem description: The Runner installation on the host fails with the error Runner register failed. , producing a log similar to the following.

Connecting to agent-install-cn-qingdao.oss-cn-qingdao-internal.aliyuncs.com (agent-install-cn-qingdao.oss-cn-qingd
ao-internal.aliyuncs.com)|100.115.173.8|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3441 (3.4K) [text/x-sh]
Saving to: '/tmp/aliyun/yunxiao-runner/install.sh'
     0K ...                                     100%  349M=0s
2023-03-10 09:33:06 (349 MB/s) – '/tmp/aliyun/yunxiao-runner/install.sh' saved [3441/3441]
INFO[2023-03-10T09:33:06+08:00] [Register] options: {"URL":"https://gray-devops-build.aliyuncs.com","Token":"PRRvr
Mb4sKhgCGrqLzgt","Tenant":"be-yxctbiii2ml4aydisrlfozvk","Workspace":"/root/yunxiao/be-yxctbiii2ml4aydisrlfozvk/run
ner","SceanInterval":5,"Concurrency":50,"RunnerGroupUUID":"HY8UhW1PmS2hpw27","ConfigPath":"/root/yunxiao/be-yxctbiii2ml4ayd
isrlfozvk/runner/config","InstanceId":"i-m5e1ct61ztfma76svxr4","InstanceName":"flow-deploy-test2","AutoUpgrade":tr
ue,"UpgradeInterval":1200}
INFO[2023-03-10T09:33:06+08:00] Runner config file not exists, generating...
INFO[2023-03-10T09:33:06+08:00] bind to HY8UhW1PmS2hpw27
INFO[2023-03-10T09:33:26+08:00] POST /api/v2/runner/register, time spent 20.00 s
INFO[2023-03-10T09:33:26+08:00] register runner=074d1122e7bb4abeaf2fcc5d5184a3ab
ERRO[2023-03-10T09:33:26+08:00] Runner register failed.
WARN[2023-03-10T09:33:26+08:00] configfile /root/yunxiao/be-yxctbiii2ml4aydisrlfozvk/runner/config/config.yml remo
ved.
FATA[2023-03-10T09:33:26+08:00] couldn't execute POST against https://gray-devops-build.aliyuncs.com/api/v2/runne
r/register: Post https://gray-devops-build.aliyuncs.com/api/v2/runner/register: net/http: request canceled while w
aiting for connection (Client.Timeout exceeded while awaiting headers)

Solution: This is usually a transient Runner registration issue. Retry the installation later.

Problem description: Deployment to the host fails with an error indicating the Runner is unavailable.

Solution:

1. Check if the host disk is full by running df -hl. If the disk is full, clean up disk space and retry the operation.

2. Check the status of the Runner service. If the status is not active(running), run the systemctl restart runner-{version}-{tenant_name}.service command to restart the service.

3. Check for network connectivity issues.

   1. Run the systemctl status runner-{version}-{tenant-name}.service command to check the status of the Runner service, and retrieve the --configPath=*** parameter from the service process, as shown below.

      [root@ecs-for-batch-deploy-1 ~]# systemctl status runner-v0.5-be-bnyxxxlllzpci0q606yt.service
      ● runner-v0.5-be-xxxlllzpci0q606yt.service – Aliyun yunxiao runner polling jobs to execute
           Loaded: loaded (/etc/systemd/system/runner-v0.5-be-bxxxpci0q606yt.service; enabled; vendor preset: disabled)
           Active: active (running) since Tue 2022-10-11 10:50:56 CST; 41min ago
         Main PID: 1405243 (runner)
            Tasks: 10 (limit: 48875)
           Memory: 13.7M
           CGroup: /system.slice/runner-v0.5-be-bnyxxxq606yt.service
                   └─1405243 /usr/local/share/yunxiao-runner/v0.5/runner run --configPath=/root/yunxiao/be-bnykv60t83lllzpci0q606yt/runner/config
      10月 11 11:31:46 ecs-for-batch-deploy-1 runner[1405243]: INFO[2022-10-11T11:31:46+08:00] [runner] no new job, skip.                    runner=9e7073c92b2fa8b35bc0efd3eec051f8
      10月 11 11:31:46 ecs-for-batch-deploy-1 runner[1405243]: INFO[2022-10-11T11:31:46+08:00] counter current: 0, limit: 50
      10月 11 11:32:01 ecs-for-batch-deploy-1 runner[1405243]: WARN[2022-10-11T11:32:01+08:00] Response status code: 204 body data:
      10月 11 11:32:01 ecs-for-batch-deploy-1 runner[1405243]: INFO[2022-10-11T11:32:01+08:00] POST /api/v2/builds/request, time spent 15.07 s
      10月 11 11:32:01 ecs-for-batch-deploy-1 runner[1405243]: INFO[2022-10-11T11:32:01+08:00] [runner] no new job, skip.                    runner=9e7073c92b2fa8b35bc0efd3eec051f8
      10月 11 11:32:01 ecs-for-batch-deploy-1 runner[1405243]: INFO[2022-10-11T11:32:01+08:00] counter current: 0, limit: 50
      10月 11 11:32:16 ecs-for-batch-deploy-1 runner[1405243]: WARN[2022-10-11T11:32:16+08:00]

   2. View the URL in the configPath using cat {***}/config.yml | grep url.

      [root@ecs-for-batch-deploy-1 config]# cat /root/yunxiao/be-bnykv60t83lllzpci0q606yt/runner/config/config.yml | grep url
      url: https://xxx.com
      [root@ecs-for-batch-deploy-1 config]#

   3. Run the following command to check if the URL is accessible.

      # Note: Replace {url} in the command below with your actual URL.
      curl '{url}/api/v2/runner/storage/latest?os=linux&arch=amd64'

Problem description: When you use an Alibaba Cloud service connection to access Alibaba Cloud resources, you receive the error: "The RAM role does not have permission to access resources".

Solution: Check if the account authorized by the service connection has an AliyunDevopsRolePolicy permission policy that denies access to your Alibaba Cloud DevOps organization ID. If such a policy exists, delete it, wait 5 to 10 minutes, and then retry the operation.

This policy can be identified in its JSON Statement where the Action is devops:UseServiceAuth, the Resource value ends with your Alibaba Cloud DevOps organization ID (for example, 643f85d1b0e1dda6507e5a23), and the Effect is Deny. Once you confirm that the organization ID in the policy matches yours, delete the policy.