Bug 1501410 - Providers kebab menu is empty
Summary: Providers kebab menu is empty
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.2.0
: ---
Assignee: Alexander Wels
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-12 14:16 UTC by Petr Matyáš
Modified: 2017-12-20 11:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-12-20 11:46:28 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: planning_ack+
gshereme: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)
screenshot (36.58 KB, image/png)
2017-10-12 14:16 UTC, Petr Matyáš
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 83153 0 master MERGED webadmin: action panel Kebab visibility. 2017-10-24 22:35:52 UTC

Description Petr Matyáš 2017-10-12 14:16:11 UTC
Created attachment 1337808 [details]
screenshot

Description of problem:
Kebap menu is empty in Administration -> Providers, it should either have some items or the button should not be visible at all.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20171006152719.gitbc9a33d.el7.centos.noarch

How reproducible:
always

Steps to Reproduce:
1. open administration -> providers
2. click on kebap menu
3.

Actual results:
empty field appears

Expected results:
menu should have some items or the kebap menu button should not be visible at all

Additional info:

Comment 1 Petr Matyáš 2017-10-27 15:31:10 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20171025204923.git6f4cbc5.el7.centos.noarch

Comment 2 Sandro Bonazzola 2017-12-20 11:46:28 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.