Bug 1514941 - Network: rephrase 'There is no important LLDAP information' message
Summary: Network: rephrase 'There is no important LLDAP information' message
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-19 15:30 UTC by Yaniv Kaul
Modified: 2017-12-20 11:13 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:13:03 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 84577 0 master MERGED webadmin: Rephrase noImportantLLDP 2017-11-30 14:36:01 UTC

Description Yaniv Kaul 2017-11-19 15:30:35 UTC 
Description of problem:
When LLDP is not available, simply state:
'LLDP information is not available'

The current message is 'There is no important LLDP informaiton'.


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

How reproducible:
Always

Steps to Reproduce:
1. look into the bubble on a NIC when it's connected to an interface without LLDP.
Comment 1 Michael Burman 2017-12-03 07:21:27 UTC 
Verified on - 4.2.0-0.0.master.20171201121510.gitb338573.el7.centos
Comment 2 Michael Burman 2017-12-03 07:23:21 UTC 
(In reply to Michael Burman from comment #1)
> Verified on - 4.2.0-0.0.master.20171201121510.gitb338573.el7.centos

Rephrased to : 'LLDP information is not available'
Comment 3 Sandro Bonazzola 2017-12-12 16:09:06 UTC 
This bug is targeted 4.2.1 but is verified in 4.2.0.
Can you please check / verify this bug status and set target milestone and bug status accordingly?
Comment 4 Ales Musil 2017-12-14 12:18:47 UTC 
It is in 4.2.0
Comment 5 Sandro Bonazzola 2017-12-20 11:13:03 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.