I went though the code and I agree with you. On profile dhcp-tag is just a variable but on system it's an array, and part of the interface.
I understand what you are saying, in terms of multi interface inherit the tag, but that's a moot point. It already gets default assigned anyway, meaning on multi homed system one would have to manually assign it any way.
Thank you
----- Original Message -----
From: James Cammarata <jimi(a)sngx.net>
To: Dohojda, Marek (Hlthcr&Science)
Cc: cobbler(a)lists.fedorahosted.org <cobbler(a)lists.fedorahosted.org>
Sent: Tue Aug 31 07:44:35 2010
Subject: RE: did I just found a bug (dhcp-tag)
On Mon, 30 Aug 2010 18:17:35 -0500, <marek.dohojda(a)thomsonreuters.com>
wrote:
> Well it seems that it doesn't inherit at all. Unless there is a syntax I
> should input that I am not aware off (I tried <<inherit>>)
>
> I looked in the item_system.py and it seems to confirm what I am saying,
> i.e. that dhcp-tag doesn't inherit.
>
> What is the point, than, of profile dhcp-tag if that doesn't get
> inherited
>
> Ahm, I wonder if anybody, better than me in python, knows what I could
> put in the .py to enable inherit?
I think I see the issue - profiles don't have interfaces, but systems do.
Systems may have multiple interfaces, and the dhcp tag is set
per-interface. Therefore, if you had inheritance setup on a system with 2+
interfaces, all of them would inherit the same dhcp tag. Not sure if
necessarily that's a bad thing (since by default they're all set to
"default" or blank), but it could cause problems.
A patch to setup inheritance could be done, just thought I'd point out the
issue I see with it before diving into it.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.