josmo/drone-rancher

Confirm fails

Closed this issue · 11 comments

Miminoux commented

Hi,

I have a problem for the confirmation step, it ends up with status code "1" but there is no line printed out whereas I read in the main.go that there should be either :

  • "Error waiting for service upgrade to complete" if after 30 seconds the service wouldn't be upgraded (the service is updated in time)
  • "Unable to finish upgrade" if the method ActionFinishupgrade would have returned an error
  • "Finished upgrade" if everything went fine

Here is the log output :
[info] Pulling image artifactory.myoffice.me.fr:5001/drone-rancher:latest
Drone Rancher Plugin built at 2016-02-02 08:56:57 UTC
Upgraded glpi/glpi to docker:artifactory.myoffice.me:5003/glpi:latest
[info] build failed (exit code 1)

On Rancher, the service is upgraded but not confirmed.

Here is the deploy part of my .drone.yml :
deploy:
rancher:
image: artifactory.myoffice.me:5001/drone-rancher:latest
url: 'https://rancher.myoffice.me'
access_key: xxx
secret_key: xxx
service: glpi/glpi
docker_image: 'artifactory.myoffice.me:5003/glpi:latest'
start_first: true
confirm: true

Any idea ?

Thx

qrpike commented

Set the timeout higher

jandragsbaek commented

I am seeing this too.

Tried with timeout at different values, with same results. It seems like it is waiting for something. Last log lines are:

[info] Pulling image plugins/drone-rancher:latest
Drone Rancher Plugin built from b4cd686
Upgraded micro-tools/app to docker:docker.falconsocial.com/tools/micro-tools:latest
rgauny commented

+1

Having the same issue

cusspvz commented

@rgauny Increase the timeout.

Example:

  rancher:
    url: https://xxx
    access_key: xxx
    secret_key: xxx
    service: xxx/xxx
    docker_image: xxx/xxx:$$COMMIT
    start_first: true
    confirm: true
    timeout: 180
    when:
      branch:
        - xxx
cusspvz commented

@Miminoux can you close this issue?

jandragsbaek commented

@cusspvz I raised the timeout to 300, still having the issue

cusspvz commented

@nayena Do an analisys on what's happening on both sides. On my cases, I've seen that the upgrade job was still running after 120 seconds, so I've set the timeout to 180. You must check yours. If it doesn't solve, perhaps you are experiencing a bug.

josmo commented

I'm trying to clean up issues on this plugin. Is this still an issue for anyone?

cusspvz commented

@josmo, increasing the timeout worked for me. Assuming it also worked for @nayena since he did not replied, you can close this.

josmo commented

@cusspvz thanks I'm closing this.