Bug 1795411 - upstream patch: dracut-network's dracut-initqueue spams boot console with "/lib/dracut/hooks/initqueue/settled/99-nm-run.sh: line 13: basename: command not found"
Summary: upstream patch: dracut-network's dracut-initqueue spams boot console with "/l...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 31
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1804131 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-27 21:52 UTC by Matthias Andree
Modified: 2020-11-24 15:47 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-24 15:47:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matthias Andree 2020-01-27 21:52:25 UTC
Description of problem:
I somehow have dracut-network in use, and use full-disk encryption.
During boot, my console gets spammed with "/lib/dracut/hooks/initqueue/settled/99-nm-run.sh: line 13: basename: command not found".

Version-Release number of selected component (if applicable):
dracut-network-049-27.git20181204.fc31.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. install dracut-network, and make it so it gets activated. I, for instance, have these on my kernel's command line: rd.neednet=1 ip=192.168.33.7::192.168.33.253:255.255.255.0:examplehost:eth0:none nameserver=192.168.33.7
2. reboot

Actual results:
console spam as under Description above

Expected results:
no such messages.

Additional info:
apparently this issue got fixed upstream already, see https://github.com/dracutdevs/dracut/commit/4c216b1db6a86373549e13b60250a7fcf94417b9

Comment 1 David Tardon 2020-09-30 11:06:21 UTC
*** Bug 1804131 has been marked as a duplicate of this bug. ***

Comment 2 Richard W.M. Jones 2020-10-01 10:38:18 UTC
Did you mean to add this to the RISC-V tracker bug?  I don't see how
they are related.

Comment 3 David Tardon 2020-10-06 07:44:35 UTC
(In reply to Richard W.M. Jones from comment #2)
> Did you mean to add this to the RISC-V tracker bug?  I don't see how
> they are related.

I didn't mean anything. It was copied by bugzilla from bug 1804131, which I marked as a duplicate of this one.

Comment 4 Ben Cotton 2020-11-03 16:15:20 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-11-24 15:47:19 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.