Issue #1135 has been updated by Henrik Lindberg.

Description updated
Status changed from Accepted to Closed
Target version set to 3.3.0

--parseonly no longer exists, it has been replaced by `puppet validate`

Could not reproduce problem in Puppet 3x. Closing issue as fixed.

----------------------------------------
Bug #1135: parseonly incorrectly attempts to validate presence of parent classes
https://projects.puppetlabs.com/issues/1135#change-98538

* Author: micah -
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: language
* Target version: 3.3.0
* Affected Puppet version: 0.24.8
* Keywords: 
* Branch: 
----------------------------------------

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:

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

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.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to