-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autoload puppet/type/domain #38
Comments
@scarby Hmm, you're the second person who's reported that issue, but I've still not been able to replicate... See #34 for other issue. Can you confirm the following:
I'll then try and re-produce it again. |
module is taken from the master branch of this github repo - i have forked it and introduced a JMScluster provider, but at the moment that is not being called The error looks slightly different - yet very similar. (puppet 3.7.1, ubuntu 12.04, ruby 1.8.7) class { 'glassfish':
create_domain => true,
domain_name => 'domain1'
}
glassfish::create_cluster { 'vidispine':
cluster_name => 'vidispine',
} (i know domain1 is a terrible name but its replicating config that already exists) Initially i encountered this error, however it seemed intermittent - and would fail only on some runs. However now its pretty consistent the below shows that the cluster has actually been created at some point
Also if i stop calling create cluster everything works |
Might be worth rebasing off the develop branch, as there's a fair few changes in there that aren't on the master yet... I'll try and replicate it again over the next couple of days and come back to you... I'd be interested in reviewing/adding the JMSCluster provider to this module if necessary aswell :) Cheers |
Thanks I'll send you a pull request when i get everything working Adam On Wed, Oct 22, 2014 at 5:26 PM, Gavin Williams notifications@github.com
|
Ok, i have rebased from the develop branch and receive the same errors (seemingly only when i reference defined types such as create cluster) Adam |
Hmm, ok... Possibly gives me something a bit more specific to focus on... |
@scarby I've not been able to replicate the issue on a vagrant Ubuntu 12.04 machine running Puppet 3.7.1... One other question - are you using |
having now returned from some time away, it would appear that having rebuilt the puppet master i'm not getting the error again. I'm not entirely certain what caused it :(. |
Cheers for letting me know... |
Hi
I'm seeing the following when attempting to create a cluster resource using the glassfish module (interestingly enough i have seen this succeed - and the cluster exists and was created by the module)
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/type/domain: Could not autoload puppet/provider/domain/asadmin: no such file to load -- puppet/provider/asadmin on node vid03-prod-zonza.zonza.prv
have checked and these providers exist (obviouslt) and have been synced to the agent
Any ideas?
Thanks
Adam
The text was updated successfully, but these errors were encountered: