The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Bug #14458

Status unchanged when "Could not apply complete catalog"

Added by Roman Skvazh almost 4 years ago. Updated over 2 years ago.

Status:AcceptedStart date:05/14/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:reports
Target version:-
Affected Puppet version: Branch:
Keywords:dependency cycle, total, errors

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket is now tracked at: https://tickets.puppetlabs.com/browse/PUP-735


Description

When puppet agent report:

Could not apply complete catalog: Found 1 dependency cycle: ... Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz

there is no failed nodes.

Screen Shot 2012-05-14 at 12.47.50.png (42.5 KB) Roman Skvazh, 05/14/2012 01:49 am

Screen Shot 2012-05-14 at 12.47.36.png (55.4 KB) Roman Skvazh, 05/14/2012 01:49 am


Related issues

Related to Puppet - Bug #19033: Exit status is 0, even in the presence of errors, without... Accepted
Related to Puppet - Bug #16082: Puppet agent with --detailed-exitcodes returns exit code ... Needs Decision 08/22/2012

History

#1 Updated by Kelsey Hightower almost 4 years ago

  • Status changed from Unreviewed to Accepted

Does the dashboard only report errors from reports sent by the agent?

#2 Updated by Roman Skvazh almost 4 years ago

Kelsey Hightower wrote:

Does the dashboard only report errors from reports sent by the agent?

I think, yes

#3 Updated by Ben Hughes almost 4 years ago

  • Project changed from Puppet Dashboard to Puppet
  • Target version deleted (1.2.x)

This is actually a bug in Puppet sending the report with unchanged, rather than failed:

  report_format: 2
  resource_statuses: {}
  status: unchanged

#4 Updated by Ben Hughes almost 4 years ago

  • Category set to reports

From adding a pp transaction.report to lib/puppet/transaction.rb:406

 @status="failed",
 @time=Thu Jun 28 16:51:38 -0700 2012>
err: Could not apply complete catalog: Found 1 dependency cycle:
(Exec[add-apt-repository-ppa:schwuk/znc] => Exec[apt_update] => Package[python-software-properties] => Exec[add-apt-repository-ppa:schwuk/znc])
Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
notice: Finished catalog run in 2.25 seconds
[root@shell:~]# less           
[root@shell:~]# grep status /var/lib/puppet/state/last_run_report.yaml                                                                                                          1
  resource_statuses: {}
  status: unchanged

So it’s being eaten, I think, somewhere in the middle of that.

#5 Updated by eric sorenson almost 4 years ago

  • Priority changed from Urgent to Normal

#6 Updated by Chris Bolt over 3 years ago

This doesn’t just affect reports, puppet exits with return code 0 as if the puppet run succeeded.

Error: Could not apply complete catalog: Found 1 dependency cycle:
(Exec[aptget_update] => Package[mysql-server-core-5.1] => File[/etc/apt/sources.list.d/percona.list] => Exec[aptget_update])
Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
Finished catalog run in 1.76 seconds
# echo $?
0

#7 Updated by Stepan Cenek over 2 years ago

I tried to fix it: https://github.com/puppetlabs/puppet/pull/1854

This is my first fix to Puppet so please be gentle with me :)

#8 Updated by Adrien Thebo over 2 years ago

  • Keywords changed from dependency cycle, total to dependency cycle, total, errors

Also available in: Atom PDF