Description of problem:
The kickstart.profile.system.getPartitioningScheme() method filters out %include statements that are in the 'partitions' section of the Kickstart. Since these lines are valid, they should not be filtered in the output from the API call.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. put an %include statement in the 'partitions' section of a Kickstart
2. use the kickstart.profile.system.getPartitioningScheme() method to get the contents of the 'partitions' section
%include lines are filtered out
%include lines should be returned since they are valid
getPartitioningScheme returns all partition sections now
The following package(s) fixing the issue:
['part /boot --fstype=ext3 --size=200 ', 'part pv.01 --size=1000 --grow ', 'part swap --size=1000 --maxsize=2000 ', 'volgroup myvg pv.01 ', 'logvol / --vgname=myvg --name=rootvol --size=1000 --grow', '%include test line 1']
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Previously, the kickstart.profile.system.getPartitioningScheme() method did not return "%include" statements in the "partitions" section of Kickstart. With this update, the method has been corrected and returns "%include" statements as expected.
Changing to Version 540 to distinguish the BZ from Bug 659469