View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005108||Kali Linux||[All Projects] Kali Package Bug||public||2018-11-19 18:23||2019-03-29 13:47|
|Priority||high||Severity||major||Reproducibility||have not tried|
|Status||closed||Resolution||no change required|
|Target Version||Fixed in Version|
|Summary||0005108: Installer fails to load AHCI module if preseed is present - Workaround no longer succeeds.|
|Description||Kali has been suffering from this bug |
However, the workaround in this thread has been functional.
Within the last 2 weeks, this workaround has started to work intermittently, failing (in our case) around 90% of the time.
It appears to be a race condition somewhere within debian-installer.
However, this makes systems uninstallable with a Preseed File.
Can you be more precise on when the work-around stopped to work reliably for you? We haven't updated the kernel in that timeframe so It would be nice to have a more precise date so that we can check what got changed at the time of the regression.
Do you have this problem with real hardware only or can you also reproduce it with virtual machines?
I would say approximately a month ago? it's hard to tell exactly because we're not imaging systems every day.
Its like ACHI isn't being loaded as early? and manually loading it doesn't seem to work.
The moment we yank out the preseed, it works perfectly, and a prebuilt iso with a preseed file built in seems to work fine too. it's just when the preseed is being pulled from a HTTPs server.
The logs don't tend to show us anything new and exciting either.
We're installing on the same hardware as in that bug for Debian, the intel NUC7i5.
We've seen this now reach out to older models as well as of today.
Not sure exactly what's going on. If i figure something else out i'll let you know.
So, We replaced the preseed file with another one which resolved this issue
This difference appears to be how the preseed file works. I think it has to do with putting an apt-cacher in the middle? While this didn't cause an issue, it does now.
We'll do more investigating, but it appears to be on our side for now.
||Thanks for following up. Since there's nothing we can do about this, I'm closing the bug.|
|2018-11-19 18:23||fyzbyt||New Issue|
|2018-11-20 09:11||rhertzog||Assigned To||=> rhertzog|
|2018-11-20 09:11||rhertzog||Status||new => assigned|
|2018-11-23 12:55||rhertzog||Note Added: 0009977|
|2018-11-23 13:03||rhertzog||Priority||normal => high|
|2018-11-23 13:03||rhertzog||Severity||minor => major|
|2018-11-27 16:52||fyzbyt||Note Added: 0010026|
|2018-12-19 18:24||fyzbyt||Note Added: 0010121|
|2019-01-03 18:11||fyzbyt||Note Added: 0010139|
|2019-03-29 13:47||rhertzog||Status||assigned => closed|
|2019-03-29 13:47||rhertzog||Resolution||open => no change required|
|2019-03-29 13:47||rhertzog||Note Added: 0010453|