Bug 1418923 - links to embedded files and clients aren't working
Summary: links to embedded files and clients aren't working
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.1.0.3
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ovirt-4.1.1
: ---
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-03 07:39 UTC by Sandro Bonazzola
Modified: 2017-02-15 07:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-15 07:54:48 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: blocker+

Attachments (Terms of Use)

Description Sandro Bonazzola 2017-02-03 07:39:55 UTC 
Description of problem:
links to embedded files and clients aren't working, engine says 404, examples:
https://[your manager's address]/ovirt-engine/services/files/spice/usbdk-x64.msi
https://[your manager's address]/ovirt-engine/services/files/spice/virt-viewer-x64.msi
and other,
but they are in docs(in ovirt and also in rhel)

Reported on users mailing list: http://lists.ovirt.org/pipermail/users/2017-February/079415.html
Comment 1 Red Hat Bugzilla Rules Engine 2017-02-03 07:40:01 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 2 Greg Sheremeta 2017-02-07 21:21:08 UTC 
@Michal would this be a virt issue?
Comment 3 Oved Ourfali 2017-02-08 09:57:10 UTC 
Moving to virt.
If you need help, talk to me.
Comment 4 Tomas Jelinek 2017-02-10 10:17:13 UTC 
The documentation referenced the incorrect links, fixed in documentation:

https://github.com/oVirt/ovirt-site/pull/784/commits/c575b4914306cd19b68357e3fb0c2f183dfc6fe9
Comment 5 Tomas Jelinek 2017-02-15 07:54:48 UTC 
fixed in upstream docs only
Note You need to log in before you can comment on or make changes to this bug.