Open whowutwut opened 6 years ago
Hi @whowutwut , I think the orphan objects are imported to be a group is a problem, I will take a look at this.
@gurevichmark opened a ticket on this before https://github.com/xcat2/xcat-inventory/issues/85
on xcatdefaults
, there is a request from CORAL to make it to be a object , see https://github.com/xcat2/xcat-core/issues/1919
Disabled objects are not represented correctly
, currently, xcat-inventory will not ignore the disabled entries during export, so the disabled entry in nodelist for mid21tor24cn05 will not be used to compose the object yaml during export, and the criteria to determine whether the obj_type
of node object yaml is a group or node, is based on whether there is an entry in nodelist, hence it is exported as a group. will look to find any better solution for this
Is there a way to indicate that the object is disabled and it will be imported back as disabled also? There may be case where we want to use this as back up the database but also do not change the end result when imported...
will consider this, the difficulty is that the disbled table entries create a partial object, how to differentiate the disabled attribute and other attributes
Some issues seen....
I can export xcatdefaults, import and then delete
When exporting
xcat-inventory export -t node
it includesxcatdefults
which normally does not display inlsdef -t groups
After importing, I can now delete the xcatdefaults group and mypostscripts
are missing default postscriptsMany more objects are exported than are seen in lsdef
Somehow there is some meta data left around.
You can see this on boston01 ,, if you do
xcat-inventory export -t node
and compare the output with what you can see with xCAT commmands.Disabled objects are not represented correctly
I disabled this object by doing tabedit... and set 1 at the end:
But when exporting it, it shows up with
obj_type: group
instead of nodeThen when I import, it, it shows up as a group: