-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I believe I've encountered a bug with using cobbler where a sub-profile that inherits the template-files directive of the parent and defines the ksmeta="X=Y" does not make the $X variable available to any advanced templating you perform (ie. is not available in $searchList(). However, if you define ksmeta and template-files within the same profile, you are able to access the ksmeta variable defined and it shows up in $searchList().
- - Create a profile with --template-files="X=Y" where the template file X uses the ksmeta variable A (defined in the next step).
- - Create a sub-profile with --inherit="first profile" and define --ksmeta="A=B"
- - Create and build a system out that uses the sub-profile and take a look at the template file Y, that is supposed to be created.
Results:
The system builds out, but the template file, Y does not have access to the ksmeta variables defined in the sub-profile that the system is using.
Reasons I think this is a bug:
The ksmeta variables ARE available if you define ksmeta in the same profile (or subprofile) as the --template-file you are attempting to construct. In the man page for --inherit, it mentions that all parent settings will be overridden by what's in the sub-profile *except* --ksmeta and --ksopts. In this case, it seems that ksmeta is not being pulled in from the parent profile.
Possible workaround:
Define ksmeta and template-files in the same sub-profile. I'm having to do this now to get it working, but it's a bit of a hack and doesn't work like the man page specifies.
Thanks so much,
Kris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.12 (Darwin)
iEYEARECAAYFAkshEtgACgkQzlDC+kIIIbp0fwCeJKS9ZxZXeO9NlJxvfVXRj32o
Om4AniclS/IEyu97JRNGvUAX0WwV0QyG
=Irfh
-----END PGP SIGNATURE-----