Bug 1652590 - Configuration files are not properly marked in grafana RPM package
Summary: Configuration files are not properly marked in grafana RPM package
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-monitoring-integration
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: gowtham
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-22 12:47 UTC by Daniel Horák
Modified: 2019-05-08 18:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-08 16:04:50 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1515276 0 unspecified CLOSED notifier - configuration files are not set in rpm 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1650557 0 high CLOSED Grafana is not working after WA upgrade to BU2 2022-07-09 10:16:49 UTC

Internal Links: 1515276 1650557

Description Daniel Horák 2018-11-22 12:47:03 UTC 
Description of problem:
  Grafana package contains few files in /etc/* directory, which might be
  considered as configuration files, but they are not marked such way in the
  RPM package.
  This cause problems during package update process, for example Bug 1650557.

Version-Release number of selected component (if applicable):
  grafana-4.6.4-1.el7rhgs.x86_64

How reproducible:
  100%

Steps to Reproduce:
1. Check list of files in /etc/... owned by grafana package:
  # rpm -ql grafana | grep etc
  /etc/grafana
  /etc/grafana/grafana.ini
  /etc/grafana/ldap.toml
  /etc/sysconfig/grafana-server
2. Check if those files are marked as configuration files in RPM package:
  # rpm -qc grafana 
  # 

Actual results:
  There are 3 files in grafana package in /etc/ directory, but neither of them
  is marked as configuration file.

Expected results:
  Configuration files should be marked as "configuration" files in RPM package.

Additional info:
  See also Bug 1650557 and Bug 1515276.
Note You need to log in before you can comment on or make changes to this bug.