Just before I saw the announcement for cobbler 2.4.0-1, I upgraded my
beta RHEL5 installation to cobbler-2.4.0-beta6.el5. I synced my master
and everything looked good. Next, I upgrade my slave and ran a
replicate:
cobbler replicate --master=$master --distros="*" --profiles="*"
--systems="*" --repos="*" --prune
The replication portion went well, but the ensuing sync failed at this
point (from cobbler.log):
Thu Jun 20 18:37:51 2013 - INFO | rendering DNS files
The exception:
rendering DNS files
Exception occured: exceptions.KeyError
Exception value: 'ipv6_address'
Exception Info:
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 89, in run
rc = self._run(self)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 188, in runner
return self.remote.api.sync(self.options.get("verbose",False),logger=self.logger)
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 767, in sync
return sync.run()
File "/usr/lib/python2.4/site-packages/cobbler/action_sync.py", line 137, in run
self.dns.write_dns_files()
File "/usr/lib/python2.4/site-packages/cobbler/modules/manage_bind.py",
line 587, in write_dns_files
self.__write_named_conf()
File "/usr/lib/python2.4/site-packages/cobbler/modules/manage_bind.py",
line 259, in write_named_conf
metadata = {'forward_zones': self.forward_zones().keys(),
File "/usr/lib/python2.4/site-packages/cobbler/modules/manage_bind.py",
line 131, in __forward_zones
ipv6 = interface["ipv6_address"]
!!! TASK FAILED !!!
The error also occurs after doing a "cobbler sync", although the
cobbler.log messages are different:
There are no errors if I change manage_dns from 1 to 0 in
/etc/cobbler/settings. The only thing I haven't done is check all my
500+ system entries for a weird ipv6_address entry (we don't use it).
Maybe this get fixed with the production 2.4.0-1 release? Thanks.
--
\*..+.-
--Greg Chavez
+//..;};
P.S. Also submitted a bug with this info.