[re-sending to the list, now that I'm subscribed]
Hi Lucas,
I recently started setting up a little autotest/cobbler install and
saw some issues with the following snippet in install_server.py:
if profile is None:
profile = self.fallback_profile
system_info = self.server.get_system(system)
current_profile = system_info.get('profile')
if profile != current_profile:
self.server.modify_system(system_handle, 'profile', profile,
self.token)
Specifically, I have one server defined in Cobbler, and no
fallback_profile defined in autotest's global_config.ini. So what would
happen is each time I tried to provision the server (which would
subsequently fail) would lead to the profile on that server being unset.
Perhaps autotest shoudn't modify the system's profile (which presumably
works as-is) *unless* there actually is a fallback_profile? Or, if not,
perhaps there should be a clear warning that fallback_profile is
required in the config (although that doesn't really make sense to me,
because it seems unlikely that a single profile is going to be sensible
in a heterogenous environment)?
Thanks,
Nish
--
Nishanth Aravamudan <[email protected]>
IBM Linux Technology Center
_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
