Cobbler Missing profiles

Hi,

I am running cobbler-2.4.4-1.el6.noarch on a Centos 6 system. The last time
I used the system it worked as expected. Today, when I run cobbler sync
I get the following error:

Exception occured: <class 'cexceptions.CX'>
Exception value: 'system sp-router.mydomain.com references a missing profile
router-centos6-mini-itx-x86_64'
Exception Info:
   File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 87, in run
     rc = self._run(self)
    File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 186, in
runner
     return
self.remote.api.sync(self.options.get("verbose",False),logger=self.logger)
    File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 767, in sync
     return sync.run()
    File "/usr/lib/python2.6/site-packages/cobbler/action_sync.py", line 114, in
run
     self.tftpd.sync(self.verbose)
    File "/usr/lib/python2.6/site-packages/cobbler/modules/manage_in_tftpd.py",
line 191, in sync
     self.pxegen.write_all_system_files(x, menu_items)
    File "/usr/lib/python2.6/site-packages/cobbler/pxegen.py", line 190, in
write_all_system_files
     raise CX("system %(system)s references a missing profile %(profile)s" % {
"system" : system.name, "profile" : system.profile})

!!! TASK FAILED !!!
(dover pts3) #

If I login to the web interface, I cannot see any distros or profiles. I only
see the systems.

If I look in /var/lib/cobbler/config/distros.d, I see the distro files as
expected.  the modification times indicate that nothing has changed since Feb.

If I look in /var/lib/cobbler/config/profiles.d I also see the profiles as
expected and again mod times show nothing has changed since Feb.

The one thing that has changed, is that cobbler was upgraded since the last
use. Is there something I have to do when the system gets upgraded to allow
previously working profiles and distro file to work again?

Does anyone know how to troubleshoot and repair this problem. My Google foo
is not turning up anything useful.

Regards,

-- 
Tom			me(a)tdiehl.org		Spamtrap address	 		me123(a)tdiehl.org

[Leonid Flaks]

On 06/13/2014 09:36 AM, me(a)tdiehl.org wrote:
>  Hi,
>
>  I am running cobbler-2.4.4-1.el6.noarch on a Centos 6 system. The last time
>  I used the system it worked as expected. Today, when I run cobbler sync
>  I get the following error:
>
>  Exception occured: <class 'cexceptions.CX'>
>  Exception value: 'system sp-router.mydomain.com references a missing
>  profile router-centos6-mini-itx-x86_64'
>  Exception Info:
>     File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 87,
>  in run
>       rc = self._run(self)
>      File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 186,
>  in runner
>       return
>  self.remote.api.sync(self.options.get("verbose",False),logger=self.logger)
>      File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 767, in
>  sync
>       return sync.run()
>      File "/usr/lib/python2.6/site-packages/cobbler/action_sync.py", line
>  114, in run
>       self.tftpd.sync(self.verbose)
>      File
>  "/usr/lib/python2.6/site-packages/cobbler/modules/manage_in_tftpd.py",
>  line 191, in sync
>       self.pxegen.write_all_system_files(x, menu_items)
>      File "/usr/lib/python2.6/site-packages/cobbler/pxegen.py", line 190,
>  in write_all_system_files
>       raise CX("system %(system)s references a missing profile
>  %(profile)s" % { "system" : system.name, "profile" :
> system.profile})
>
>  !!! TASK FAILED !!!
>  (dover pts3) #
>
>  If I login to the web interface, I cannot see any distros or profiles. I
>  only
>  see the systems.
>
>  If I look in /var/lib/cobbler/config/distros.d, I see the distro files as
>  expected.  the modification times indicate that nothing has changed
>  since Feb.
>
>  If I look in /var/lib/cobbler/config/profiles.d I also see the profiles as
>  expected and again mod times show nothing has changed since Feb.
>
>  The one thing that has changed, is that cobbler was upgraded since the last
>  use. Is there something I have to do when the system gets upgraded to allow
>  previously working profiles and distro file to work again?
>
>  Does anyone know how to troubleshoot and repair this problem. My Google foo
>  is not turning up anything useful.
>
>  Regards,
>  
I suggest you try to restart cobbler daemon. It helped me in similar 
situations in the past.

HTH,

Leon

[Alan Evangelista]

On 06/13/2014 02:34 PM, Leonid Flaks wrote:
>  On 06/13/2014 09:36 AM, me(a)tdiehl.org wrote:
> > Hi,
> >
> > I am running cobbler-2.4.4-1.el6.noarch on a Centos 6 system. The 
> > last time
> > I used the system it worked as expected. Today, when I run cobbler sync
> > I get the following error:
> >
> > Exception occured: <class 'cexceptions.CX'>
> > Exception value: 'system sp-router.mydomain.com references a missing
> > profile router-centos6-mini-itx-x86_64'
> > Exception Info:
> >    File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 87,
> > in run
> >      rc = self._run(self)
> >     File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 186,
> > in runner
> >      return
> > self.remote.api.sync(self.options.get("verbose",False),logger=self.logger)
>
> >
> >     File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 767, in
> > sync
> >      return sync.run()
> >     File "/usr/lib/python2.6/site-packages/cobbler/action_sync.py", line
> > 114, in run
> >      self.tftpd.sync(self.verbose)
> >     File
> > "/usr/lib/python2.6/site-packages/cobbler/modules/manage_in_tftpd.py",
> > line 191, in sync
> >      self.pxegen.write_all_system_files(x, menu_items)
> >     File "/usr/lib/python2.6/site-packages/cobbler/pxegen.py", line 190,
> > in write_all_system_files
> >      raise CX("system %(system)s references a missing profile
> > %(profile)s" % { "system" : system.name, "profile" :
> system.profile})
> >
> > !!! TASK FAILED !!!
> > (dover pts3) #
> >
> > If I login to the web interface, I cannot see any distros or profiles. I
> > only
> > see the systems.
> >
> > If I look in /var/lib/cobbler/config/distros.d, I see the distro 
> > files as
> > expected.  the modification times indicate that nothing has changed
> > since Feb.
> >
> > If I look in /var/lib/cobbler/config/profiles.d I also see the 
> > profiles as
> > expected and again mod times show nothing has changed since Feb.
> >
> > The one thing that has changed, is that cobbler was upgraded since 
> > the last
> > use. Is there something I have to do when the system gets upgraded to 
> > allow
> > previously working profiles and distro file to work again?
> >
> > Does anyone know how to troubleshoot and repair this problem. My 
> > Google foo
> > is not turning up anything useful.
> >
> > Regards,
> >
>  I suggest you try to restart cobbler daemon. It helped me in similar 
>  situations in the past. 

I'd check if the referenced profile's JSON file exists in 
/var/lib/cobbler/config/profiles.d/ .
If it is there, restarting cobbler daemon should work as mentioned. If 
not, you'll
need to recreate it (via Cobbler web UI, XML-RPC interface or manually 
creating a JSON file
+ restarting cobbler daemon).


Regards,
Alan Evangelista

Hi,

On Fri, 13 Jun 2014, Alan Evangelista wrote:

>  On 06/13/2014 02:34 PM, Leonid Flaks wrote:
> >  On 06/13/2014 09:36 AM, me(a)tdiehl.org wrote:
> > >  Hi,
> > > 
> > >  I am running cobbler-2.4.4-1.el6.noarch on a Centos 6 system. The last 
> > >  time
> > >  I used the system it worked as expected. Today, when I run cobbler sync
> > >  I get the following error:
> > > 
> > >  Exception occured: <class 'cexceptions.CX'>
> > >  Exception value: 'system sp-router.mydomain.com references a missing
> > >  profile router-centos6-mini-itx-x86_64'
> > >  Exception Info:
> > >     File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line
> 87,
> > >  in run
> > >      rc = self._run(self)
> > >      File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line
> 186,
> > >  in runner
> > >       return
> > > 
> self.remote.api.sync(self.options.get("verbose",False),logger=self.logger) 
> > > 
> > >      File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 767,
> in
> > >  sync
> > >      return sync.run()
> > >      File "/usr/lib/python2.6/site-packages/cobbler/action_sync.py",
> line
> > >  114, in run
> > >      self.tftpd.sync(self.verbose)
> > >      File
> > > 
> "/usr/lib/python2.6/site-packages/cobbler/modules/manage_in_tftpd.py",
> > >  line 191, in sync
> > >      self.pxegen.write_all_system_files(x, menu_items)
> > >      File "/usr/lib/python2.6/site-packages/cobbler/pxegen.py", line
> 190,
> > >  in write_all_system_files
> > >       raise CX("system %(system)s references a missing profile
> > >  %(profile)s" % { "system" : system.name, "profile" :
> system.profile})
> > > 
> > >  !!! TASK FAILED !!!
> > >  (dover pts3) #
> > > 
> > >  If I login to the web interface, I cannot see any distros or profiles. I
> > >  only
> > >  see the systems.
> > > 
> > >  If I look in /var/lib/cobbler/config/distros.d, I see the distro files 
> > >  as
> > >  expected.  the modification times indicate that nothing has changed
> > >  since Feb.
> > > 
> > >  If I look in /var/lib/cobbler/config/profiles.d I also see the profiles 
> > >  as
> > >  expected and again mod times show nothing has changed since Feb.
> > > 
> > >  The one thing that has changed, is that cobbler was upgraded since the 
> > >  last
> > >  use. Is there something I have to do when the system gets upgraded to 
> > >  allow
> > >  previously working profiles and distro file to work again?
> > > 
> > >  Does anyone know how to troubleshoot and repair this problem. My Google 
> > >  foo
> > >  is not turning up anything useful.
> > > 
> > >  Regards,
> > >
> >  I suggest you try to restart cobbler daemon. It helped me in similar
> >  situations in the past. 
I already did that AND made sure selinux is in permissive before I posted.

>  I'd check if the referenced profile's JSON file exists in 
>  /var/lib/cobbler/config/profiles.d/ . 
As I said above, the profiles are there as are the distro files, see below.

>  If it is there, restarting cobbler daemon should work as mentioned.
> If not, 
>  you'll
>  need to recreate it (via Cobbler web UI, XML-RPC interface or manually 
>  creating a JSON file 
The files are indeed there but cobbler does not see them. I could rm them and
recreate them but that just seems wrong. I have had this problem in the past
and that is how I fixed it. I would really like to avoid recreating the profiles
again, just because I did an upgrade.

(dover pts3) # ll /var/lib/cobbler/config/profiles.d
total 32
-rw-r--r--. 1 root root 966 Feb  1 16:20 c6-i386-server.json
-rw-r--r--. 1 root root 931 Feb  1 16:20 c6-x86_64-desktop.json
-rw-r--r--. 1 root root 929 Feb  1 16:20 c6-x86_64-server.json
-rw-r--r--. 1 root root 951 Feb  1 16:20 c6-x86_64-virt.json
-rw-r--r--. 1 root root 919 Feb  1 16:20 centos6-x86_64-manual.json
-rw-r--r--. 1 root root 966 Feb  1 16:20 KVM-hypervisor-centos6-x86_64.json
-rw-r--r--. 1 root root 944 Feb  1 07:38 router-centos6-mini-itx-x86_64.json
-rw-r--r--. 1 root root 957 Feb  1 16:20 server-centos6-mini-itx-x86_64.json
(dover pts3) #

(dover pts3) # ll /var/lib/cobbler/config/distros.d
total 8
-rw-r--r--. 1 root root 702 Feb  1 16:32 centos6-i386.json
-rw-r--r--. 1 root root 687 Feb  1 07:35 centos6-x86_64.json
(dover pts3) #

When I look at the cobbler web ui it shows nothing under systems or distros.
Is there a log somewhere that shows better errors?

Regards,

-- 
Tom			me(a)tdiehl.org		Spamtrap address	 		me123(a)tdiehl.org

[Alan Evangelista]

On 06/13/2014 06:31 PM, me(a)tdiehl.org wrote:
> >
> > I'd check if the referenced profile's JSON file exists in 
> > /var/lib/cobbler/config/profiles.d/ .
>
>  As I said above, the profiles are there as are the distro files, see 
>  below.
>  
Sorry, I missed that before.

>  When I look at the cobbler web ui it shows nothing under systems or 
>  distros.
>  Is there a log somewhere that shows better errors? 
/var/log/cobbler/cobbler.log

Probably the profile loading from disk failed, Cobbler usually fails 
silently when that happens.
Check if you find any errors in the log, otherwise you'll need to have 
some Python debugging skills
to understand the problem. Commenting the exception handling around 
serializer.deserialize() call in
deserialize() method in cobbler/config.py should be enough to make the 
real error pop up in the log
when cobblerd is restarted (moment when all Cobbler objects are loaded 
from disk).


Regards,
Alan Evangelista