phantom entries about cobbler HOT 11 CLOSED

Theory is deletion of the image deleted the image without first blocking on the system.

This is likely as images were not the core of the app for a while, while this should already work as designed for profiles, etc.

In any event, it should work like profile deletion blocking works, debuglaptop is definitely a system and we don't want to leave the object store in a state with dangling links.

from cobbler.

If this helps

[root@solexa-db ~]# ls /var/lib/cobbler/config/images.d/SF2250.json
/var/lib/cobbler/config/images.d/SF2250.json
[root@solexa-db ~]# more !$
more /var/lib/cobbler/config/images.d/SF2250.json
{"comment": "", "kickstart": "", "uid": "MTMyMzIwNzM1NS43NjI5MjcxNy4xNzQ1MQ", "virt_auto_boot": 1, "virt_path": "", "file": "/var/li
b/cobbler/blob/tools_and_drivers-SW1.5.0-X2250.iso", "mtime": 1323207355.6965449, "network_count": 1, "image_type": "direct", "breed
": "redhat", "os_version": "", "virt_bridge": "xenbr0", "parent": "", "virt_type": "xenpv", "virt_file_size": 5, "arch": "i386", "ct
ime": 1323207355.6965449, "owners": ["admin"], "name": "SF2250", "virt_ram": 512, "virt_cpus": 1, "depth": 0}

from cobbler.

Can you let me know if you've got a system.d file named "debuglaptop" and if so, cat'ing that should mention the image that got deleted.

from cobbler.

Oh and I just removed the json file and did "cobbler sync" and the phantom entry still shows up

from cobbler.

You can in the short term, if that's the case, just delete the system file and things should be workable again.

from cobbler.

You'll need to restart cobblerd, as it has a copy of the state.

from cobbler.

[root@solexa-db ~]# find /var/lib/cobbler/ -name debug
[root@solexa-db ~]# ls /var/lib/cobbler/config/systems.d/
[root@solexa-db ~]#

Restarting cobblerd make the phantom go away.

from cobbler.

This happens for me on profiles and systems too. The real culprit is indeed the 'broken' caching of cobblerd, or so it seems.

from cobbler.

Can we get a set of steps to reproduce this issue? I don't quite see how caching would be the cause, since sync doesn't read from the cache and get_item() in remote only returns a cached item if it starts with '__ NEW __' (temporary caching when adding objects before they are saved).

from cobbler.

I have never seen this again since 2.4. Closing this issue. If the problem remains for someone we can re-open.

from cobbler.

AlanMcKay: Oh! Please email me! kallisti5 :at: unixzen.com

from cobbler.