Bug 859928

Created attachment 616530 [details]
File: backtrace

Created attachment 616531 [details]
File: core_backtrace

run system-config-kickstart

Package: system-config-kickstart-2.8.10-2.fc18
OS Release: Fedora release 18 (Spherical Cow)

I have no idea what comment 3 is suppose to mean.

As of today and F18-beta, it is still broken.

Given the date of this report, either nobody is using this or nobody cares if it works.

Too busy working on anaconda, which cannot be updated post-release.  I'll get to this for F19.  Sorry.

*** Bug 896173 has been marked as a duplicate of this bug. ***

*** Bug 901738 has been marked as a duplicate of this bug. ***

/usr/lib64/python2.7/site-packages/pyanaconda/iw does not appear to exist with Fedora 18 anaconda

What about this?

this problem still it's  in Version 2.8.10 to F18

system-config-kickstart-2.9.0-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/system-config-kickstart-2.9.0-1.fc18

verified: works

Verified: Works

Thanks a lot!

Package system-config-kickstart-2.9.0-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing system-config-kickstart-2.9.0-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-1856/system-config-kickstart-2.9.0-1.fc18
then log in and leave karma (feedback).

system-config-kickstart-2.9.0-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

I reported problems with the kickstart file generated by anaconda - see https://bugzilla.redhat.com/show_bug.cgi?id=908914 - but would consider system-config-kickstart as a workaround.

But when I follow the directions given in comments #13 and #14, above, I am offered nothing newer than version 2.8.10-2.fc18.  But (as reported above - see comment #9), version 2.8.10-2 does not work (because of the missing iw package.)

However, if I follow the links on either of the admin page referenced above (comments #10 and #13), I see that the version in-question is available at http://kojipkgs.fedoraproject.org//packages/system-config-kickstart/2.9.0/1.fc18/noarch/system-config-kickstart-2.9.0-1.fc18.noarch.rpm - is this what "pushed to the Fedora 18 stable repository" means?  What yum invocation do I need to address this repository?  Thanks.

I reported problems with the kickstart file generated by anaconda - see https://bugzilla.redhat.com/show_bug.cgi?id=908914 - but would consider system-config-kickstart as a workaround.

But when I follow the directions given in comments #13 and #14, above, I am offered nothing newer than version 2.8.10-2.fc18.  But (as reported above - see comment #9), version 2.8.10-2 does not work (because of the missing iw package.)

However, if I follow the links on either of the admin pages referenced above (comments #10 and #13), I see that the version in-question is available at http://kojipkgs.fedoraproject.org//packages/system-config-kickstart/2.9.0/1.fc18/noarch/system-config-kickstart-2.9.0-1.fc18.noarch.rpm - is this what "pushed to the Fedora 18 stable repository" means?  What yum invocation do I need to address this repository?  Thanks.

I see that system-config-kickstart is now available; perhaps propagation took longer than expected.

I appreciate that busy people took time from other and possibly more-critical tasks to bring this utility back to life.  That said, it's difficult to feel confident that system-config-kickstart is fc18-aware; for example, it provides no hooks for configuring LVM or BTRFS, nor even for device encryption.  Particularly as these parameterisations are difficult to debug (and because debugging kickstart files involves particularly painful latencies), this is unfortunate.

I hope that this project, or some variant, can be resurrected in the near future.  FWIW, it has often struck me as strange that anaconda itself does not actually =use= its own kickstart file - that is, treat its GUI as directed only to generating 'correct' kickstart files, which are then passed to an interpreter.  In this scenario, system-config-kickstart =is= the anaconda GUI, and vice-versa; further, the GUI is =just= a user-space application (and, so, able to be run at any time, post-OS installation.)

This sort of paradigm is well-established in other domains, and its benefits w/rt determinacy and transparency are, I think, well-understood; further, it's not apparent that anaconda's tight GUI::installation binding enables functionality unobtainable by other means.  The current design, OTOH, seems to guarantee that system-config-kickstart will fall into neglect - which, we may expect, will discourage end-users from taking advantage of it.

> I appreciate that busy people took time from other and possibly
> more-critical tasks to bring this utility back to life.  That said, it's
> difficult to feel confident that system-config-kickstart is fc18-aware; for
> example, it provides no hooks for configuring LVM or BTRFS, nor even for
> device encryption.  Particularly as these parameterisations are difficult to
> debug (and because debugging kickstart files involves particularly painful
> latencies), this is unfortunate.

It has never supported configuration of LVM, or btrfs, or lots and lots of other things.

> I hope that this project, or some variant, can be resurrected in the near
> future.  FWIW, it has often struck me as strange that anaconda itself does
> not actually =use= its own kickstart file - that is, treat its GUI as
> directed only to generating 'correct' kickstart files, which are then passed
> to an interpreter.  In this scenario, system-config-kickstart =is= the
> anaconda GUI, and vice-versa; further, the GUI is =just= a user-space
> application (and, so, able to be run at any time, post-OS installation.)

If you've been following the new UI in anaconda, you'd see this is basically what we've set up now.  anaconda does generate a kickstart file internally (though, the partitioning section of it does still need some work).  The eventual plan is to just use the anaconda UI as a kickstart generator, perhaps with some extra s-c-ks specific spokes for things like specifying your drives and doing authconfig.

What I've done for now is just a stop-gap to make it work in some capacity while we continue work in anaconda to support the new plan.  However that is going to take some time, and this is pretty far off topic for this bug report.