Bug 1299431 - rename fails when reports is installed and not set up
Summary: rename fails when reports is installed and not set up
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-reports
Classification: Retired
Component: Setup
Version: 3.6.5
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: ovirt-3.6.2
: 3.6.2.4
Assignee: Yedidyah Bar David
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-18 11:20 UTC by Yedidyah Bar David
Modified: 2016-02-18 11:07 UTC (History)
9 users (show)

Fixed In Version: rhevm-reports-3.6.2.4-1.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 11:07:59 UTC
oVirt Team: Integration
rule-engine: ovirt-3.6.z+
ylavi: planning_ack+
sbonazzo: devel_ack+
pnovotny: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 52337 0 master MERGED packaging: rename: Do not fail if reports is not set up 2016-01-19 10:39:49 UTC

Description Yedidyah Bar David 2016-01-18 11:20:48 UTC
Description of problem:

$subject

[ ERROR ] Failed to execute stage 'Misc configuration': [Errno 2] No such file or directory: '/etc/ovirt-engine/engine.conf.d/10-setup-reports-access.conf'

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


How reproducible:


Steps to Reproduce:
1. install engine and reports
2. setup engine but not reports
3. rename

Actual results:

fails

Expected results:

succeeds

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2016-01-18 11:34:23 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Lukas Svaty 2016-01-21 11:44:19 UTC
rhevm-dwh-3.6.2-1.el6ev.noarch

Comment 3 Lukas Svaty 2016-01-21 11:44:56 UTC
correct package is: rhevm-reports-3.6.2.4-1.el6ev.noarch, tested and verified


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