Bug 1335092 - DASD device discovery succeeds even when the device doesn't exist
Summary: DASD device discovery succeeds even when the device doesn't exist
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 24
Hardware: s390x
OS: Linux
Target Milestone: ---
Assignee: Vendula Poncova
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
Reported: 2016-05-11 10:48 UTC by Jan Stodola
Modified: 2017-08-08 14:28 UTC (History)
5 users (show)

Fixed In Version: anaconda-26.20-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-08-08 14:28:16 UTC
Type: Bug

Attachments (Terms of Use)
screenshot (74.25 KB, image/png)
2016-05-11 10:48 UTC, Jan Stodola
no flags Details
storage.log (22.56 KB, text/plain)
2016-05-11 10:51 UTC, Jan Stodola
no flags Details

Description Jan Stodola 2016-05-11 10:48:24 UTC
Created attachment 1156080 [details]

Description of problem:
When adding new DASD in GUI, anaconda reports success even in case the device doesn't exist, see attached screenshot.

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

How reproducible:

Steps to Reproduce:
1. proceed to the Installation Destination spoke
2. click "Add a disk..."
3. click "Add ECKD DASD..."
4. enter some non-existing device number, for example "tttt"
5. click "Start Discovery"

Actual results:
Device discovery succeeded.

Expected results:
Device discovery shouldn't be successful

Comment 3 Jan Stodola 2016-05-11 10:51:03 UTC
Created attachment 1156084 [details]

Comment 5 Vendula Poncova 2017-01-12 15:53:04 UTC
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/929

Comment 6 Fedora End Of Life 2017-07-25 20:43:41 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 '24'.

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 24 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 7 Fedora End Of Life 2017-08-08 14:28:16 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.