Bug 1470163

Summary:	if service name is changed between el6 and el7 then tooling can enable wrong one.
Product:	Red Hat Enterprise Linux 6	Reporter:	Petr Sklenar <psklenar>
Component:	preupgrade-assistant-el6toel7	Assignee:	Petr Stodulka <pstodulk>
Status:	CLOSED WONTFIX	QA Contact:	Alois Mahdal <amahdal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.10	Keywords:	Extras
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-01 16:43: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:	1429926

Description Petr Sklenar 2017-07-12 13:20:23 UTC

Description of problem:
if service name is changed between el6 and el7 then tooling can enable wrong one.
For ex el6=named, el7 named-chroot (if configured)

Version-Release number of selected component (if applicable):
preupgrade-assistant-2.4.1-1.el6.noarch

system/initscripts/control/check

How reproducible:
always

Steps to Reproduce:
1. have a named + /etc/sysconfig/named configured as chroot environment
2. chconfig named on
3. upgrade

Actual results:
named-chroot is the name of service on rhel7

Expected results:
rhel7 uses service name = named or named-chroot or named-*
it should be said somewhere or something 

Additional info:
it could affect more services which changed its name.

Comment 2 Petr Stodulka 2017-08-24 16:03:14 UTC

This is about more modules to fix that. But at least, we would mentioned the change inside the report so user will be noticed how to fix that that manually.

Comment 3 Petr Stodulka 2019-07-01 16:43:31 UTC

Closing this bugzilla as the component is under a maintenance mode in which the maintainers are going to fix only critical bugs. If you consider the bugzilla critical, feel free to reopen the bug with an explanation.