Bug #353

puppetrun returns success even if triggering was unsuccessful

Added by Mario Martelli about 5 years ago. Updated almost 5 years ago.

Status:Closed Start date:
Priority:Normal Due date:
Assignee:Luke Kanies % Done:

0%
Category:-
Target version:0.25.0
Affected Puppet version:0.25.4 Branch:
Keywords:
Votes: 0

Description

puppetrun:

Triggering sop-cm01-01
sop-cm01-01 finished with exit code 0
Finished

puppet:

notice: Could not trigger run; already running

History

#1
Updated by Luke Kanies about 5 years ago

  • Status changed from 1 to 2

#2
Updated by Luke Kanies about 5 years ago

  • Status changed from 2 to Closed
  • 7 set to fixed

Fixed in r1975.

#3
Updated by Mario Martelli about 5 years ago

  • Status changed from Closed to 4
  • 7 deleted (fixed)

I just invoked puppetrun:

# puppetrun --host sop-cm01-01  -t testbed -t testrun
Failed to load ruby LDAP library. LDAP functionality will not be available
Triggering sop-cm01-01
sop-cm01-01 finished with exit code 0
Finished

puppetd:

notice: Could not trigger run; already running

Please note: puppetd seems to hang, it does nothing for about 10 minutes now

#4
Updated by Mario Martelli about 5 years ago

yes, it hung. Cause was #417

#5
Updated by Luke Kanies about 5 years ago

Are you sure this is using the latest puppetrun and the latest client? If the client said that it was already running, then it should have returned ‘running’, which puppetrun should now understand.

Either you’ve got some outdated code here, or there’s a much bigger problem.

#6
Updated by Luke Kanies almost 5 years ago

  • Status changed from 4 to Closed
  • 7 set to worksforme

I’m closing this, as I cannot get confirmation this is still a problem. It shouldn’t be possible to have this set of results with the current code base.

Also available in: Atom PDF