Bug 1142256
Summary: | remote engine-reports-setup does not write conf file to allow accessing reports from engine | |||
---|---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Yedidyah Bar David <didi> | |
Component: | ovirt-engine-reports | Assignee: | Yedidyah Bar David <didi> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Stehlik <pstehlik> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 3.5 | CC: | aberezin, bazulay, bugs, ecohen, gklein, iheim, movciari, rbalakri, redhat.bugzilla, sbonazzo, sherold, sradco, yeylon, ylavi | |
Target Milestone: | --- | |||
Target Release: | 3.5.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | integration | |||
Fixed In Version: | oVirt-3.5 GA ovirt-engine-reports-3.5.0-1.fc19.noarch.rpm | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1144079 (view as bug list) | Environment: | ||
Last Closed: | 2014-10-17 12:35:31 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1144079 |
Description
Yedidyah Bar David
2014-09-16 12:57:51 UTC
workaound: do this manually after setup. E.g.: Create a file /etc/ovirt-engine/engine.conf.d/10-my-reports.conf with this content: ENGINE_REPORTS_BASE_URL=https://REPORTS_FQDN/ovirt-engine-reports ENGINE_REPORTS_DASHBOARD_URL=${ENGINE_REPORTS_BASE_URL}/flow.html?viewAsDashboardFrame=true ENGINE_REPORTS_PROXY_URL=${ENGINE_REPORTS_BASE_URL}/ovirt/reports-interface ENGINE_REPORTS_VERIFY_HOST=true ENGINE_REPORTS_VERIFY_CHAIN=true ENGINE_REPORTS_READ_TIMEOUT= replace above REPORTS_FQDN with the fqdn of the reports server (same as engine if on same server). Imported reports cert to truststore with the following command: keytool -importcert -alias reportscacert -file /etc/pki/ovirt-engine/certs/reports.cer -keystore /etc/pki/ovirt-engine/.truststore -storepass mypass If on remote host, replace above '/etc/pki/ovirt-engine/certs/reports.cer' with a file name containing the reports cert. service ovirt-engine restart (In reply to Yedidyah Bar David from comment #1) > workaound: do this manually after setup. E.g.: > > Create a file /etc/ovirt-engine/engine.conf.d/10-my-reports.conf with this > content: > > ENGINE_REPORTS_BASE_URL=https://REPORTS_FQDN/ovirt-engine-reports > ENGINE_REPORTS_DASHBOARD_URL=${ENGINE_REPORTS_BASE_URL}/flow. > html?viewAsDashboardFrame=true Sorry, this should be: ENGINE_REPORTS_DASHBOARD_URL=${ENGINE_REPORTS_BASE_URL}/flow.html?viewReportFlow=true > ENGINE_REPORTS_PROXY_URL=${ENGINE_REPORTS_BASE_URL}/ovirt/reports-interface > ENGINE_REPORTS_VERIFY_HOST=true > ENGINE_REPORTS_VERIFY_CHAIN=true > ENGINE_REPORTS_READ_TIMEOUT= > > replace above REPORTS_FQDN with the fqdn of the reports server (same as > engine if on same server). > > Imported reports cert to truststore with the following command: > > keytool -importcert -alias reportscacert -file > /etc/pki/ovirt-engine/certs/reports.cer -keystore > /etc/pki/ovirt-engine/.truststore -storepass mypass > > If on remote host, replace above '/etc/pki/ovirt-engine/certs/reports.cer' > with a file name containing the reports cert. > > service ovirt-engine restart Barak, Arthur, This means that 3.5 will require the workaround in order to setup reports in local and remote installations. Do you approve? This should definitely make it to 3.5.1, From my point of view this is a must. Current http://gerrit.ovirt.org/32989 is on engine side, works only if both are on same host. Another patch will be required on reports side when it's remote. *** Bug 1142750 has been marked as a duplicate of this bug. *** Not blocking 3.5.0 GA since it has been targeted for 3.5.1 only Eventually solved both this one and bug 1144079 with a single patch, leaving open for qe verification. *** Bug 1147435 has been marked as a duplicate of this bug. *** oVirt 3.5 has been released and should include the fix for this issue. |