Hi @all,
I have a small problem with my module test using spec_puppet. I use the
Puppetlabs MySQL module to create databases in my module. When running
"rake spec" my coverage report that not all resources are tested:
<--- snip --->
Mysql_database[test1]
Mysql_grant[test1@localhost/test1.*]
Mys
On Monday, February 15, 2016 at 1:55:39 PM UTC-6, Joseph Karns wrote:
When I run the agent it picks up nothingI'm super confused and the
> module needs WAY MORE documentation. I've added --debug and can see that
> the class is being applied because I can see the providers are being picked
On 16 February 2016 at 09:37, Thomas Bendler wrote:
> Hi @all,
>
> I have a small problem with my module test using spec_puppet. I use the
> Puppetlabs MySQL module to create databases in my module. When running "rake
> spec" my coverage report that not all resources are tested:
>
> <--- snip --->
Things can be so easy:
Total resources: 56
Touched resources: 56
Resource coverage: 100.00%
Thanks a lot!
Regards Thomas
2016-02-16 15:28 GMT+01:00 Gareth Rushgrove :
> On 16 February 2016 at 09:37, Thomas Bendler
> wrote:
> > Hi @all,
> >
> > I have a small problem with my module test us
We are running puppetserver 1.1.3 under Ubuntu Trusty. It is apparent that
we have a memory leak of some sort. Tuning guide claims ~512M of ram per
instance, we are running with max-active-instances: 8, and I have gone from
xmx5G to xmx12G yet the memory graph continues to look like
this: htt
On Tue, Feb 16, 2016 at 11:00 AM, Brett Swift wrote:
> It's the spec_prep that is failing, so even bundle exec spec won't work.
>
Just an FYI: the spec* rake tasks are controlling and setting up lower
level unit tests using "rspec-puppet"[1] while the task to run acceptance
tests with beaker-rs
Hi,
I don't really have an answer for you, but would it be a feasible
workaround for you to convert your variable lookup into a class
parameter that is looked up implicitly? This way, you can just exploit
rspec-puppet's own facilities for providing test input, and need not
perform the whole H
I am trying to install puppet server on an ec2 ubuntu instance>
--
I get: ubuntu@ip-172-31-43-240:~$ sudo apt-get install puppetserver
Reading package lists... Done Building dependency tree Reading state
information... Done
Some packages could not be installed.
There are a couple of possibilities for what could be going on. First, I
don't see any calls to `apt-get update`. After adding a new apt source
running `apt-get update` is needed for apt to find any new packages in that
repository.
The second possibility is that you have an apt-pin in place[1]. If
