Bug 1342943 - Typos found while translating oVirt 4.0 UI strings
Summary: Typos found while translating oVirt 4.0 UI strings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Alona Kaplan
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-06 07:59 UTC by Yuko Katabami
Modified: 2016-08-01 12:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-01 12:28:20 UTC
oVirt Team: Network
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 58795 0 master MERGED webadmin: typos in setup-networks error messages 2016-06-08 08:04:01 UTC
oVirt gerrit 58818 0 ovirt-engine-4.0 MERGED webadmin: typos in setup-networks error messages 2016-06-08 09:35:30 UTC

Description Yuko Katabami 2016-06-06 07:59:18 UTC
Description of problem:

I found typos in the following strings:

Cannot ${action} ${type}. NetworkAttachment (id ${$referrerId}) does not reference nic coherently. Nic name and id reference different nics: nicId ${referringId} nicName ${referringName}}.

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



Actual results:
(id ${$referrerId}) 
${referringName}}

Expected results:
(id ${referrerId}) 
${referringName}

Additional info:

Comment 1 Yuko Katabami 2016-06-06 08:54:11 UTC
A similar error found in:

Cannot ${action} ${type}. NetworkAttachment (id ${referrerId}) does not reference network coherently. Network name and id reference different networks: networkId ${referringId} networkName ${referringName}}.



${referringName}}
=> ${referringName}

Comment 2 Michael Burman 2016-06-22 13:13:07 UTC
Alona, how can i test it?

Comment 3 Alona Kaplan 2016-07-04 05:28:22 UTC
Send setup network via rest api.
For example you can add an attachment to a nic -
1. supply the nic name of one nic and the nic id of another nic.
2. supply the network name of one network and the network id of another network.

Comment 4 Michael Burman 2016-07-19 06:51:18 UTC
Hi Yuko, 

Tested on 4.0.1.1-0.1.el7ev 

- [Cannot setup Networks. NetworkAttachment (id null) does not reference nic coherently. Nic name and id reference different nics: nicId 696ee82f-af02-4607-83f7-68f369404f9f nicName ens1f0.]

- [Cannot setup Networks. NetworkAttachment (id null) does not reference network coherently. Network name and id reference different networks: networkId 9c92de73-ebf9-470a-bd78-b767320d9c0b networkName n3.]


Is this is the expected result^^ ?

Comment 5 Yuko Katabami 2016-07-19 14:22:09 UTC
Hi Michael,

I confirmed the updated messages in zanata.
They are properly fixed as follows.

Cannot ${action} ${type}. NetworkAttachment (id ${referrerId}) does not reference network coherently. Network name and id reference different networks: networkId ${referringId} networkName ${referringName}.

	
Cannot ${action} ${type}. NetworkAttachment (id ${referrerId}) does not reference nic coherently. Nic name and id reference different nics: nicId ${referringId} nicName ${referringName}.


Kind regards,

Yuko


Note You need to log in before you can comment on or make changes to this bug.