On 08/10/2009 12:19 PM, James Cammarata wrote:
I am trying to create sub-profiles, and ran into this error:
# cobbler profile add --name=rhel4.6-i386-vm --inherit=rhel4.6-i386
--in-place --ksmeta=is_vm=1
object does not support item assignment
File "/usr/lib/python2.4/site-packages/cobbler/cobbler.py", line 83, in
main
rc = BootCLI().run(sys.argv)
File "/usr/lib/python2.4/site-packages/cobbler/cobbler.py", line 61, in
run
return self.loader.run(args)
File "/usr/lib/python2.4/site-packages/cobbler/commands.py", line 122, in
run
return fn.run()
File "/usr/lib/python2.4/site-packages/cobbler/modules/cli_profile.py",
line 135, in run
obj.set_ksmeta(self.options.ksmeta,self.options.inplace)
File "/usr/lib/python2.4/site-packages/cobbler/item.py", line 193, in
set_ksmeta
self.ks_meta[key] = value[key]
In my environment, VMware based hosts get much less disk space so we have
special partitioning snippets for them. If I take off the --ksmeta
assignment, the add works fine, so it looks like you can't modify the
ksmeta while doing a subprofile creation.
Is this a bug, or expected behavior?
Any traceback going to console instead of a friendly message is /always/
a bug.
Does this happen on master? If not, the release is coming out this month
(most likely) in which case, we should be fine.
(A ton of that code is rewritten on master)