Bug 1509178

Summary: Wrapped provider URL in General tab of external provider
Product: [oVirt] ovirt-engine Reporter: Petr Kubica <pkubica>
Component: Frontend.WebAdminAssignee: Dana <delfassy>
Status: CLOSED CURRENTRELEASE QA Contact: Ravi Nori <rnori>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.1.6.2CC: bugs, gshereme, mperina, pkubica, rnori
Target Milestone: ovirt-4.3.1Flags: rule-engine: ovirt-4.3+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-01 10:20:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot
none
4.2 none

Description Petr Kubica 2017-11-03 09:45:00 UTC
Description of problem:
Wrapped provider URL in General tab of external provider


Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.1.6.2-0.1.el7.noarch

How reproducible:
Always - when url is too long

Actual results:
see screenshot

Expected results:
url shouldn't be wrapped (or wrapped in this way - in middle of (sub)domain)

Comment 1 Petr Kubica 2017-11-03 09:46:08 UTC
Created attachment 1347232 [details]
screenshot

Comment 2 Greg Sheremeta 2017-11-07 17:25:32 UTC
Is this an issue in 4.2?

Comment 3 Petr Kubica 2017-11-08 11:52:31 UTC
Created attachment 1349412 [details]
4.2

Yes, I see the issue in 4.2.0-0.4.master.el7

Comment 4 Ravi Nori 2019-02-22 15:20:09 UTC
verified on ovirt-engine-4.3.1.1-1.el7

Comment 5 Sandro Bonazzola 2019-03-01 10:20:22 UTC
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.