Bug 1287547 - 389-ds-base- leaves empty /NUL around after ipa-server-install
Summary: 389-ds-base- leaves empty /NUL around after ipa-server-i...
Alias: None
Product: Fedora
Classification: Fedora
Component: 389-ds-base
Version: 23
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-12-02 10:27 UTC by Jan Pazdziora
Modified: 2020-09-13 21:33 UTC (History)
6 users (show)

Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-12-20 16:31:13 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1636 0 None None None 2020-09-13 21:33:41 UTC

Description Jan Pazdziora 2015-12-02 10:27:28 UTC
Description of problem:

When ipa-server-install is run to configure FreeIPA server, with 389-ds-base- there is a new empty file /NUL left around after the installation finishes. The stat /NUL suggests it was created during the step

  [2/43]: creating directory server instance

hence filing against 389-ds-base.

Version-Release number of selected component (if applicable):


How reproducible:

Deterministic, seen in containerized installations.

Steps to Reproduce:
1. ipa-server-install
2. ls -la /NUL

Actual results:

-rw-r--r--. 1 root root 0 Dec  2 15:00 /NUL

Expected results:

ls: cannot access /NUL: No such file or directory

Additional info:

Comment 1 Jan Pazdziora 2015-12-02 10:29:07 UTC
With 389-ds-base- I did not see this behaviour.

Comment 2 Jan Pazdziora 2015-12-02 10:31:03 UTC
My guess is it came from 9fefc13c02c9ae037fad053152193794706aaa31. That

  -f "/dev/null"

test does not seem correct -- /dev/null is a device, not file.

Comment 3 Rich Megginson 2015-12-02 15:49:44 UTC

*** This bug has been marked as a duplicate of bug 1259959 ***

Comment 6 Rich Megginson 2015-12-03 21:36:27 UTC
Upstream ticket:

Comment 7 Mike McCune 2016-03-28 23:29:09 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

Comment 8 Fedora End Of Life 2016-11-24 13:54:30 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 9 Fedora End Of Life 2016-12-20 16:31:13 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

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.