Puppet: System Administration Automated

Support

Ticket #1135 (new defect)

Opened 7 months ago

Last modified 6 months ago

parseonly incorrectly attempts to validate presence of parent classes

Reported by: micah Assigned to: community
Priority: normal Milestone:
Component: language Version: 0.24.2
Severity: normal Keywords: parseonly
Cc: Triage Stage: Accepted
Attached Patches: None Complexity: Unknown

Description

The '--parseonly' option to puppet is not working correctly. One user posted to the mailing list here: http://mail.madstop.com/pipermail/puppet-users/2008-February/006281.html about their problems, my problem is probably related. I'm running a --parseonly as a pre-commit hook to svn, and I am getting this: 

Could not find class nagios2::target at /etc/puppet/manifests/site.pp:60 on node puppetmaster

although that class exists, and if I start up that manifest with puppetmaster -v --no-daemonize, it has no problem with the manifest.

We had to disable the pre-commit hook.

Running 0.24.3rc1 from the 0.24.x branch.

Change History

03/20/08 20:17:28 changed by luke

  • summary changed from parseonly is confused to parseonly incorrectly attempts to validate presence of parent classes.
  • stage changed from Unreviewed to Needs more info.

You should only get this kind of problem if the class is mentioned as the parent class of the file you're testing, and only then if the class is in a different file.

My guess is that this is mentioned as your class's parent class, and it's in a file in a module, and that module is not in a place where the commit hook knows how to look for it.

It looks like this means that parseonly should ignore parent classes (which are normally checked at parse time).

If I'm wrong about this, please indicate so. Also, please be somewhat more descriptive in your bug titles.

04/08/08 18:06:32 changed by luke

  • component changed from client to language.
  • stage changed from Needs more info to Accepted.