Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1084807

Summary: VM panel: column IP not readable with multiple interfaces
Product: [Retired] oVirt Reporter: Markus Stockhausen <mst>
Component: ovirt-engine-webadminAssignee: Lior Vernia <lvernia>
Status: CLOSED NOTABUG QA Contact: Meni Yakove <myakove>
Severity: low Docs Contact:
Priority: medium    
Version: 3.4CC: acathrow, bazulay, danken, ecohen, gklein, iheim, masayag, mgoldboi, mst, yeylon
Target Milestone: ---Keywords: Triaged, UserExperience
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-19 16:58:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot
none
before
none
after none

Description Markus Stockhausen 2014-04-06 18:45:47 UTC
Description of problem:

If VM has multiple IP addresses and a guest agent is installed th column "IP address" in the web admin portal is not very comfortable to read.


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

Ovirt 3.4


How reproducible:

100%

Steps to Reproduce:

1. Install Linux VM in OVirt 3.4

2. start Linux VM

3. If guest agent is not available do the following to emulate agent detection of multiple network interfaces inside the VM:

echo  '{"__name__": "network-interfaces", "interfaces": [{"name": "en1", "inet": "1.2.3.4"}, {"name": "en2", "inet": "9.10.11.12"}]}' > /dev/virtio-ports/com.redhat.rhevm.vdsm

Actual results:

webadmin ip address column gets populated but is not readable. see screenshot

Expected results:

better separation of multiple addresses.

Additional info:

Comment 1 Markus Stockhausen 2014-04-06 18:46:51 UTC
Created attachment 883369 [details]
screenshot

Comment 2 Markus Stockhausen 2014-04-06 18:48:43 UTC
Remark: screenshot is from 125% windows theme scaling. Nevertheless I guess there a too many spaces between the digits and the dots of one IP address.

Comment 3 Lior Vernia 2014-05-19 08:10:42 UTC
Hi Markus,

What do you mean by "windows theme"? There are no space characters between digits/dots inside a single IP address, and by default in Firefox it looks better than the screenshot you've attached. So it might be the custom theme, if you're using one, that makes things look more spacious, and there's not a lot that can be done about that.

Having said that, we could add some separator character between addresses, maybe ';'. Does that sound like a good enough solution to you?

Yours, Lior.

Comment 4 Markus Stockhausen 2014-05-19 15:06:36 UTC
Hi,

"windows theme 125%" means that I only changed the scaling to 125%. But this does not seem to be the culprit. The error arises from the "manual agent emulation".

To reproduce the issue:

1) install a linux VM without! guest agent.

2) start linux VM

3) fill IP information inside VM manually:

echo  '{"__name__": "network-interfaces", "interfaces": [{"name": "en1", "inet": "1.2.3.4"}, {"name": "en2", "inet": "9.10.11.12"}]}' > /dev/virtio-ports/com.redhat.rhevm.vdsm

Any ideas how this command should be changed. It would be helpful to know the syntax because the IP data inside webadmin will be helpful for Linux VM distros that do not have a guest agent yet.

Comment 5 Lior Vernia 2014-05-19 15:22:14 UTC
Just to make sure, this only happens when you input the IP addresses manually? Via the guest agent things look different?

Comment 6 Markus Stockhausen 2014-05-19 15:33:13 UTC
See screenshots attached.

before.png: generated by agent
after.png: generated by echo

Comment 7 Markus Stockhausen 2014-05-19 15:35:17 UTC
Created attachment 897227 [details]
before

Comment 8 Markus Stockhausen 2014-05-19 15:35:47 UTC
Created attachment 897230 [details]
after

Comment 9 Lior Vernia 2014-05-19 15:53:49 UTC
Interesting. Dan, any idea?

Comment 10 Dan Kenigsberg 2014-05-19 16:58:02 UTC
Markus, please note that replacing the guest agent with shell scripting is not recommended or supported.

Nonetheless: The value of "inet" has to be a list (of all ipv4 addresses) and not a single string. When you see on screen is a somewhat-funny side effect of vdsm (and python in general) referring to strings as a list of chars.

I suspect that

echo  '{"__name__": "network-interfaces", "interfaces": [{"name": "en1", "inet": "1.2.3.4"}, {"name": "en2", "inet": ["9.10.11.12"]}]}' > /dev/virtio-ports/com.redhat.rhevm.vdsm

would fly.

Comment 11 Markus Stockhausen 2014-05-19 17:05:22 UTC
Thanks,

that did the trick. As mentioned I only use this method for guests that do not have a guest agent yet. For anyone who might find this thread in the future: The complete syntax for supplying two interfaces:

echo  '{"__name__": "network-interfaces", "interfaces": [{"name": "en1", "inet": "1.2.3.4"}, {"name": "en2", "inet": ["9.10.11.12"]}]}' > /dev/virtio-ports/com.redhat.rhevm.vdsm