Description of problem: Cobbler no longer starts after updating to 2.2.2-1 Version-Release number of selected component (if applicable): cobbler-2.2.2-1.el6.noarch How reproducible: Everytime Steps to Reproduce: 1. /etc/init.d/cobblerd restart (or start) Actual results: Cobbler fails to start and I receive the following error output: Starting cobbler daemon: Traceback (most recent call last): File "/usr/bin/cobblerd", line 76, in main api = cobbler_api.BootAPI(is_cobblerd=True) File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 130, in __init__ self.deserialize() File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 873, in deserialize return self._config.deserialize() File "/usr/lib/python2.6/site-packages/cobbler/config.py", line 266, in deserialize raise CX("serializer: error loading collection %s. Check /etc/cobbler/modules.conf" % item.collection_type()) CX: 'serializer: error loading collection distro. Check /etc/cobbler/modules.conf' [ OK ] Expected results: It should start without issue as it did with the previous version of the package Additional info: Please let me know if you want any other information, thanks!
Created attachment 582821 [details] Screen-shot of relabel operation
This seems to be a selinux issue, possibly due to a conflict with a previous local policy, as a work-around run a full relabel: touch /.autorelabel reboot See attachment for actual error messages
Wiping out my selinux policy resolved the issue (as per http://forums.fedoraforum.org/showthread.php?t=248137) but is a bit of a sledgehammer approach, if someone could provide a surgical method for removing old local policy it would be appreciated.
I have SElinux disabled on this particular server so I am not sure if that is the culprit. I have reinstalled the previous version of the cobbler package and it functions correctly.
Please make sure you read the "Upgrade notes" section here: https://github.com/cobbler/cobbler/wiki/2.2.0 If it's not a SELinux issue, it is most likely an issue caused by needing to cleanup/merge a .rpmnew file in with your existing files.
After spending some time on this issue I discovered I was missing an important block of text in "/etc/cobbler/modules.conf". That block of text was: # tftpd: # chooses the TFTP management engine if manage_tftp is enabled # in /etc/cobbler/settings, which is ON by default. # # choices: # manage_in_tftpd -- default, uses the system's tftp server # manage_tftpd_py -- uses cobbler's tftp server # # for more information: # https://fedorahosted.org/cobbler/wiki/ManageTftp [tftpd] module = manage_in_tftpd Regards, Dan
FYI -- affects RHEL exact same issue occurred on a rhel 6.3 system with satellite 5.4.1 after doing weekly patches on 8/17/2012. Prior to patching all was fine, after patch cobblerd would not start with same errors in this bug. The tftpd configuration block was missing from the cobbler modules.conf file.
(In reply to comment #7) > FYI -- affects RHEL > > exact same issue occurred on a rhel 6.3 system with satellite 5.4.1 after > doing weekly patches on 8/17/2012. Prior to patching all was fine, after > patch cobblerd would not start with same errors in this bug. > > The tftpd configuration block was missing from the cobbler modules.conf file. What version of cobbler do you have on your Satellite 5.4.1? What does rpm -q cobbler output exactly?
In any case, any Satellite issue needs to be reported against the Satellite product, not in EPEL bugzilla. Restoring the NOTABUG resolution.
(In reply to comment #8) > (In reply to comment #7) > > FYI -- affects RHEL > > > > exact same issue occurred on a rhel 6.3 system with satellite 5.4.1 after > > doing weekly patches on 8/17/2012. Prior to patching all was fine, after > > patch cobblerd would not start with same errors in this bug. > > > > The tftpd configuration block was missing from the cobbler modules.conf file. > > What version of cobbler do you have on your Satellite 5.4.1? What does > > rpm -q cobbler > > output exactly? []$ rpm -q cobbler cobbler-2.2.3-2.el6.noarch []$ rpm -qi cobbler Name : cobbler Relocations: (not relocatable) Version : 2.2.3 Vendor: Fedora Project Release : 2.el6 Build Date: Sun 17 Jun 2012 09:04:57 PM EDT Install Date: Fri 17 Aug 2012 08:06:33 AM EDT Build Host: x86-01.phx2.fedoraproject.org Group : Applications/System Source RPM: cobbler-2.2.3-2.el6.src.rpm Size : 2289083 License: GPLv2+ Signature : RSA/8, Tue 19 Jun 2012 11:45:05 AM EDT, Key ID 3b49df2a0608b895 Packager : Fedora Project URL : http://cobbler.github.com/ Summary : Boot server configurator Description :
changed product to satellite
Flipping back to EPEL for search capabilities, leaving closed note that adding cobbler to the EPEL repositories disagrees with the FAQ at http://fedoraproject.org/wiki/EPEL/FAQ#Is_EPEL_commercially_supported_by_Red_Hat.3F Particularly these statments: Does EPEL replace packages provided within Red Hat Enterprise Linux or layered products? No. EPEL is purely a complementary repository that provide add-on packages. and under: How is EPEL different from other third party repositories for RHEL and derivatives? bullet "EPEL is purely a complementary add-on repository and does not replace packages in RHEL or layered products." --Doug
Technically, the satellite packages are in a different channel, so that's not a direct conflict with RHEL's standard packages. Also, they're repacking our files - something else that is against strict packaging guidelines (note the spacewalk files would conflict too, but are available in EPEL).