Created attachment 925294 [details] screenshot Description of problem: vms that are kickstarted using the pulp synced kickstart tree repos from cdn are failing with kernel panic Version-Release number of selected component (if applicable): [root@qe-blade-08 ~]# rpm -qa pulp-server pulp-server-2.4.0-0.30.beta.el6.noarch [root@qe-blade-08 ~]# How reproducible: Steps to Reproduce: 1.sync the kickstart tree from cdn for 6.5 2. try to kickstart a vm with the tree 3. Actual results: kernel panic Expected results: Additional info:
The issue is that the default property is not being set properly on the component groups. If no group is set as default then the graphical installer lets you progress without selecting any group. In this case packages are missing. However, If a group is selected, minimal install, basic server, etc., then the install completes and boots successfully.
Editing pulp_rpm/plugins/pulp_rpm/plugins/distributors/yum/metadata/package.py:78 and adding the lines: ElementTree.SubElement(group_element, 'default').text = \ str(group_unit.metadata['default']).lower() will fix the problem
PR: https://github.com/pulp/pulp_rpm/pull/540
This was fixed in the 2.4.1-0.1.alpha build.
verified with 2.4.1 kickstarted rhel6 with the synced repo from cdn
We are rebasing pulp-2.4.1, and so all of these bugs can no longer be considered VERIFIED. We will need to recheck them against the rebased build to make sure the cherry picking strategy did not introduce any regressions.
build: 2.5.0-0.6.beta
verified [root@cloud-qe-15 ~]# rpm -qa pulp-server pulp-server-2.5.0-0.7.beta.el7.noarch [root@cloud-qe-15 ~]# kickstarted rhel6 with the synced repo from cdn