Bug 1139951 - guest recipes do not inherit OS major install options configured by the admin
Summary: guest recipes do not inherit OS major install options configured by the admin
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 0.18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.18.1
Assignee: Dan Callaghan
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-10 04:38 UTC by Dan Callaghan
Modified: 2018-02-06 00:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-12 07:36:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Dan Callaghan 2014-09-10 04:38:03 UTC
Similar to bug 1138533, but slightly different...

Guest recipes and recipes dispatched to OpenStack do not obey OS major install options configured by the admin.

This is not actually a new problem in 0.18 (probably guest recipes regressed in 0.10) but it was never noticed before because OS major install options were not used for anything besides the "serial" Anaconda option which was added and then dropped during the RHEL7 Alpha timeframe. Now in 0.18 we have the distro feature variables which can be overridden for custom distros.

Steps to Reproduce:
1. Add a fake custom RHEL6 distro, as per the second half of https://bugzilla.redhat.com/show_bug.cgi?id=1070597#c11
2. Provision the custom RHEL6 distro in a guest recipe

Actual results:
After fixing bug 1138533, the distro is treated like RHEL7. Guest recipe kickstart includes systemd-specific bits (systemctl instead of chkconfig, RHTS_OPTION_COMPATIBLE=, etc).

Expected results:
Distro should be treated like RHEL6. Systemd-specific bits should not be present (chkconfig not systemctl, no RHTS_OPTION_COMPATIBLE=).

Comment 1 Dan Callaghan 2014-09-10 06:48:43 UTC
On Gerrit: http://gerrit.beaker-project.org/3318

Comment 4 Dan Callaghan 2014-09-12 07:36:23 UTC
Beaker 0.18.1 has been released.


Note You need to log in before you can comment on or make changes to this bug.