Bug 1657265 - [RHEL 8.2] tmpfiles snippet needs updated path
Summary: [RHEL 8.2] tmpfiles snippet needs updated path
Keywords:
Status: MODIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mdadm
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: XiaoNi
QA Contact: Fine Fan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-07 14:38 UTC by Rik Theys
Modified: 2020-02-19 16:14 UTC (History)
11 users (show)

Fixed In Version: mdadm-4.1-12.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Rik Theys 2018-12-07 14:38:10 UTC
Description of problem:
When booting a RHEL 8 beta, the following message is displayed in the system log:

systemd-tmpfiles[635]: [/usr/lib/tmpfiles.d/mdadm.conf:1] Line references path below legacy directory /var/run/, updating /var/run/mdadm → /run/mdadm; please update the tmpfiles.d/ drop-in file accordingly.

The snippet needs to be updated with the new default path.

Version-Release number of selected component (if applicable):
mdadm-4.1-rc1_2.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. Boot system with package installed
2.
3.

Actual results:
Message about legacy path in use

Expected results:
No messages

Additional info

Comment 1 Nigel Croxon 2018-12-11 15:01:31 UTC
This is not a specific mdadm problem, but a packaging problem.

Comment 2 ChanghuiZhong 2018-12-13 06:12:20 UTC
Hi,Nigel Croxon

The same problem occurs on the RHEL 8 beta OS. When using the RPM package to install mdadm, the same message appears.

[root@storageqe-09 ~]# rpm -ivh mdadm-4.1-rc1_3.el8.x86_64.rpm 
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:mdadm-4.1-rc1_3.el8              ################################# [100%]
[/usr/lib/tmpfiles.d/mdadm.conf:1] Line references path below legacy directory /var/run/, updating /var/run/mdadm → /run/mdadm; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/pesign.conf:1] Line references path below legacy directory /var/run/, updating /var/run/pesign → /run/pesign; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/subscription-manager.conf:1] Line references path below legacy directory /var/run/, updating /var/run/rhsm → /run/rhsm; please update the tmpfiles.d/ drop-in file accordingly.
[root@storageqe-09 ~]# 

I want to know how this problem will be dealt with next.

Comment 3 Nigel Croxon 2019-01-15 12:53:41 UTC
Hello Changhui,

Does this problem still exist with later versions of RHEL8 snapshots?

Comment 4 ChanghuiZhong 2019-01-16 03:22:28 UTC
Hi,Nigel Croxon

This problem still exists in the latest RHEL-8.0-Snapshot-3.1 :(RHEL-8.0-20181220.1-x86_64-dvd1.iso)

[root@intel-mahobay-01 ~]# 
[root@intel-mahobay-01 ~]# uname -a
Linux intel-mahobay-01.lab.eng.rdu.redhat.com 4.18.0-56.el8.x86_64 #1 SMP Mon Dec 17 13:56:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[root@intel-mahobay-01 ~]# 
[root@intel-mahobay-01 ~]# rpm -q mdadm
package mdadm is not installed
[root@intel-mahobay-01 ~]# 
[root@intel-mahobay-01 ~]# rpm -ivh mdadm-4.1-3.el8.x86_64.rpm 
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:mdadm-4.1-3.el8                  ################################# [100%]
[/usr/lib/tmpfiles.d/mdadm.conf:1] Line references path below legacy directory /var/run/, updating /var/run/mdadm → /run/mdadm; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/pesign.conf:1] Line references path below legacy directory /var/run/, updating /var/run/pesign → /run/pesign; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/subscription-manager.conf:1] Line references path below legacy directory /var/run/, updating /var/run/rhsm → /run/rhsm; please update the tmpfiles.d/ drop-in file accordingly.
[root@intel-mahobay-01 ~]# rpm -q mdadm
mdadm-4.1-3.el8.x86_64
[root@intel-mahobay-01 ~]# 

thanks,
Changhui Zhong

Comment 6 Christian Horn 2019-02-08 07:56:53 UTC
I see this on a nightly build.
Probable duplicate: bz1657269

Comment 7 XiaoNi 2019-02-14 08:00:25 UTC
Hi all

This patch can fix this problem

diff --git a/mdadm.conf b/mdadm.conf
index 6200117..3207dda 100644
--- a/mdadm.conf
+++ b/mdadm.conf
@@ -1 +1 @@
-d /var/run/mdadm 0710 root root -
+d /run/mdadm 0710 root root -


[root@storageqe-29 ~]# rpm -ivh mdadm-4.1-5.el8.x86_64.rpm 
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:mdadm-4.1-5.el8                  ################################# [100%]
[/usr/lib/tmpfiles.d/subscription-manager.conf:1] Line references path below legacy directory /var/run/, updating /var/run/rhsm → /run/rhsm; please update the tmpfiles.d/ drop-in file accordingly.

I don't know the root cause. Because I'm not familiar with the detail of rpm. Why does it complain about this. 
But it's too late to fix this problem. It's not a serious problem. It just gives a warning message. The rpm
package can be installed successfully. 

So it's better to fix this in rhel8.1

Thanks
Xiao

Comment 9 ChanghuiZhong 2019-06-12 08:39:48 UTC
Hello

This problem still exists in mdadm-4.1-6.el8:

[root@hp-z8-g4-01 ~]# rpm -ivh mdadm-4.1-6.el8.x86_64.rpm 
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:mdadm-4.1-6.el8                  ################################# [100%]
[/usr/lib/tmpfiles.d/mdadm.conf:1] Line references path below legacy directory /var/run/, updating /var/run/mdadm → /run/mdadm; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/pesign.conf:1] Line references path below legacy directory /var/run/, updating /var/run/pesign → /run/pesign; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/subscription-manager.conf:1] Line references path below legacy directory /var/run/, updating /var/run/rhsm → /run/rhsm; please update the tmpfiles.d/ drop-in file accordingly.
[root@hp-z8-g4-01 ~]#

Comment 10 Pino Toscano 2019-07-23 12:50:53 UTC
(In reply to XiaoNi from comment #7)
> Hi all
> 
> This patch can fix this problem
> 
> diff --git a/mdadm.conf b/mdadm.conf
> index 6200117..3207dda 100644
> --- a/mdadm.conf
> +++ b/mdadm.conf
> @@ -1 +1 @@
> -d /var/run/mdadm 0710 root root -
> +d /run/mdadm 0710 root root -

This seems correct to me, although I'm not a systemd expert.

> [root@storageqe-29 ~]# rpm -ivh mdadm-4.1-5.el8.x86_64.rpm 
> Verifying...                          #################################
> [100%]
> Preparing...                          #################################
> [100%]
> Updating / installing...
>    1:mdadm-4.1-5.el8                  #################################
> [100%]
> [/usr/lib/tmpfiles.d/subscription-manager.conf:1] Line references path below
> legacy directory /var/run/, updating /var/run/rhsm → /run/rhsm; please
> update the tmpfiles.d/ drop-in file accordingly.
> 
> I don't know the root cause. Because I'm not familiar with the detail of
> rpm. Why does it complain about this. 
> But it's too late to fix this problem. It's not a serious problem. It just
> gives a warning message. The rpm
> package can be installed successfully. 

This is not an RPM issue, but a systemd message: the mdadm RPM contains .service files for systemd, so when it is updated, systemd is invoked to reload its units.
/var/run is considered a legacy path, and /run is the "canonical" location, so systemd prints that message.

Also, the message quoted above is not from mdadm, but from subscription-manager (see the [/usr/lib/tmpfiles.d/subscription-manager.conf:1] prefix in the message text).


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