Bug 1249795 - FileNotFoundError: [Errno 2] No such file or directory: '/var/run/anaconda.pid'
Summary: FileNotFoundError: [Errno 2] No such file or directory: '/var/run/anaconda.pid'
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: David Shea
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-03 20:38 UTC by Giulio 'juliuxpigface'
Modified: 2015-08-04 14:56 UTC (History)
4 users (show)

Fixed In Version: anaconda-23.18-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-04 14:56:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Giulio 'juliuxpigface' 2015-08-03 20:38:05 UTC
Description of problem:
I encountered this exception after the execution of liveinst.

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

How reproducible:
I haven't tried to reproduce it.

Steps to Reproduce:
1. Boot Fedora-Live-KDE-x86_64-23_Alpha-TC2.iso
2. Launch 'liveinst' via konsole
3. Install the system, following this TestCase: https://fedoraproject.org/wiki/QA:Testcase_partitioning_guided_multi_empty_all
4. Set a password for root, do not create a standard user.
5. Close 'liveinst'.

Actual results:
1. Anaconda seems to run fine and the new system is installed properly.
2. This traceback is printed on the terminal emulator:

Error in atexit._run_exitfuncs:
Traceback (most recent call last):
    File "/sbin/anaconda", line 91, in exitHandler
        os.unlink(pidfile_path)
        FileNotFoundError: [Errno 2] No such file or directory: '/var/run/anaconda.pid'


Expected results:
1. I don't know what consequences causes this (if any), but ideally liveinst should not crash on exit.


Additional info:
I was testing on a qemu-kvm guest, with two empty virtual disks (both 10gb).

Comment 1 David Shea 2015-08-03 20:47:35 UTC
I'm not real sure what caused this particular issue but I have an idea that removes that chunk of code entirely.

Comment 2 David Shea 2015-08-04 14:56:17 UTC
Actually, this is already fixed by commit 2a96c06f63d3f5215e004de66a79bc24141438b0


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