Bug 1327615 - Incorrect subnet mask shown in network spoke
Summary: Incorrect subnet mask shown in network spoke
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 24
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedFreezeException
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 13:23 UTC by Jan Stodola
Modified: 2016-05-17 15:12 UTC (History)
6 users (show)

Fixed In Version: anaconda-24.13.5-1 anaconda-24.13.5-1.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-17 15:12:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (84.79 KB, image/png)
2016-04-15 13:23 UTC, Jan Stodola
no flags Details
anaconda.log (90.99 KB, text/plain)
2016-04-15 13:24 UTC, Jan Stodola
no flags Details
ifcfg.log (2.40 KB, text/plain)
2016-04-15 13:24 UTC, Jan Stodola
no flags Details
journalctl (193.95 KB, text/plain)
2016-04-15 13:24 UTC, Jan Stodola
no flags Details
nmcli c show uuid a29218f8-0805-492e-8fd5-bcdd76d31a4d (5.75 KB, text/plain)
2016-04-15 13:25 UTC, Jan Stodola
no flags Details

Description Jan Stodola 2016-04-15 13:23:04 UTC
Description of problem:
Anaconda shows an incorrect subnet mask on the network spoke:

127.0.0.1

The IP address is 192.168.122.172/24, so the mask should be 255.255.255.0, see attached screenshot.

Version-Release number of selected component (if applicable):
anaconda-24.13.3-1.fc24
NetworkManager-1.2.0-0.8.rc1.fc24

How reproducible:
always

Steps to Reproduce:
1. boot from boot.iso
2. proceed to the network spoke
3. check the netmask

Actual results:
127.0.0.1

Expected results:
a correct mask (255.255.255.0 in my case)

Comment 1 Jan Stodola 2016-04-15 13:23:53 UTC
Created attachment 1147642 [details]
screenshot

Comment 2 Jan Stodola 2016-04-15 13:24:11 UTC
Created attachment 1147643 [details]
anaconda.log

Comment 3 Jan Stodola 2016-04-15 13:24:28 UTC
Created attachment 1147645 [details]
ifcfg.log

Comment 4 Jan Stodola 2016-04-15 13:24:48 UTC
Created attachment 1147646 [details]
journalctl

Comment 5 Jan Stodola 2016-04-15 13:25:33 UTC
Created attachment 1147647 [details]
nmcli c show uuid a29218f8-0805-492e-8fd5-bcdd76d31a4d

Comment 6 David Shea 2016-04-20 16:08:29 UTC
https://github.com/rhinstaller/anaconda/pull/601

Comment 7 Fedora Blocker Bugs Application 2016-04-20 16:09:58 UTC
Proposed as a Freeze Exception for 24-beta by Fedora user dshea using the blocker tracking app because:

 Incorrect information is being displayed in the network spoke so it would be nice to fix that.

Comment 8 David Shea 2016-04-21 13:57:53 UTC
Pushed to master as 598ec41a9e8d39b6b8aaec83b6d47d89794f68d4 and ec24cb404fb60c024099703aace8caf2457850a8

Comment 9 Petr Schindler 2016-04-25 18:06:28 UTC
Discussed at 2016-04-25 blocker review meeting: [1]. 

This bug was rejected as Freeze Exception: at this point in the Beta process it's a bit late to poke the network screen for a purely cosmetic fix

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2016-02-29/f24-blocker-review.2016-04-25-17.02.html

Comment 10 Fedora Update System 2016-05-13 18:32:17 UTC
python-blivet-1.20.2-1.fc24 anaconda-24.13.5-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-1a7f1df025

Comment 11 Fedora Update System 2016-05-15 06:56:35 UTC
anaconda-24.13.5-1.fc24, python-blivet-1.20.2-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-1a7f1df025

Comment 12 Fedora Update System 2016-05-17 15:12:05 UTC
anaconda-24.13.5-1.fc24, python-blivet-1.20.2-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


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