Pending status stuck when Drone version > 1.4.0

Drone Support
1

While updating drone from version 1.4.0 to 1.6.1 it appears that any jobs get stuck at the beginning with the ‘default: Pending’ message (same with 1.5). Reverting back to 1.4.0 successfully restore the job triggering and go until complete…

Here is a .drone.yml that fail (Gitea/Gogs - Git - No such device or address - Debugging):

kind: pipeline
name: default

clone:
  disable: true

steps:
- name: debug
  image: alpine
  commands:
  - env
  - ls -lah
  - apk add --no-cache git curl
  - echo $DRONE_REPO_PRIVATE
  - curl -v $DRONE_GIT_HTTP_URL

Here is the log when triggering the job:

drone-server_1  | {"level":"debug","msg":"api: root access granted","name":"drone-test","namespace":"mynamespace","request-id":"1SbFx8bnPkJie1zOogiC22EjZd0","time":"2019-10-23T09:57:11Z","user.admin":true,"user.login":"mynamespace"}
drone-server_1  | {"level":"debug","msg":"api: root access granted","name":"drone-test","namespace":"mynamespace","request-id":"1SbFx8bnPkJie1zOogiC22EjZd0","time":"2019-10-23T09:57:11Z","user.admin":true,"user.login":"mynamespace"}
drone-server_1  | {"commit":"10fc0a5195311c651a70e6f154112d1dd0aef0ae","event":"push","level":"debug","msg":"trigger: received","ref":"refs/heads/master","repo":"mynamespace/drone-test","time":"2019-10-23T09:57:11Z"}
drone-server_1  | {"fields.time":"2019-10-23T09:57:12Z","latency":745156525,"level":"debug","method":"POST","msg":"","remote":"192.168.128.2:39418","request":"/api/repos/mynamespace/drone-test/builds/9","request-id":"1SbFx8bnPkJie1zOogiC22EjZd0","time":"2019-10-23T09:57:12Z"}
drone-server_1  | {"level":"debug","msg":"api: root access granted","name":"drone-test","namespace":"mynamespace","request-id":"1SbFxESkPbdTsSjZUm1lhPzzOEe","time":"2019-10-23T09:57:12Z","user.admin":true,"user.login":"mynamespace"}
drone-server_1  | {"fields.time":"2019-10-23T09:57:12Z","latency":862018,"level":"debug","method":"GET","msg":"","remote":"192.168.128.2:39418","request":"/api/repos/mynamespace/drone-test","request-id":"1SbFxESkPbdTsSjZUm1lhPzzOEe","time":"2019-10-23T09:57:12Z"}
drone-server_1  | {"level":"debug","msg":"api: root access granted","name":"drone-test","namespace":"mynamespace","request-id":"1SbFxEmObIm02gfyvmqnDJm6X69","time":"2019-10-23T09:57:12Z","user.admin":true,"user.login":"mynamespace"}
drone-server_1  | {"fields.time":"2019-10-23T09:57:12Z","latency":13662556,"level":"debug","method":"GET","msg":"","remote":"192.168.128.2:39418","request":"/api/repos/mynamespace/drone-test/builds/10","request-id":"1SbFxEmObIm02gfyvmqnDJm6X69","time":"2019-10-23T09:57:12Z"}

I must add that this drone setup is a single instance (only the server, no runners)…

2

see 1.5.0 release notes

3

Thank you @bradrydzewski, indeed this make sense since I just noticed that by adding a runner it works!..

So either add a runner or set the following:

DRONE_AGENTS_DISABLED=true
4

@trepmag thanks for posting the issue on this forum. Even I was facing the same issue, now it’s resolved.
@bradrydzewski can you please add the parameter “DRONE_AGENTS_DISABLED=true” on your hosted platform “cloud.drone.io” as well. As jobs were getting stuck on Pending status.

Many Thanks

5

cloud.drone.io uses agents, therefore we would not set a parameter that disables agents.

there are many reasons a build can sit in queue, unrelated to what is being discussed in this thread. If your builds are stuck on cloud.drone.io you are probably using an unsupported os/arch or you are trying to use a pipeline type that is not supported. When there are no matching runners to pick up a build, they sit in queue.

6

Oh I see, thanks for the clarification @bradrydzewski