Bug 1447635 - [UX] window title "undefined" in removing subnet
Summary: [UX] window title "undefined" in removing subnet
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-provider-ovn
Classification: oVirt
Component: provider
Version: 1.0.4
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Dominik Holler
QA Contact: Mor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-03 11:19 UTC by Mor
Modified: 2017-12-20 11:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:21:26 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screenshot (12.42 KB, image/png)
2017-05-03 11:19 UTC, Mor
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 76922 0 master MERGED webadmin: Set title on RemoveExternalSubnet dialog 2017-05-17 12:52:37 UTC

Description Mor 2017-05-03 11:19:18 UTC
Created attachment 1275879 [details]
screenshot

Description of problem:
When deleting existing subnet of OVN network, the title of the deletion window is set as Undefined.

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170429081602.gitb982df7.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Create OVN network with subnet.
2. Try to delete the subnet from Networks --> Select network --> Subnets.
3. Window appear with Undefined title.

Actual results:
Window is with undefined title.

Expected results:
Window should be with title.

Comment 1 Mor 2017-06-11 10:25:04 UTC
Verified on: 4.2.0-0.0.master.20170609091031.gitc86d08a.el7.centos

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