Bug 818262
| Summary: | RHEVM - Admin GUI: Origin field for templates is always "N/A" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Daniel Paikov <dpaikov> | ||||
| Component: | ovirt-engine-webadmin-portal | Assignee: | Tal Nisan <tnisan> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | vvyazmin <vvyazmin> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 3.1.0 | CC: | abaron, acathrow, amureini, dyasny, ecohen, hateya, iheim, ofrenkel, Rhev-m-bugs, ykaul | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | SI11 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-12-04 20:07:24 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Daniel Paikov
2012-05-02 15:26:20 UTC
not sure why it happens, can be one of the following: - information simply doesn't exist in OVF - backend doesn't read it well from OVF before returning results to the GUI - GUI simply doesn't display it. Needs investigation. Created attachment 592916 [details]
screen shot
not solved.
my templates are from 3.0
moving back on devel.
It will only happen with newly created OVF files, before the fix the OVF writer omitted the origin field, please check on a newly created OVF, import it and see if the origin is visible This is the bug: (In reply to comment #0) > Origin field for templates on an export domain is always "N/A". For VMs the > origin field is either RHEV or oVirt, never N/A. if the fix is only for templates created from current build than its only half a fix and we cannot verify it. There can be no other fix since you cannot restore the origin fields for OVF files created without this field in the first place, you have no way to determine what was the origin Tal, this is not a new field for 3.1. I attached the same Export domain in 3.0 and the templates are showing the field Origin with correct results. ovf shows the same code for field in 3.0 and 3.1: <Origin>0</Origin> 0=RHEVM on both, 3.0 shows it as RHEVM and 3.1 shows it as N/A. since this field exists in both 3.0 and 3.1 and the results from the same templates are read correctly from the ovf in 3.0 and not in 3.1 I cannot verify this bug and in fact its a regression. you were right the 'origin' I was seeing was for the vms and not the templates. so as we discussed with Dan, if we have a N/A result we should change it to something else and not present N/A Remind me what should I write instead of N/A? (In reply to comment #8) > Remind me what should I write instead of N/A? Not Specified When template origin is unknown, the origin field will appear as "Not Specified" instead of N/A http://gerrit.ovirt.org/6337 Checked on si11. |