On 03/21/18 07:46, CLOSE Dave wrote:
Greshko wrote:
>> I think I found the problem. Comparing packages installed on this
>> problem machine with others, I noticed that grubby was not
>> installed. After installing it and then re-installing the kernel,
>> I find the kernel in /boot where it belongs.
>>
>> Evidently, something isn't checking dependencies sufficiently. I
>> saw no error messages indicating anything was missing.
> If that turns out to be the case, and if things on that machine used
> to work, it would be interesting to know if/when grubby was removed.
Too long ago to still be in my /var/log/dnf* logs. Evidently, some time
after kernel 4.14.11-300.fc27.x86_64 as that was the last one properly
placed in /boot.
OK...
> Also, if it fails with grubby out it sounds like a very good
> bugzilla.
True.
I have tested this in a VM and verified the failure. There is one exception. If the
/boot directory does not contain a directory with the name of the "machine-id"
then
the upgrade will be successful.
Will you be writing up the BZ?
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.