Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Have an issue with a bad kickstart tree. I have tried every conceivable way to fix the problem short of reinstalling or deleting all my content. No joy.
Need a method to force redownload of specified content so that it overwrites existing content.
Version-Release number of selected component (if applicable):
6.1.5
How reproducible:
Unknown - feature not available - problem not reproducible.
Kickstart failure is always reproducible.
fails as it thinks that xfs is not an available file system (or any other fs for that matter) when specified in the partition table.
Steps to Reproduce:
1. Kickstart system
2. Fails just as anaconda starts
3. Resynching satellite kickstart files has no effect
4. Message is no new packages/content
Actual results:
Resynching can not be forced.
Expected results:
Request force resynch
Content is refreshed. Kickstart then succeeds.
Additional info: