Bug 1342943
| Summary: | Typos found while translating oVirt 4.0 UI strings | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Yuko Katabami <ykatabam> |
| Component: | Frontend.WebAdmin | Assignee: | Alona Kaplan <alkaplan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.0.0 | CC: | alkaplan, bugs, gklein, mburman, oourfali, stirabos, tnisan, ykatabam |
| Target Milestone: | ovirt-4.0.0-rc | Flags: | rule-engine:
ovirt-4.0.0+
rule-engine: planning_ack+ rule-engine: devel_ack+ rule-engine: testing_ack+ |
| Target Release: | 4.0.0 | ||
| 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: | 2016-08-01 12:28:20 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: | |||
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}
Alona, how can i test it? 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. 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^^ ? 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
|
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: