Re: [foreman-users] foreman.rb Bad URI

2017-07-06 Thread Asher Schaffer
The guide you referenced is for foreman 1.3, I assume you are using a later
version of foreman? Here is the latest documentation:
https://theforeman.org/manuals/1.15/index.html#3.5.4PuppetReports

On Thu, Jul 6, 2017 at 12:35 PM, Kernel Panic 
wrote:

> Hi guys, hope you are doing well.
>
> I'm trying to configure  puppet reports using this guide:
> https://theforeman.org/manuals/1.3/index.html#3.5.4PuppetReports
> I copied the file to 
> /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb
> and the I configured the following:
>
> $foreman_url='<%= @https://servername:8443 -%>'
>
> # if CA is specified, remote Foreman host will be verified
> $foreman_ssl_ca = "<%= @/etc/puppetlabs/foreman/ssl/ca/ca.pem -%>"
> # ssl_cert and key are required if require_ssl_puppetmasters is enabled in
> Foreman
> $foreman_ssl_cert = "<%= @/etc/puppetlabs/foreman/ssl/certs/foreman.local.pem
> -%>"
> $foreman_ssl_key = "<%= 
> @/etc/puppetlabs/foreman/ssl/private_keys/foreman.local.pem
> -%>"
>
> On puppet.conf
> storeconfigs = true
> storeconfigs_backend = puppetdb
> reports = store,puppetdb,foreman
>
>
> But in the logs I get this error:
>
>  Puppet Report processor failed: Could not send report to Foreman at <%= @
> https://servername:8443 -%>/api/reports: bad URI(is not URI?): <%= @
> https://servername:8443 -%>
>
> Using:
> puppetserver version: 2.7.2
> puppet -V
> 4.10.1
>
> Can you please help me on this?
>
> Thanks
> Regards
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


[foreman-users] can no longer provision discovered hosts

2017-06-12 Thread Asher Schaffer
Running foreman 1.15.0 on Ubuntu 16.04

Currently discovered hosts are showing up fine, if I attempt to provision
one I go to the normal provision screen, enter all the info, template
resolution works correct, but as soon as I hit submit I get  the following
error: "*Host not found *Please try to update your request"

I have noticed on the logs the following error on every page but I'm not
sure if it's related.
2017-06-12T15:12:47 20482c08 [app] [I] Started GET
"/javascripts/locale/en/app.js" for 10.180.112.106 at 2017-06-12 15:12:47
-0700
2017-06-12T15:12:47 20482c08 [app] [F]
 | ActionController::RoutingError (No route matches [GET]
"/javascripts/locale/en/app.js"):
 |   lib/middleware/tagged_logging.rb:18:in `call'
 |
 |

Any thoughts on what to look into at this point, I can't find any other
errors, it has been a while since I tried to provision a discovered host,
but it was working when I was running 1.14.3

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


Re: [foreman-users] Smart Variables - are they still useful?

2017-05-31 Thread Asher Schaffer
On Wed, May 31, 2017 at 7:24 AM, Sean O'Keeffe <sokee...@redhat.com> wrote:

>
>
> On Fri, May 26, 2017 at 5:06 PM, Asher Schaffer <as...@squaretrade.com>
> wrote:
>
>> On Mon, May 22, 2017 at 5:53 AM, Tomer Brisker <tbris...@redhat.com>
>> wrote:
>>
>>> 
>>> So, what I'm wondering is:
>>> Do people actually still use smart variables at all?
>>>
>>
>> Only in limited use cases
>>
>>
>>> If so, what do you use them for?
>>>
>>
>> Global parameters that we want to define on a per environment basis
>>
>
> I guess you mean Puppet Environment and not Katello Life Cycle Environment
> ?
>

That is correct, puppet environment


>
>>
>>> Would that same use-case be possible using smart class parameters, or
>>> possibly using global parameters? If not, what is missing for that to work?
>>>
>>
>> If global parameters could have the ability to be overridden that would
>> solve our use case, or the ability to have 'environment parameters'
>>
>
> They can be overridden the priority is common_parameter => 0,
> :domain_parameter => 1, :subnet_parameter => 2, :os_parameter => 3, :
> group_parameter => 4, :host_parameter => 5 .
>

Right, but none of those maps to environment, without smart parameters we
would end up having to duplicate the same setting across multiple subnet
parameters which makes it much more likely to make a mistake.

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


[foreman-users] EC2 Security Group changes to default

2017-01-09 Thread Asher Schaffer
When creating an EC2 compute profile I am correctly given the choice of the 
security groups for the subnet.[1]

After selecting one of them and clicking submit I am only able to create 
hosts in the default sg, similarly going back to the compute profile only 
displays the default sg[2] until I change the subnet. I'm currently running 
1.14-rc3 but saw the same behavior with 1.13

Has anyone else seen this and found a solution? I'm guessing it is related 
to this ticket: http://projects.theforeman.org/issues/12042 but there is no 
information other then that security groups don't really work when VPCs are 
involved.

1. http://imgur.com/KZjvv4U
2. http://imgur.com/GQx3LWX

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.