Bug 1470163 - if service name is changed between el6 and el7 then tooling can enable wrong one.
if service name is changed between el6 and el7 then tooling can enable wrong ...
Status: ASSIGNED
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant-el6toel7 (Show other bugs)
6.10
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: pstodulk
Alois Mahdal
: Extras
Depends On:
Blocks: 1429926
  Show dependency treegraph
 
Reported: 2017-07-12 09:20 EDT by Petr Sklenar
Modified: 2017-08-24 12:03 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Sklenar 2017-07-12 09:20:23 EDT
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 pstodulk 2017-08-24 12:03:14 EDT
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.

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