[foreman-users] Re: Pupet-4 on provisioned hosts

[Akash Kaveti]

I have tried by adding enable-puppet-4 to host parameters. But puppet is 
not installed on the provisioned host.

On Thursday, June 29, 2017 at 1:49:41 PM UTC+2, Akash Kaveti wrote:
>
> Hello,
>
> How can I make sure that puppet- 4 is installed on the hosts that are 
> provisioned with foreman? Currently I am using 1.15.1
>
> Thanks.
>

-- 
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] Pupet-4 on provisioned hosts

[Akash Kaveti]

Hello,

How can I make sure that puppet- 4 is installed on the hosts that are 
provisioned with foreman? Currently I am using 1.15.1

Thanks.

-- 
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] Re: Puppet agent 4.x upgrade/ installation.

[Akash Kaveti]

Hi Dominic,

Puppet agent being installed, but I want the puppet version on that agent 
should be 4.x.



On Tuesday, November 15, 2016 at 5:11:35 PM UTC+1, Akash Kaveti wrote:
>
> Hello,
>
> I have foreman 1.12.3 with pupper servers puppet version 4.7.0, but with 
> my current setup, puppet agent 3.8.5 is installing.
> How do I make the new clients installations from foreman should install 
> puppet agent 4.x? 
> I have checked in puppet_setup snippet, but didnt work out.
>
>
> Thank you.
>

-- 
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] Re: Puppet agent 4.x upgrade/ installation.

[Akash Kaveti]

Apologies,
Ubuntu Xenial.

On Tuesday, November 15, 2016 at 5:11:35 PM UTC+1, Akash Kaveti wrote:
>
> Hello,
>
> I have foreman 1.12.3 with pupper servers puppet version 4.7.0, but with 
> my current setup, puppet agent 3.8.5 is installing.
> How do I make the new clients installations from foreman should install 
> puppet agent 4.x? 
> I have checked in puppet_setup snippet, but didnt work out.
>
>
> Thank you.
>

-- 
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] Puppet agent 4.x upgrade/ installation.

[Akash Kaveti]

Hello,

I have foreman 1.12.3 with pupper servers puppet version 4.7.0, but with my 
current setup, puppet agent 3.8.5 is installing.
How do I make the new clients installations from foreman should install 
puppet agent 4.x? 
I have checked in puppet_setup snippet, but didnt work out.


Thank you.

-- 
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] Re: Reports are not showing up

[Akash Kaveti]

Issue is resolved. Changing in foreman-ssl.conf file resolved the issue.

-- 
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] Re: Reports are not showing up

[Akash Kaveti]

Hi,

I have followed this comment, But of no use. still I am facing the issues.
Server-17 

I have installed libbcprov-java and changed the java.security file.

Thank you.

-- 
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] Re: Reports are not showing up

[Akash Kaveti]

Hi Michael,

Thankyou for the reply,
I was confused, bwhich method should I follow from link you have provided.
Should I change/ paste the DH parameters to my puppetserver pem file?
or should I change in foreman-ssl.conf file? 

Thanks.
On Friday, November 11, 2016 at 11:53:51 AM UTC+1, Akash Kaveti wrote:
>
> Hi All,
>
> I have followed the documentation give in foreman site, Still reports are 
> not showing up.
> My puppet.conf file
> ### File managed with puppet ###
> ## Module:   'puppet'
>
> [main]
> # Where Puppet's general dynamic and/or growing data is kept
> vardir = /opt/puppetlabs/puppet/cache
>
> # The Puppet log directory.
> # The default value is '$vardir/log'.
> logdir = /var/log/puppetlabs/puppet
>
> # Where Puppet PID files are kept.
> # The default value is '$vardir/run'.
> rundir = /var/run/puppetlabs
>
> # Where SSL certificates are kept.
> # The default value is '$confdir/ssl'.
> ssldir = /etc/puppetlabs/puppet/ssl
>
> # Allow services in the 'puppet' group to access key (Foreman + proxy)
> privatekeydir = $ssldir/private_keys { group = service }
> hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
>
> show_diff = false
> reports   = log, foreman
>
>
> ## Server config
>
> reports  = foreman
>
> environmentpath  = /etc/puppetlabs/code/environments
>   basemodulepath   = 
> /etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
>   
> hiera_config = $confdir/hiera.yaml
> ### Next part of the file is managed by a different template ###
> ## Module:   'puppet'
>
> [agent]
> # The file in which puppetd stores a list of the classes
> # associated with the retrieved configuration.  Can be loaded in
> # the separate ``puppet`` executable using the ``--loadclasses``
> # option.
> # The default value is '$statedir/classes.txt'.
> classfile = $statedir/classes.txt
>
> # Where puppetd caches the local configuration.  An
> # extension indicating the cache format is added automatically.
> # The default value is '$confdir/localconfig'.
> localconfig = $vardir/localconfig
>
> # Disable the default schedules as they cause continual skipped
> # resources to be displayed in Foreman - only for Puppet >= 3.4
> default_schedules = false
>
> report= true
> pluginsync= true
> masterport= 8140
> environment   = production
> certname  = <%= fqdn %>
> server= <%= puppet server fqdn %>
> listen= false
> splay = false
> splaylimit= 1800
> runinterval   = 1800
> noop  = false
> usecacheonfailure = true
> ### Next part of the file is managed by a different template ###
> ## Module:   'puppet'
>
> [master]
> autosign   = /etc/puppetlabs/puppet/autosign.conf { mode = 0664 }
> external_nodes = /etc/puppetlabs/puppet/node.rb
> node_terminus  = exec
> ca = true
> ssldir = /etc/puppetlabs/puppet/ssl
> certname   = <%= fqdn %>
> parser = current
> strict_variables = false
>
> my foreman.yaml file,
>
> ---
> :url: "https://foreman.bonner.cogno.loc;
> :ssl_ca: "/etc/puppetlabs/puppet/ssl/ca/ca_crt.pem"
> :ssl_cert: "/etc/puppetlabs/puppet/ssl/certs/<%= fqdn %>.pem"
> :ssl_key: "/etc/puppetlabs/puppet/ssl/private_keys/<%= fqdn %>.pem"
> :user:
> :password:
> :puppetdir: "/opt/puppetlabs/puppet/cache"
> :puppetuser: "puppet"
> :facts: true
> :timeout: 60
> :report_timeout: 60
> :threads: null
>
>
> I have foreman.rb at 
> /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb.
>
> Thank you.
>
>
>
>

-- 
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] Re: Reports are not showing up

[Akash Kaveti]

When I checked pupperserver logs, this is the error.
2016-11-14 11:58:53,352 ERROR [qtp895696639-72] [puppetserver] Puppet 
Report processor failed: Could not send report to Foreman at 
https://foreman.bonner.cogno.loc/api/config_reports: Could not generate DH 
keypair



On Friday, November 11, 2016 at 11:53:51 AM UTC+1, Akash Kaveti wrote:
>
> Hi All,
>
> I have followed the documentation give in foreman site, Still reports are 
> not showing up.
> My puppet.conf file
> ### File managed with puppet ###
> ## Module:   'puppet'
>
> [main]
> # Where Puppet's general dynamic and/or growing data is kept
> vardir = /opt/puppetlabs/puppet/cache
>
> # The Puppet log directory.
> # The default value is '$vardir/log'.
> logdir = /var/log/puppetlabs/puppet
>
> # Where Puppet PID files are kept.
> # The default value is '$vardir/run'.
> rundir = /var/run/puppetlabs
>
> # Where SSL certificates are kept.
> # The default value is '$confdir/ssl'.
> ssldir = /etc/puppetlabs/puppet/ssl
>
> # Allow services in the 'puppet' group to access key (Foreman + proxy)
> privatekeydir = $ssldir/private_keys { group = service }
> hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
>
> show_diff = false
> reports   = log, foreman
>
>
> ## Server config
>
> reports  = foreman
>
> environmentpath  = /etc/puppetlabs/code/environments
>   basemodulepath   = 
> /etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
>   
> hiera_config = $confdir/hiera.yaml
> ### Next part of the file is managed by a different template ###
> ## Module:   'puppet'
>
> [agent]
> # The file in which puppetd stores a list of the classes
> # associated with the retrieved configuration.  Can be loaded in
> # the separate ``puppet`` executable using the ``--loadclasses``
> # option.
> # The default value is '$statedir/classes.txt'.
> classfile = $statedir/classes.txt
>
> # Where puppetd caches the local configuration.  An
> # extension indicating the cache format is added automatically.
> # The default value is '$confdir/localconfig'.
> localconfig = $vardir/localconfig
>
> # Disable the default schedules as they cause continual skipped
> # resources to be displayed in Foreman - only for Puppet >= 3.4
> default_schedules = false
>
> report= true
> pluginsync= true
> masterport= 8140
> environment   = production
> certname  = <%= fqdn %>
> server= <%= puppet server fqdn %>
> listen= false
> splay = false
> splaylimit= 1800
> runinterval   = 1800
> noop  = false
> usecacheonfailure = true
> ### Next part of the file is managed by a different template ###
> ## Module:   'puppet'
>
> [master]
> autosign   = /etc/puppetlabs/puppet/autosign.conf { mode = 0664 }
> external_nodes = /etc/puppetlabs/puppet/node.rb
> node_terminus  = exec
> ca = true
> ssldir = /etc/puppetlabs/puppet/ssl
> certname   = <%= fqdn %>
> parser = current
> strict_variables = false
>
> my foreman.yaml file,
>
> ---
> :url: "https://foreman.bonner.cogno.loc;
> :ssl_ca: "/etc/puppetlabs/puppet/ssl/ca/ca_crt.pem"
> :ssl_cert: "/etc/puppetlabs/puppet/ssl/certs/<%= fqdn %>.pem"
> :ssl_key: "/etc/puppetlabs/puppet/ssl/private_keys/<%= fqdn %>.pem"
> :user:
> :password:
> :puppetdir: "/opt/puppetlabs/puppet/cache"
> :puppetuser: "puppet"
> :facts: true
> :timeout: 60
> :report_timeout: 60
> :threads: null
>
>
> I have foreman.rb at 
> /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb.
>
> Thank you.
>
>
>
>

-- 
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] Re: Reports are not showing up

[Akash Kaveti]

Hi,
My production log during the puppet agent run,

2016-11-14T11:46:40 [app] [I] Import facts for '' completed. 
Added: 0, Updated: 5, Deleted 0 facts
2016-11-14T11:46:40 [app] [I] Completed 201 Created in 105ms (Views: 1.7ms 
| ActiveRecord: 54.5ms)
2016-11-14T11:46:40 [app] [I] Started GET "/node/?format=yml" 
for 192.168.119.44 at 2016-11-14 11:46:40 +0100
2016-11-14T11:46:40 [app] [I] Processing by HostsController#externalNodes 
as YML
2016-11-14T11:46:40 [app] [I]   Parameters: {"name"=>""}
2016-11-14T11:46:40 [app] [I]   Rendered text template (0.0ms)
2016-11-14T11:46:40 [app] [I] Completed 200 OK in 72ms (Views: 0.3ms | 
ActiveRecord: 4.5ms)

Thanks.


On Friday, November 11, 2016 at 11:53:51 AM UTC+1, Akash Kaveti wrote:
>
> Hi All,
>
> I have followed the documentation give in foreman site, Still reports are 
> not showing up.
> My puppet.conf file
> ### File managed with puppet ###
> ## Module:   'puppet'
>
> [main]
> # Where Puppet's general dynamic and/or growing data is kept
> vardir = /opt/puppetlabs/puppet/cache
>
> # The Puppet log directory.
> # The default value is '$vardir/log'.
> logdir = /var/log/puppetlabs/puppet
>
> # Where Puppet PID files are kept.
> # The default value is '$vardir/run'.
> rundir = /var/run/puppetlabs
>
> # Where SSL certificates are kept.
> # The default value is '$confdir/ssl'.
> ssldir = /etc/puppetlabs/puppet/ssl
>
> # Allow services in the 'puppet' group to access key (Foreman + proxy)
> privatekeydir = $ssldir/private_keys { group = service }
> hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
>
> show_diff = false
> reports   = log, foreman
>
>
> ## Server config
>
> reports  = foreman
>
> environmentpath  = /etc/puppetlabs/code/environments
>   basemodulepath   = 
> /etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
>   
> hiera_config = $confdir/hiera.yaml
> ### Next part of the file is managed by a different template ###
> ## Module:   'puppet'
>
> [agent]
> # The file in which puppetd stores a list of the classes
> # associated with the retrieved configuration.  Can be loaded in
> # the separate ``puppet`` executable using the ``--loadclasses``
> # option.
> # The default value is '$statedir/classes.txt'.
> classfile = $statedir/classes.txt
>
> # Where puppetd caches the local configuration.  An
> # extension indicating the cache format is added automatically.
> # The default value is '$confdir/localconfig'.
> localconfig = $vardir/localconfig
>
> # Disable the default schedules as they cause continual skipped
> # resources to be displayed in Foreman - only for Puppet >= 3.4
> default_schedules = false
>
> report= true
> pluginsync= true
> masterport= 8140
> environment   = production
> certname  = <%= fqdn %>
> server= <%= puppet server fqdn %>
> listen= false
> splay = false
> splaylimit= 1800
> runinterval   = 1800
> noop  = false
> usecacheonfailure = true
> ### Next part of the file is managed by a different template ###
> ## Module:   'puppet'
>
> [master]
> autosign   = /etc/puppetlabs/puppet/autosign.conf { mode = 0664 }
> external_nodes = /etc/puppetlabs/puppet/node.rb
> node_terminus  = exec
> ca = true
> ssldir = /etc/puppetlabs/puppet/ssl
> certname   = <%= fqdn %>
> parser = current
> strict_variables = false
>
> my foreman.yaml file,
>
> ---
> :url: " <https://foreman.bonner.cogno.loc>"
> :ssl_ca: "/etc/puppetlabs/puppet/ssl/ca/ca_crt.pem"
> :ssl_cert: "/etc/puppetlabs/puppet/ssl/certs/<%= fqdn %>.pem"
> :ssl_key: "/etc/puppetlabs/puppet/ssl/private_keys/<%= fqdn %>.pem"
> :user:
> :password:
> :puppetdir: "/opt/puppetlabs/puppet/cache"
> :puppetuser: "puppet"
> :facts: true
> :timeout: 60
> :report_timeout: 60
> :threads: null
>
>
> I have foreman.rb at 
> /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb.
>
> Thank you.
>
>
>
>

-- 
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] Reports are not showing up

[Akash Kaveti]

Hi All,

I have followed the documentation give in foreman site, Still reports are 
not showing up.
My puppet.conf file
### File managed with puppet ###
## Module:   'puppet'

[main]
# Where Puppet's general dynamic and/or growing data is kept
vardir = /opt/puppetlabs/puppet/cache

# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppetlabs/puppet

# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppetlabs

# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = /etc/puppetlabs/puppet/ssl

# Allow services in the 'puppet' group to access key (Foreman + proxy)
privatekeydir = $ssldir/private_keys { group = service }
hostprivkey = $privatekeydir/$certname.pem { mode = 640 }

show_diff = false
reports   = log, foreman


## Server config

reports  = foreman

environmentpath  = /etc/puppetlabs/code/environments
  basemodulepath   = 
/etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
  
hiera_config = $confdir/hiera.yaml
### Next part of the file is managed by a different template ###
## Module:   'puppet'

[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuration.  Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is '$statedir/classes.txt'.
classfile = $statedir/classes.txt

# Where puppetd caches the local configuration.  An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig

# Disable the default schedules as they cause continual skipped
# resources to be displayed in Foreman - only for Puppet >= 3.4
default_schedules = false

report= true
pluginsync= true
masterport= 8140
environment   = production
certname  = <%= fqdn %>
server= <%= puppet server fqdn %>
listen= false
splay = false
splaylimit= 1800
runinterval   = 1800
noop  = false
usecacheonfailure = true
### Next part of the file is managed by a different template ###
## Module:   'puppet'

[master]
autosign   = /etc/puppetlabs/puppet/autosign.conf { mode = 0664 }
external_nodes = /etc/puppetlabs/puppet/node.rb
node_terminus  = exec
ca = true
ssldir = /etc/puppetlabs/puppet/ssl
certname   = <%= fqdn %>
parser = current
strict_variables = false

my foreman.yaml file,

---
:url: "https://foreman.bonner.cogno.loc;
:ssl_ca: "/etc/puppetlabs/puppet/ssl/ca/ca_crt.pem"
:ssl_cert: "/etc/puppetlabs/puppet/ssl/certs/<%= fqdn %>.pem"
:ssl_key: "/etc/puppetlabs/puppet/ssl/private_keys/<%= fqdn %>.pem"
:user:
:password:
:puppetdir: "/opt/puppetlabs/puppet/cache"
:puppetuser: "puppet"
:facts: true
:timeout: 60
:report_timeout: 60
:threads: null


I have foreman.rb at 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb.

Thank you.



-- 
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] Re: Unable to fetch my node definition, but the agent run will continue

[Akash Kaveti]

Figured out the error. I made some mistake in foreman.yaml file.

On Thursday, November 10, 2016 at 5:22:25 PM UTC+1, Akash Kaveti wrote:
>
> Hi,
>
> i am facing this issue, when ever I run puppet in agent.
>
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
> {"message":"Server Error: Could not find node 'host.mydomain.com'; cannot 
> compile","issue_kind":"RUNTIME_ERROR","stacktrace":["/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:336:in
>  
> `node_from_request'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:50:in
>  
> `find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in
>  
> `find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:121:in
>  
> `do_find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in
>  
> `call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in 
> `override'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in 
> `override'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
>  
> `call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in
>  
> `process'","org/jruby/RubyArray.java:1613:in 
> `each'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in
>  
> `process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
>  
> `process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
>  
> `process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
>  
> `process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
>  
> `profile'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in
>  
> `profile'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in
>  
> `process'","file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
>  
> `handleRequest'","Puppet$$Server$$Master_1033412677.gen:13:in 
> `handleRequest'","request_handler_core.clj:273:in 
> `invoke'","jruby_request.clj:46:in `invoke'","jruby_request.clj:31:in 
> `invoke'","request_handler_service.clj:34:in 
> `handle_request'","request_handler.clj:3:in 
> `invoke'","request_handler.clj:3:in `invoke'","core.clj:2493:in 
> `invoke'","master_core.clj:428:in `invoke'","ring.clj:21:in 
> `invoke'","ring.clj:12:in `invoke'","comidi.clj:249:in 
> `invoke'","ring_middleware.clj:284:in `invoke'","core.clj:168:in 
> `invoke'","core.clj:211:in `invoke'","core.clj:45:in 
> `invoke'","core.clj:343:in `invoke'","core.clj:51:in 
> `invoke'","ringutils.clj:86:in `invoke'","legacy_routes_core.clj:114:in 
> `invoke'","legacy_routes_core.clj:94:in 
> `invoke'","legacy_routes_core.clj:184:in 
> `invoke'","legacy_routes_core.clj:151:in `invoke'","ring.clj:21:in 
> `invoke'","ring.clj:12:in `invoke'","comidi.clj:249:in 
> `invoke'","jetty9_core.clj:424:in 
> `invoke'","normalized_uri_helpers.clj:80:in `invoke'"]}
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
> my production log, while running puppet agent is,
>
> 2016-11-10T07:15:34 [app] [I] Started POST "/api/hosts/facts" for 
> 192.168.119.44 at 2016-11-10 07:15:34 +0100
> 2016-11-10T07:15:34 [app] [I] Processing by Api::V2::HostsController#facts 
> as JSON
> 2016-11-10T07:15:34 [app] [I]   Parameters: {"facts"=>"[FILTERED]", 
> "name"=>"host.mydomain.com", "certname"=>"host.mydomain.com", 
> "apiv"=>"v2", :host=>{"name"=>"host.mydomain.com", "certname"=>"
> host.mydomain.com"}}
> 2016-11-10T07:15:34 [app] [I] Import facts for 'host.mydomain.com' 
> completed. Added: 0, Updated: 5, Deleted 0 facts
> 2016-11-10T07:15:34 [app] [I] Completed 201 Created in 96ms (Views: 1.6ms 
> | ActiveRecord: 45.4ms)
> 2016-11-10T07:15:34 [app] [I] Started GET "/node/
> host.mydomain.com?format=yml" for 192.168.119.44 at 2016-11-10 07:15:34 
> +0100
> 2016-11-10T07:15:34 [app] [I] Processing by HostsController#externalNodes 
> as YML
> 2016-11-10T07:15:34 [app] [I]   Parameters: {"name"=>"host.mydomain.com"}
> 2016-11-10T07:15:34 [app] [I]   Rendered text template (0.0ms)
> 2016-11-10T07:15:34 [app] [I] Completed 200 OK in 68ms (Views: 0.2ms | 
> ActiveRecord: 4.5ms)
>
> THANKS
>
>

-- 
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] Unable to fetch my node definition, but the agent run will continue

[Akash Kaveti]

Hi,

i am facing this issue, when ever I run puppet in agent.

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
{"message":"Server Error: Could not find node 'host.mydomain.com'; cannot 
compile","issue_kind":"RUNTIME_ERROR","stacktrace":["/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:336:in
 
`node_from_request'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:50:in
 
`find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in
 
`find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:121:in
 
`do_find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in
 
`call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in 
`override'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in 
`override'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
 
`call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in
 
`process'","org/jruby/RubyArray.java:1613:in 
`each'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in
 
`process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
 
`process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
 
`process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
 
`process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
 
`profile'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in
 
`profile'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in
 
`process'","file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
 
`handleRequest'","Puppet$$Server$$Master_1033412677.gen:13:in 
`handleRequest'","request_handler_core.clj:273:in 
`invoke'","jruby_request.clj:46:in `invoke'","jruby_request.clj:31:in 
`invoke'","request_handler_service.clj:34:in 
`handle_request'","request_handler.clj:3:in 
`invoke'","request_handler.clj:3:in `invoke'","core.clj:2493:in 
`invoke'","master_core.clj:428:in `invoke'","ring.clj:21:in 
`invoke'","ring.clj:12:in `invoke'","comidi.clj:249:in 
`invoke'","ring_middleware.clj:284:in `invoke'","core.clj:168:in 
`invoke'","core.clj:211:in `invoke'","core.clj:45:in 
`invoke'","core.clj:343:in `invoke'","core.clj:51:in 
`invoke'","ringutils.clj:86:in `invoke'","legacy_routes_core.clj:114:in 
`invoke'","legacy_routes_core.clj:94:in 
`invoke'","legacy_routes_core.clj:184:in 
`invoke'","legacy_routes_core.clj:151:in `invoke'","ring.clj:21:in 
`invoke'","ring.clj:12:in `invoke'","comidi.clj:249:in 
`invoke'","jetty9_core.clj:424:in 
`invoke'","normalized_uri_helpers.clj:80:in `invoke'"]}
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

my production log, while running puppet agent is,

2016-11-10T07:15:34 [app] [I] Started POST "/api/hosts/facts" for 
192.168.119.44 at 2016-11-10 07:15:34 +0100
2016-11-10T07:15:34 [app] [I] Processing by Api::V2::HostsController#facts 
as JSON
2016-11-10T07:15:34 [app] [I]   Parameters: {"facts"=>"[FILTERED]", 
"name"=>"host.mydomain.com", "certname"=>"host.mydomain.com", "apiv"=>"v2", 
:host=>{"name"=>"host.mydomain.com", "certname"=>"host.mydomain.com"}}
2016-11-10T07:15:34 [app] [I] Import facts for 'host.mydomain.com' 
completed. Added: 0, Updated: 5, Deleted 0 facts
2016-11-10T07:15:34 [app] [I] Completed 201 Created in 96ms (Views: 1.6ms | 
ActiveRecord: 45.4ms)
2016-11-10T07:15:34 [app] [I] Started GET 
"/node/host.mydomain.com?format=yml" for 192.168.119.44 at 2016-11-10 
07:15:34 +0100
2016-11-10T07:15:34 [app] [I] Processing by HostsController#externalNodes 
as YML
2016-11-10T07:15:34 [app] [I]   Parameters: {"name"=>"host.mydomain.com"}
2016-11-10T07:15:34 [app] [I]   Rendered text template (0.0ms)
2016-11-10T07:15:34 [app] [I] Completed 200 OK in 68ms (Views: 0.2ms | 
ActiveRecord: 4.5ms)

THANKS

-- 
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] Re: "No root file system is defined" error using preseed atomic partitioning scheme

[Akash Kaveti]

Hey Hauke,

I am using Preseed default template for partition table, in it using Crypto 
method for my hardware encryption.
Is there any way I can give a default password for it, so that I shouldn't 
give password during the installation?

Thank you.

On Thursday, September 15, 2016 at 2:34:35 PM UTC+2, Akash Kaveti wrote:
>
> Thank you so much for the response. :)
>
> On Wednesday, September 14, 2016 at 4:40:14 PM UTC+2, Hauke Behrens wrote:
>>
>>
>>
>> On 09/14/2016 03:04 PM, Akash Kaveti wrote: 
>> > Hello Again, 
>> > 
>> > It is working now, I have check the syslog, the device I am trying to 
>> > install is not there it seems, 
>> > so I gave /dev/sdb, it is working now. 
>>
>> Glad I could help. :-) 
>>
>>
>> > It is working for the current host, but what about the other hosts, Why 
>> > cant I use "/d-i partman/early_command string debconf-set 
>> > partman-auto/disk "$(list-devices disk | head -n1)/" 
>>
>> It's always hard to guess what device is getting used. 
>> If you have a usb-stick plugged-in with the e.g. a formean-boot-iso, 
>> that might be /dev/sda and your "real" hard-disk might be /dev/sdb/. 
>>
>> In that case "head -n2" will do the trick. 
>> When using raid-devices this might be different too. 
>>
>> Also check out this thread: 
>>
>> https://groups.google.com/forum/#!topic/foreman-users/uKuY4YJuy7E 
>>
>> Hauke 
>>
>> -- 
>> bytemine GmbH, Im Technologiepark 4, 26129 Oldenburg 
>> Support: 0441-309197-42 --- Vertrieb: 0441-309197-69 
>> GF: Felix Kronlage -- AG in Oldenburg -- HRB 203 940 
>> https://www.bytemine.net --- VAT-Number: DE267286778 
>>
>

-- 
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] Puppet agent --test throwing error on cleint installed through foreman

[Akash Kaveti]

Hi,

I have installed Ubuntu 16.04 on client system using foreman, when I run 
puppet agent --test on it is throwing an error.




*"Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional 
resources using 'eval_generate': Failed to open TCP connection to 
mydomain.com:8140 (getaddrinfo: Name or service not known)"Thanks.*

-- 
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] Ubuntu Desktop-Unattended installation

[Akash Kaveti]

Thank you Dominic, That worked.

On Thursday, September 15, 2016 at 2:38:11 PM UTC+2, Dominic Cleal wrote:
>
> On 15/09/16 13:11, Akash Kaveti wrote: 
> > Hello, 
> > 
> > I am trying to install ubuntu desktop, but I have succeeded. I have 
> > tried different mirrors but I ended up with Ubuntu server. 
> > Would be very much greatful, if any one can help. 
>
> Try updating the package list (via tasksel) in the preseed file, i.e. 
> the line at 
>
> https://github.com/theforeman/community-templates/blob/develop/preseed/provision.erb#L132.
>  
>
> Edit your preseed via Foreman's provisioning templates UI. 
>
> See 
>
> https://help.ubuntu.com/lts/installation-guide/amd64/apbs04.html#preseed-pkgsel
>  
> for a list of standard tasks. 
>
> -- 
> Dominic Cleal 
> dom...@cleal.org  
>

-- 
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] Re: "No root file system is defined" error using preseed atomic partitioning scheme

[Akash Kaveti]

Thank you so much for the response. :)

On Wednesday, September 14, 2016 at 4:40:14 PM UTC+2, Hauke Behrens wrote:
>
>
>
> On 09/14/2016 03:04 PM, Akash Kaveti wrote: 
> > Hello Again, 
> > 
> > It is working now, I have check the syslog, the device I am trying to 
> > install is not there it seems, 
> > so I gave /dev/sdb, it is working now. 
>
> Glad I could help. :-) 
>
>
> > It is working for the current host, but what about the other hosts, Why 
> > cant I use "/d-i partman/early_command string debconf-set 
> > partman-auto/disk "$(list-devices disk | head -n1)/" 
>
> It's always hard to guess what device is getting used. 
> If you have a usb-stick plugged-in with the e.g. a formean-boot-iso, 
> that might be /dev/sda and your "real" hard-disk might be /dev/sdb/. 
>
> In that case "head -n2" will do the trick. 
> When using raid-devices this might be different too. 
>
> Also check out this thread: 
>
> https://groups.google.com/forum/#!topic/foreman-users/uKuY4YJuy7E 
>
> Hauke 
>
> -- 
> bytemine GmbH, Im Technologiepark 4, 26129 Oldenburg 
> Support: 0441-309197-42 --- Vertrieb: 0441-309197-69 
> GF: Felix Kronlage -- AG in Oldenburg -- HRB 203 940 
> https://www.bytemine.net --- VAT-Number: DE267286778 
>

-- 
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] Ubuntu Desktop-Unattended installation

[Akash Kaveti]

Hello,

I am trying to install ubuntu desktop, but I have succeeded. I have tried 
different mirrors but I ended up with Ubuntu server.
Would be very much greatful, if any one can help.

Thank you.

-- 
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] Re: "No root file system is defined" error using preseed atomic partitioning scheme

[Akash Kaveti]

Hello Again,

It is working now, I have check the syslog, the device I am trying to 
install is not there it seems,
so I gave /dev/sdb, it is working now.

I am trying to install ubuntu by unattended installation on a hardware box.
I am using the default the partition template, I am not using LVM.
 
It is working for the current host, but what about the other hosts, Why 
cant I use "*d-i partman/early_command string debconf-set partman-auto/disk 
"$(list-devices disk | head -n1)*"

Thank you for the help, i have been struggling with this error from 
yesterday.

On Wednesday, September 14, 2016 at 1:52:33 PM UTC+2, Hauke Behrens wrote:
>
> Hi, 
>
> what kind of system are you trying to install to ? 
> KVM/Libvirt, a hardware box, something else ? 
> Are you maybe using LVM to provide the virtual disk ? 
>
> Please provide some more information on what you are trying to install 
> to. Maybe that will help to find the error. 
>
> I've also seen that error before, and in my cases it always was: 
> "trying to install to a wrong disk or "trying to install to non- 
> existant device". 
>
> One thing you can try is to switch to a different console 
> (ctrl+alt+f1,f2 etc.) during the install and checking syslog, to see 
> what commands are issued. 
> Check if the device really exists on the system or try another recipe. 
>
> Hauke 
>
>
>
>

-- 
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] Re: "No root file system is defined" error using preseed atomic partitioning scheme

[Akash Kaveti]

Hi,

Thanks for the response, I have tried to install on different server as 
well, but got the same error,
Below I am pasting my partition template,



# Use the first detected hard disk as default installation disk
#d-i partman/early_command string debconf-set partman-auto/disk 
"$(list-devices disk | head -n1)"
d-i partman-auto/disk string dev/sda

### Partitioning
# The presently available methods are: "regular", "lvm" and "crypto"
d-i partman-auto/method string crypto

# If one of the disks that are going to be automatically partitioned
# contains an old LVM configuration, the user will normally receive a
# warning. This can be preseeded away...
d-i partman-lvm/device_remove_lvm boolean true
# The same applies to pre-existing software RAID array:
d-i partman-md/device_remove_md boolean true
# And the same goes for the confirmation to write the lvm partitions.
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true


# You can choose one of the three predefined partitioning recipes:
# - atomic: all files in one partition
# - home:   separate /home partition
# - multi:  separate /home, /var, and /tmp partitions (/usr was removed in 
jessie)
d-i partman-auto/choose_recipe select atomic


# If you just want to change the default filesystem to something
# else, you can do that without providing a full recipe.

# This makes partman automatically partition without confirmation, provided
# that you told it what to do using one of the methods above.
d-i partman/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true

Thank you.


On Tuesday, September 13, 2016 at 4:49:42 PM UTC+2, Akash Kaveti wrote:
>
> I am using preseed default as partitioning template, but when a host is 
> launched using that I got this error "No root file system is defined"
>

-- 
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] Re: "No root file system is defined" error using preseed atomic partitioning scheme

[Akash Kaveti]

Exact error message is, No root file system is defined, Please correct this 
form partitioning menu. 
I have installed foreman with DHCP in a network, where I have disabled the 
existing DHCP in that Network. 

On Tuesday, September 13, 2016 at 4:49:42 PM UTC+2, Akash Kaveti wrote:
>
> I am using preseed default as partitioning template, but when a host is 
> launched using that I got this error "No root file system is defined"
>

-- 
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.