search

josmo / drone-rancher

Drone plugin for triggering Rancher deployments
53 stars 35 forks source link

Confirm fails #8

Closed Miminoux closed 7 years ago

Miminoux commented 8 years ago

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 :

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 8 years ago

Set the timeout higher

cusspvz commented 8 years ago

Same here. https://github.com/drone/drone/issues/1663#issue-158401177

jandragsbaek commented 8 years ago

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 7 years ago

+1

Having the same issue

cusspvz commented 7 years ago

@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 7 years ago

@Miminoux can you close this issue?

jandragsbaek commented 7 years ago

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

cusspvz commented 7 years ago

@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 7 years ago

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

cusspvz commented 7 years ago

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

josmo commented 7 years ago

@cusspvz thanks I'm closing this.