revisor

#69 Advanced Configuration Requires Kickstart
Closed: Fixed Opened by jsteffan.

Closed: Fixed
Reopen Issue

The current logic of the "Customize/Review additional options loaded from kickstart data" (self.cfg.advanced_configuration) requires that first "Use package manifest from kickstart data" is selected (self.cfg.use_kickstart). I don't think this is what we want.

load_kickstart.py

Lines: 174-201

I don't want to adjust anything because the advanced configuration stuff might need a kickstart object or some such. I might have time to look at it tonight, just wanted to get it reported.

This use case might be covered.. Should still check...

package_selection.py Line: 496

This use case might be covered.. Should still check...

package_selection.py Line: 496

A kickstart object is created in the config store. Depending on the selections made in LoadKickstart, that kickstart object is populated. If no kickstart is supplied, either the default (sample-ks.cfg) is being used, or no kickstart is being loaded and we continue with the advanced configuration.

Fixed.

A kickstart object is created in the config store. Depending on the selections made in LoadKickstart, that kickstart object is populated. If no kickstart is supplied, either the default (sample-ks.cfg) is being used, or no kickstart is being loaded and we continue with the advanced configuration.

Fixed.

Milestone Beta release on F7 deleted

Milestone Beta release on F7 deleted

Metadata Update from @jsteffan:
- Issue assigned to kanarip
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.