Displaying 20 results from an estimated 20000 matches similar to: "Puppet without FQDN (could not retrieve fact fqdn)"
2013 Mar 23
1
warning: Could not retrieve fact fqdn
Hi;
After applying this pp i get this error.
*file {''/tmp/test1'':*
* ensure => present,*
* content => "Hi.",*
* }*
*
*
* file {''/tmp/test2'':*
* ensure => directory,*
* mode => 0644,*
* }*
*
*
* file {''/tmp/test3'':*
* ensure => link,*
* target =>
2009 Feb 12
2
"Could not find server puppet" - installation/configuration error
Started the discussion in puppet users mailing list based on
recommendation from luke. This discussion is to a follow up regarding
bug#1955 "Could not find server puppet" - installation/configuration
error".
jamtur01''s last recommendation:
Rather than renaming things try the certname option (see
http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference).
But
2010 Feb 14
2
How can I set certname in managed puppet.conf?
I want to manage my puppet.conf files on every node, via a puppet
module on the puppetmaster.
However, in puppet.conf on each of my nodes, I also *must* specify the
certname attribute.
(This is because my company''s NIS domain doesn''t match it''s DNS domain
and the fqdn comes out erroneous unless I enforce the DNS name with
the certname attribute.)
Does anyone know how
2008 Apr 11
2
Fake FQDN for puppetmaster (and ca) in faked environment?
Hi there,
We have a fake environment in which we test software and config before
rolling it out to prod. Here, we have a fake puppetmasterd running,
serving the new config under test.
But we''re having trouble with certificates. It is possible to specify
via config what fqdn the puppet ca should use for itself? We need this
to be a different (faked) fqdn than the real name of the
2013 Jan 22
6
Security considerations for basing decisions on facts
Hello,
Let''s consider the scenario when a client node in a puppet environment
gets compromised.
In case some of the puppet modules make decisions based on agent facts,
these modules are potentially exposed to abuse from the malicious puppet
agent.
For example, if a class has:
if $some_fact == ''some value'' {
# deploy some configuration
}
then the compromised node
2012 Oct 26
2
Using regex to match hostnames in hiera
Hi, I''m having a problem with extlookup not respecting the ''certname'' parameter[1]. When executing a puppet run with either the --certname or --fqdn parameters, it ends up using the specified SSL certificate and gets the correct node definition applied from the puppetmaster. However, it still retrieves extlookup data using the node''s actual FQDN, not the one
2012 Nov 05
6
err: Could not request certificate when I run "puppet device"
1. I get the following error when I run “puppet device’
err: Could not request certificate: Could not write
/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to
privatekeydir: Permission denied -
/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem
Any thought?
Thanks,
--
You received this message because you are subscribed to the Google Groups
2011 Jun 30
7
Puppet agent creates certificates for localhost.localdomain and does not pick up the changed hostname
Hi Everyone,
I am using Puppet 2.6.5 to configure fresh VMs. These VMs have their
hostname set to localhost.localdomain initially at boot-time.
There is this script file that runs in rc.local and this is what I do
inside it
1. I change the hostname from localhost to xxx.xxxxxx using the
hostname command.
2. start the puppet agent as /usr/sbin/puppetd --certname=xxx.xxxxxx
2008 Jun 14
9
Disabling 'node_name = facter' setting
I''m having a heck of a time trying to fix #1178, which is a problem
related to inconsistent node names, and it all stems from the
''node_name'' setting.
In the default setup, your certificate gets created with your host''s
fully qualified node name, and Puppet uses the value from the
certificate for everything.
In addition, there''s a setting,
2013 Jun 19
1
puppet 3.1.1 - wrong domain and fqdn in facter.
Hi All.
I am using:
#rpm -qa | egrep ''puppet|facter''
puppetlabs-release-6-7.noarch
puppet-3.1.1-1.el6.noarch
facter-1.7.1-1.el6.x86_64
on:
#cat /etc/redhat-release ; uname -r
CentOS release 6.4 (Final)
2.6.32-358.11.1.el6.centos.plus.x86_64
My hostname is server.one.two.com:
# hostname
server.one.two.com
# hostname --fqdn
one.two.com
#grep HOSTNAME /etc/sysconfig/network
2012 Jul 11
6
certname doesn't seem to work on the agent
Hi guys,
I have a box that needs to identify itself to the puppetmaster as something
different from the FQDN. I added certname to the agent configuration before
the first run, but it doesn''t seem to be sufficient. The certificate was
generated for the FQDN, and the host appears in the dashboard as the FQDN,
and the node name used to evaluate the manifest is also the FQDN. I would
2008 Oct 14
2
Certificate validation failing
I am trying to use puppet to configure Amazon EC2 instances. The
server is my own box at home. Both server and clients are Ubuntu 8.04
running puppet 0.24.5.
On the client when I run:
puppetd --server myserver.com --waitforcert 60 --test
I get a cert to sign on the server. I sign it and run the command
above again on the client. But then I get 3 errors similar to this:
warning: Certificate
2010 Nov 07
14
EC2 with puppet bootstrap notes and scripts
Hello...
I wanted to be able to startup an EC2 instance with one command and
have a fully functioning server without having to shell into each new
instance and configure the bits to allow puppet to finish the
configuration. Here are some notes I came up with for bootstrapping an
ec2 instance with puppet using Ubuntu 10.04. I left out a lot of things
about creating and running custom AIM
2010 Dec 01
4
problem booting (Fedora) LiveCD ISO over PXELINUX
This is an issue I've researched quite a bit on bug lists, and looked
in the Syslinux Wiki for a way to do this, but haven't yet found a
solution.
1) I have an existing Fedora 13 LiveCD which I burned to a CD and
tested on a system without issue.
2) I then took that same ISO and dropped it in my pxelinux.cfg/default
for being able to boot over the network. I made sure to extract the
2010 May 05
2
Puppet with cloud instances
Hello all,
Recently I was asked to start using Puppet as part of our Eucalyptus
powered internal cloud. I have been able to set up Puppet and a
puppet master on various instances, but what I am running into, is
that several of the instances have the same hostname or no hostname
when they are first launched, so of course when they try to get a cert
from puppetmaster I get an error saying that I
2007 Nov 29
2
puppet:// URIs don''t allow FQDN?
Hi List,
I''m using puppet 0.23.2 (tarball) on Debian sarge as server and the same
version on an etch client. When I try to use the following class :
class base {
$puppet = "security01.mydomain.com"
# bashrc file for global shell settings. file depends on used OS
version (etch, sarge etc).
file {
"/etc/bash.bashrc":
ensure =>
2011 Oct 19
5
How to know the generated certname used by a puppet client, for reuse within erb (because of cloud provisioner) ?
Hi,
I am using the cloud provisioner to bootstrap some ec2 nodes, and these
clients are signed using a randomly generated certname, which is put in
/etc/puppet.conf at the bootstrap time (eg certname =
d7bcd693-73fd-495f-0876-ff91ea11111e).
But my puppet code repo also manages the puppet.conf file, so the file will
be overwritten on the client at the first puppet run. Nevertheless, i should
not
2011 Nov 04
1
Storeconfigs and nagios and foreman
All-
Poking around in the bug database it looks like storeconfigs is being
actively worked on. I am using 2.7.6 on my master as well as all the
clients. I have clients boot , start puppet and get a signed cert via
auto signing. The nagios module (and currently the only thing puppet
does) complains a lot during compile time about not having
storeconfigs enabled, which is not the case in my
2010 Oct 15
5
alternate hostnames, keys, and certs
I''d like to extend my use of puppet to manage my desktop/notebook macs.
As others have noted, the hostname of the mobile machines tends to change frequently, so basing the node name (in my site.pp) and the corresponding cert and private key names seems to be an issue.
I seem to recall somewhat talking about this at Puppet Camp last week…..
Generally my signing strategy is always to
2012 Nov 28
3
Could not retrieve information from environment production source
I''m using puppet 3.0
i install puppet by these two command:
sudo rpm -i
http://yum.puppetlabs.com/el/5/products/i386/puppetlabs-release-5-6.noarch.rpm
sudo yum install puppet-server
as
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-red-hat-enterprise-linux-and-derivatives
and