Dispatch to one node only shows "1 node ok" even if job fails

#519

With this job and with the dbapp tag only matching one node, the job fails but the failed node list shows "1 ok".

- id: 39cc0eca-8a04-4889-a2a1-82a68670bc04
  project: dbapp
  loglevel: INFO
  sequence:
    keepgoing: false
    strategy: node-first
    commands:
    - exec: 'false'
  description: ''
  name: false2
  uuid: 39cc0eca-8a04-4889-a2a1-82a68670bc04
  nodefilters:
    dispatch:
      threadcount: 1
      keepgoing: false
      excludePrecedence: true
    include:
      tags: dbapp
  group: temp

Reported by Moses Lei · February 16th, 2012 @ 04:15 PM

Activity

Moses Lei
Bug also appears if you dispatch to local only.

February 16th, 2012 @ 04:16 PM
Greg Schueler
- Tag set to node failures, bug, logging
- Assigned user set to Greg Schueler
bug was: if keepgoing is false and the execution simply failed (i.e. didn't throw an exception like connection timeout), then the node failure was not reported.

May 1st, 2012 @ 05:25 PM
Greg Schueler
- State changed from new to needs_verification
(from [95a51f309c7de94df3fd1b8e7e4f60c9f54907f7]) Fix node failure reporting for keepgoing=false

If keepgoing was false, then execution failure that was not
caused by an exception would fail to report the failed node list

[#519 Dispatch to one node only shows "1 node ok" even if job fails state:needs_verification] https://github.com/dtolabs/rundeck/commit/95a51f309c7de94df3fd1b8e7...

May 1st, 2012 @ 05:27 PM
Greg Schueler
- State changed from needs_verification to resolved
May 16th, 2012 @ 05:29 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.