Hello all,
I am not positive that this happened in concurrence with my upgrading cobbler to 2.2.1 from the el5 2.0.11 version, but I haven't changed that much aside from that.
I was having problems before in that cobbler seemed to fire off the command to sign new puppet certs way too late, which I had never successfully figured out why. Now it is not ever firing that task.
Now, however, cobbler is not removing old certs either. I have the following puppet related settings in my /etc/cobbler/settings file, and cobbler sync doesn't generate any warnings.
puppet_auto_setup: 1 sign_puppet_certs_automatically: 1 puppetca_path: "/usr/sbin/puppetca" remove_old_puppet_certs_automatically: 1
my puppet master is on the same machine as my cobbler server. I don't see anything in the logs after december 16th indicating that cobbler has kicked off the puppetca tasks:
Fri Dec 16 15:35:09 2011 - INFO | running: ['/usr/sbin/puppetca', '--clean', 'XXXX'] Fri Dec 16 16:14:07 2011 - INFO | running: ['/usr/sbin/puppetca', '--sign', 'XXXX']
New machines brought online get their puppet cert added to the puppet master.
Any ideas where to look into this further? The only change I have made to the puppet_register_if_enabled snippet is that I have the snippet load the correct auth.conf and puppet.conf files. Reverting that change makes no difference in the cobbler->puppet interactions.
Thanks,
Jim Goddard
-----Original Message----- From: cobbler-bounces@lists.fedorahosted.org on behalf of cobbler-request@lists.fedorahosted.org Sent: Fri 1/6/2012 4:00 AM To: cobbler@lists.fedorahosted.org Subject: cobbler Digest, Vol 43, Issue 3
Send cobbler mailing list submissions to cobbler@lists.fedorahosted.org
To subscribe or unsubscribe via the World Wide Web, visit https://fedorahosted.org/mailman/listinfo/cobbler or, via email, send a message with subject or body 'help' to cobbler-request@lists.fedorahosted.org
You can reach the person managing the list at cobbler-owner@lists.fedorahosted.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of cobbler digest..."
Today's Topics:
1. cobbler 2.2 and empty subnet (Christian Horn) 2. Re: How does one set up dnsmasq/DHCP to play nice with Windows DNS/DHCP (Ger Apeldoorn) 3. Re: How does one set up dnsmasq/DHCP to play nice with Windows DNS/DHCP (David Lee)
----------------------------------------------------------------------
Message: 1 Date: Thu, 5 Jan 2012 15:15:30 +0100 From: Christian Horn chorn@fluxcoil.net To: cobbler mailing list cobbler@lists.fedorahosted.org Subject: cobbler 2.2 and empty subnet Message-ID: 20120105141530.GC2540@fluxcoil.net Content-Type: text/plain; charset=us-ascii
Hi,
using a RHEL6.2 and the current cobble in epel, 2.0.11-2, a system object can be added, and is handled properly.
Using cobbler 2.2.1-1 from testing leads to this:
# cobbler system add --name=tester6 --profile=rhel6u2-x86_64 # cobbler system edit --name=tester6 --hostname=tester6 \ --interface=eth0 --ip-address=10.0.100.6 \ --subnet=255.255.255.0 --mac=00:ff:06:00:00:01 --static=1 # cobbler system dumpvars --name=tester6 |grep subnet_ subnet_eth0 : # cobbler system report --name=tester6 |grep Subnet Subnet Mask : 255.255.255.0
Dumpvars is not presenting the netmask, also not 'getks'. Performing the same steps with 2.0.11-2 everything works. Accessing system objects that were created with 2.0.11-2 after upgrade to 2.2.1-1 leads to the subnet still beeing accessable.
Any ideas on what I could possibly be missing here? Did not spot a related ticket on github yet, got aware of this from a report from another cobbler user.
cheers, Christian
------------------------------
Message: 2 Date: Fri, 06 Jan 2012 07:33:30 +0100 From: Ger Apeldoorn g.apeldoorn@fundeon.nl To: cobbler mailing list cobbler@lists.fedorahosted.org Subject: Re: How does one set up dnsmasq/DHCP to play nice with Windows DNS/DHCP Message-ID: 4F0695BA.1060900@fundeon.nl Content-Type: text/plain; charset=UTF-8; format=flowed
you should be able to run dhcpd on your own subnet w/o causing problems to any other dhcpd servers on other subnets that service you. to be safe, you can also disable any dhcp helpers on your switch ports that service you subnet.
This is only true if your network is on a seperate vlan or physical network. Multiple subnets can coexist on a single vlan, in which case you would surely cause issues on the LAN.
You could also configure a dhcp server to respond only to known macadresses.
Ger
------------------------------
Message: 3 Date: Fri, 06 Jan 2012 10:14:24 +0000 From: David Lee David.Lee@ecmwf.int To: cobbler mailing list cobbler@lists.fedorahosted.org Subject: Re: How does one set up dnsmasq/DHCP to play nice with Windows DNS/DHCP Message-ID: 4F06C980.2020604@ecmwf.int Content-Type: text/plain; charset=UTF-8; format=flowed
Ger Apeldoorn wrote:
you should be able to run dhcpd on your own subnet w/o causing problems to any other dhcpd servers on other subnets that service you. to be safe, you can also disable any dhcp helpers on your switch ports that service you subnet.
This is only true if your network is on a seperate vlan or physical network. Multiple subnets can coexist on a single vlan, in which case you would surely cause issues on the LAN.
You could also configure a dhcp server to respond only to known macadresses. [...]
For the future, we definitely need to ensure that the various aspects of this are addressed in the documentation, as both principle and example.
The documentation is moving to a wiki, much of whose content originated from the existing big man page. The main page regarding DHCP is: https://github.com/cobbler/cobbler/wiki/DHCP%20management
I don't see any mention there of the considerations raised in this thread.
Dan, Pete, and Ger (as technical contributors to the thread): If you don't wish to update the wiki yourselves, I'm happy to try to consolidate any suggestions you may make or send to me.
-- David Lee
------------------------------
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
End of cobbler Digest, Vol 43, Issue 3 **************************************
cobbler@lists.fedorahosted.org