Bug 1474306 - Create subsection under system "Details" for network adapters
Summary: Create subsection under system "Details" for network adapters
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: develop
Hardware: All
OS: All
medium
high
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 11:24 UTC by Arthur Benoit
Modified: 2020-06-02 11:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-02 11:49:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Arthur Benoit 2017-07-24 11:24:17 UTC
Description of problem:
Currently there is no way to identify whether or not a network port is
connected. During inventory is would be very helpful for developers to identify NIC's and to ensure that beaker jobs are able to access the devices. 

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

How reproducible:
Always

Steps to Reproduce:
1. Run beaker inventory
2. Look at the system details
3. Notice that there is no way to identify whether or not a network port is
connected

Actual results:
There is no way to identify whether or not a network port is
connected

Expected results:
Likes the "Disks" subsection under Beaker "Details" it would be great
to see a subsection for network adapters that would include the link status for each network adapter.

Additional info:

Comment 1 Martin Styk 2020-06-02 11:49:38 UTC
Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>


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