Bug 1489771 - Read error - cannot reconstruct rpm from disk files
Summary: Read error - cannot reconstruct rpm from disk files
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 31
Hardware: noarch
OS: Linux
low
low
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-08 10:57 UTC by fednuc
Modified: 2020-11-24 19:59 UTC (History)
29 users (show)

Fixed In Version:
Clone Of: 1381387
Environment:
Last Closed: 2020-11-24 19:59:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description fednuc 2017-09-08 10:57:44 UTC
+++ This bug was initially created as a clone of Bug #1381387 +++

Description of problem:

Upon updating two systems (Fedora 24, 64-bit) using dnf, the following error displayed during the process on both systems:

/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 8192 bytes from offset 3786868)
cannot reconstruct rpm from disk files
selinux-policy-targeted-3.13.1-191.17.fc24.noarch: Delta RPM rebuild failed


It appears to have re-downloaded the package after the error occurred on each:

selinux-policy-targeted-3.13.1-191.17.fc24.noar 6.7 MB/s | 8.7 MB     00:01

--- Additional comment from Fedora End Of Life on 2017-07-25 19:20:33 EDT ---

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

--- Additional comment from John Reiser on 2017-08-01 18:02:06 EDT ---

I get the same error on Fedora 25:
=====
 selinux-policy                    noarch    3.13.1-225.19.fc25             updates                   495 k
 selinux-policy-targeted           noarch    3.13.1-225.19.fc25             updates                   9.3 M
   . . .
(19/37): selinux-policy-targeted-3.13.1-225.18.fc25_3.13.1-225.19.fc25.noar  92 kB/s | 4.3 MB     00:47    

   . . .
/var/lib/selinux/targeted/active/policy.kern: read error                  ] 5.4 MB/s |  54 MB     00:18 ETA
(tried to read 8192 bytes from offset 3852492)
cannot reconstruct rpm from disk files
   . . .
selinux-policy-targeted-3.13.1-225.19.fc25.noarch: Delta RPM rebuild failed
selinux-policy-targeted-3.13.1-225.19.fc25.noarch.rpm                       270 kB/s | 9.3 MB     00:35    
=====
# rpm -qf /usr/bin/dnf
dnf-1.1.10-6.fc25.noarch

--- Additional comment from Fedora End Of Life on 2017-08-08 15:18:30 EDT ---

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--- Additional comment from Stan King on 2017-08-08 21:29:48 EDT ---

I concur with Mr. Reiser in comment #2.  I got the error recently with Fedora 25, and the symptoms looked much the same.  It recovered after fetching the standard RPM, after the processing of the delta RPM failed.  If I see it again, I'll open a new bug, unless I see that this one gets re-opened.

--- Additional comment from John Reiser on 2017-08-15 19:20:30 EDT ---

I get the same error in f26, so the original Reporter (or someone with privileges) could change the Version to 26, thus keeping this report alive beyond f24 EOL.

=====
(194/382): selinux-policy-targeted-3.13.1-259.fc26_3.13.1-260.4. 1.0 MB/s | 5.3 MB     00:05
   [[snip]]
(369/382): selinux-policy-3.13.1-260.4.fc26.noarch.rpm           271 kB/s | 502 kB     00:01
   [[snip]]
var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 4600 bytes from offset 3888024)
cannot reconstruct rpm from disk files
[DRPM 193/200] sqlite-libs-3.19.1-1.fc26_3.20.0-1.fc26.x86_64.drpm: done
[DRPM 194/200] strace-4.17-1.fc26_4.18-1.fc26.x86_64.drpm: done
[DRPM 195/200] tar-1.29-4.fc26_1.29-5.fc26.x86_64.drpm: done
[DRPM 196/200] unzip-6.0-33.fc26_6.0-34.fc26.x86_64.drpm: done
[DRPM 197/200] totem-pl-parser-3.10.7-2.fc26_3.10.8-1.fc26.x86_64.drpm: done
[DRPM 198/200] unicode-ucd-9.0.0-3.fc26_10.0.0-1.fc26.noarch.drpm: done
[DRPM 199/200] firefox-54.0-2.fc26_55.0.1-1.fc26.x86_64.drpm: done
Some packages were not downloaded. Retrying.
selinux-policy-targeted-3.13.1-260.4.fc26.noarch.rpm             840 kB/s | 9.4 MB     00:11
-------------------------------------------------------------------------------------------------
Total                                                            1.2 MB/s | 379 MB     05:27
=====

--- Additional comment from Paulo Matos on 2017-09-05 04:05:06 EDT ---

I saw this on Fedora 26 as well. Is there a bug to track this on F26?

--- Additional comment from AsciiWolf on 2017-09-05 05:04:41 EDT ---

I got the same error during today's update.
(selinux-policy-targeted-3.13.1-260.8.fc26.noarch)

/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 6452 bytes from offset 3888896)
cannot reconstruct rpm from disk files

--- Additional comment from Tomislav Ivek on 2017-09-06 03:29:54 EDT ---

Can also confirm the error on today's update of selinux-policy-3.13.1-260.8.fc26.noarch.rpm.

/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 6452 bytes from offset 3888896)
cannot reconstruct rpm from disk files


-------------------------------

Cloned to a new bug in F26 because requests for someone to change the version/re-open the old one by someone with adequate privileges were ignored.

I also saw the message with the above selinux update.

Comment 1 Edward Campbell 2017-09-08 13:34:04 UTC
I received the same error on Fedora 25 9/8/17. Below is the output:

Downloading Packages:
(1/5): selinux-policy-devel-3.13.1-225.20.fc25_ 232 kB/s | 554 kB     00:02    
(2/5): selinux-policy-3.13.1-225.22.fc25.noarch 256 kB/s | 496 kB     00:01    
(3/5): upower-0.99.5-2.fc25.x86_64.rpm          288 kB/s | 161 kB     00:00    
(4/5): selinux-policy-targeted-3.13.1-225.20.fc 392 kB/s | 4.3 MB     00:11    
[DRPM] selinux-policy-devel-3.13.1-225.20.fc25_3.13.1-225.22.fc25.noarch.drpm: done
/var/lib/selinux/targeted/active/policy.kern: read error |  13 MB     00:09 ETA
(tried to read 8192 bytes from offset 3859404)
cannot reconstruct rpm from disk files
(5/5): thunderbird-52.2.1-1.fc25_52.3.0-1.fc25. 595 kB/s |  15 MB     00:25    
[DRPM] thunderbird-52.2.1-1.fc25_52.3.0-1.fc25.x86_64.drpm: done               
selinux-policy-targeted-3.13.1-225.22.fc25.noarch: Delta RPM rebuild failed
selinux-policy-targeted-3.13.1-225.22.fc25.noar 806 kB/s | 9.4 MB     00:11    
--------------------------------------------------------------------------------
Total                                           426 kB/s |  30 MB     01:11     
Delta RPMs reduced 86.7 MB of updates to 29.8 MB (65.1% saved)
Running transaction check


The update seems to have completed normally, but is it worth trusting that feeling, since selinux is for my system security?

Any help or advise as to whether all is OK would be appreciated.

Comment 2 Need Real Name 2017-09-11 22:46:38 UTC
Same bug here, Fedora 25, uname -a gives
4.10.11-200.fc25.x86_64 #1 SMP Tue Apr 18 17:25:01 UTC 2017 x86_64 x86_64 x86_64 GNU/Linu

problem seems to be

selinux-policy-3.13.1-225.22.fc25.noarch

/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 8192 bytes from offset 3859404)
cannot reconstruct rpm from disk files

Comment 3 David Canzi 2017-10-18 15:20:41 UTC
I get this error occasionally on a nightly cron job that
runs this:

dnf -y --quiet --downloadonly upgrade

The most recent version of this message I received was:

/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 8192 bytes from offset 3871400)
cannot reconstruct rpm from disk files

The offset 3871400 is past the end of the file.

The file mentioned in the error message is part of the
selinux-policy-targeted package.  On the night this
error message was produced, dnf downloaded an upgrade
for selinux-policy-targeted.  When I ran dnf upgrade the
next day, all package upgrades succeeded, including for
selinux-policy-targeted.

My best guess as to what happened is that the delta rpm
file could not be applied successfully (which the error
message told me about) and so the full rpm file was
downloaded (which nothing told me about).  There is
probably a script in the delta rpm file that fails, and
outputs the baffling error message.  Everything that
had to work worked.

The problem is in selinux-policy-targeted or its delta
rpm files, not in dnf or rpm.

Comment 4 Joel C Ewing 2018-02-07 15:03:58 UTC
And I just had this occur twice in the last week on f27!   Different offset than mentioned previously, but same file:
/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 8192 bytes from offset 3895944)
Not a nice error message to see, because "read error" implies potential disk hardware issues, while from the pattern of previous reports this seems to be a software logic issue.

As with other reports, dnf appeared to successfully download the full rpm file and completed normally; so other than an alarming message, no damage.

I also checked the attributes of my policy.kern (after the dnf update) and it was 3,896,983 bytes, so at offset 3895944 a read of 8192 bytes would be past the end of the file.  Presumably if this existing file on my system was being checked, this would have been a part of the rpm that was unchanged in the new version (selinux-policy-targeted-3.13.1-283.24.fc27.noar in my case)

For this to happen repeatedly and just on this one file in this one package, there must be something weird about the way this one package is constructed.   If this is the result of some kind of validity check on every 8K segment of an existing file of the prior package version, something isn't handling end-of-file correctly.  It's as if somewhere the file length is recorded wrong, or is being ignored.

Comment 5 Ian Collier 2018-02-07 18:13:52 UTC
The problem here seems to be that the files in /var/lib/selinux/targeted/active
are written regularly and don't have to agree with what's in the RPM, but the
RPM file isn't flagging them as variable files.

So in the package itself (3.13.1-260.18.fc26):

-rw-r--r--   1 root     root      3904423 Dec 13 07:58 ./var/lib/selinux/targeted/active/policy.kern
-rw-------   1 root     root           73 Dec 13 07:58 ./var/lib/selinux/targeted/active/seusers
-rw-------   1 root     root          101 Dec 13 07:58 ./var/lib/selinux/targeted/active/users_extra

while installed on system X:

-rw-r--r-- 1 root root 3979371 Feb  7 18:00 policy.kern
-rw-r--r-- 1 root root 3979371 Feb  7 18:00 policy.linked
-rw-r--r-- 1 root root     314 Feb  7 18:00 seusers
-rw------- 1 root root      73 Feb  7 18:00 seusers.linked
-rw-rw-rw- 1 root root     241 Feb  7 18:00 seusers.local
-rw-r--r-- 1 root root     101 Feb  7 18:00 users_extra
-rw------- 1 root root     101 Feb  7 18:00 users_extra.linked

and installed on system Y:

-rw-r--r-- 1 root root 3879608 Feb  7 17:46 policy.kern
-rw-rw-rw- 1 root root 3879608 Feb  7 17:46 policy.linked
-rw-r--r-- 1 root root     212 Feb  7 17:46 seusers
-rw------- 1 root root      73 Feb  7 17:46 seusers.linked
-rw-rw-rw- 1 root root     139 Feb  7 17:46 seusers.local
-rw-r--r-- 1 root root     101 Feb  7 17:46 users_extra
-rw------- 1 root root     101 Feb  7 17:46 users_extra.linked

And this leads to:

$ sudo rpm -V selinux-policy-targeted
..5....T.    /var/lib/selinux/targeted/active/commit_num
S.5....T.    /var/lib/selinux/targeted/active/file_contexts
.......T.    /var/lib/selinux/targeted/active/homedir_template
S.5....T.    /var/lib/selinux/targeted/active/policy.kern
SM5....T.    /var/lib/selinux/targeted/active/seusers
.M.....T.    /var/lib/selinux/targeted/active/users_extra

Therefore the specfile needs %verify(not md5 size mtime) and possibly also
something else such as %ghost or %config in order to mark these as changeable
files.  (It's not clear to me that RPM even *has* a directive that says "we
install this file, but it might change later, and it's not a config file".
The RPM for rpm itself marks the RPM database files as %config(noreplace)
although it's not clear that they are in fact config files.)

Comment 6 Andrew J. Caines 2018-03-21 14:24:26 UTC
Reproduced just now updating Fedora 27 Workstation.

----8<----
$ sudo dnf upgrade --downloadonly
Last metadata expiration check: 2:00:51 ago on Wed 21 Mar 2018 07:56:25 AM EDT.
...
 selinux-policy               noarch 3.13.1-283.28.fc27        updates    535 k
 selinux-policy-targeted      noarch 3.13.1-283.28.fc27        updates     10 M
...
Install   4 Packages
Upgrade  77 Packages
Remove    4 Packages

Total download size: 306 M
DNF will only download packages for the transaction.
...
[MIRROR] clang-libs-5.0.1-3.fc27_5.0.1-4.fc27.x86_64.drpm: Curl error (18): Transferred a partial file for http://mirror.vcu.edu/pub/gnu_linux/fedora/updates/27/x86_64/drpms/clang-libs-5.0.1-3.fc27_5.0.1-4.fc27.x86_64.drpm [transfer closed with 899925 bytes remaining to read]
(17/81): clang-libs-5.0.1-3.fc27_5.0.1-4.fc27.x  43 kB/s | 1.3 MB     00:30    
...
(42/81): selinux-policy-targeted-3.13.1-283.26. 1.1 MB/s | 5.3 MB     00:04    
...
(77/81): selinux-policy-3.13.1-283.28.fc27.noar 3.3 MB/s | 535 kB     00:00    
(78/81): shared-mime-info-1.9-2.fc27.x86_64.rpm 2.7 MB/s | 327 kB     00:00    
(79/81): sssd-nfs-idmap-1.16.1-1.fc27.x86_64.rp 1.2 MB/s |  82 kB     00:00    
[MIRROR] gstreamer1-plugins-ugly-free-1.13.91-7.gitf16550f.fc27.x86_64.rpm: Curl error (7): Couldn't connect to server for https://svwh.dl.sourceforge.net/project/unitedrpms/27/x86_64/gstreamer1-plugins-ugly-free-1.13.91-7.gitf16550f.fc27.x86_64.rpm [Failed to connect to svwh.dl.sourceforge.net port 443: Connection timed out]
[FAILED] gstreamer1-plugins-ugly-free-1.13.91-7.gitf16550f.fc27.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success
...
[DRPM 39/42] microcode_ctl-2.1-20.fc27_2.1-22.fc27.x86_64.drpm: done           
/var/lib/selinux/targeted/active/policy.kern: read error | 248 MB     00:01 ETA
(tried to read 8192 bytes from offset 3895380)
cannot reconstruct rpm from disk files
[DRPM 40/42] libreoffice-data-5.4.5.1-1.fc27_5.4.6.2-1.fc27.noarch.drpm: done  
[DRPM 41/42] python2-libs-2.7.14-8.fc27_2.7.14-10.fc27.x86_64.drpm: done       
(81/81): libreoffice 96% [=================== ] 6.2 MB/s | 248 MB     00:01 ETA
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
  Cannot download gstreamer1-plugins-ugly-free-1.13.91-7.gitf16550f.fc27.x86_64.rpm: All mirrors were tried
----8<----

Verifying selinux-policy-targeted

----8<----
$ sudo rpm -V selinux-policy-targeted
S.5....T.  c /etc/selinux/targeted/contexts/files/file_contexts.local
..5....T.    /var/lib/selinux/targeted/active/commit_num
.......T.    /var/lib/selinux/targeted/active/file_contexts
.......T.    /var/lib/selinux/targeted/active/homedir_template
S.5....T.    /var/lib/selinux/targeted/active/policy.kern
.......T.    /var/lib/selinux/targeted/active/seusers
.......T.    /var/lib/selinux/targeted/active/users_extra

Comment 7 Dave Allan 2018-04-02 12:56:21 UTC
Just saw this again on F27, can someone with perms bump the version to 27?

Comment 8 Fedora End Of Life 2018-05-03 08:56:02 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 9 Dave Allan 2018-05-03 13:00:48 UTC
Given that a number of us are still occasionally seeing this on F27, can somebody with permissions bump the version and keep open?

Comment 10 Stan King 2018-05-06 19:00:14 UTC
I second Dave Allan's observation.  I've seen this in the past few days on F27.

Comment 11 Tom Bouwman 2019-01-18 20:22:35 UTC
Happened on my F29 system nightly update.

Downloading Packages:
(1/5): kernel-4.19.15-300.fc29.x86_64.rpm        24 kB/s |  28 kB     00:01
(2/5): selinux-policy-targeted-3.14.2-44.fc29_3 1.6 MB/s | 9.8 MB     00:06
(3/5): selinux-policy-3.14.2-46.fc29.noarch.rpm 716 kB/s | 115 kB     00:00
(4/5): kernel-core-4.19.15-300.fc29.x86_64.rpm  2.0 MB/s |  25 MB     00:12
(5/5): kernel-modules-4.19.15-300.fc29.x86_64.r 2.4 MB/s |  28 MB     00:11
/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 7146 bytes from offset 8375012)
cannot reconstruct rpm from disk files
Some packages were not downloaded. Retrying.
selinux-policy-targeted-3.14.2-46.fc29.noarch.r 5.1 MB/s |  14 MB     00:02

Comment 12 Lukas Vrabec 2019-01-20 17:57:16 UTC
Hi rpm maintainers, 

Please, could someone look on this issue? At least try to explain whats going on? 

Thanks,
Lukas.

Comment 13 Panu Matilainen 2019-01-21 08:40:04 UTC
Rpm is not really involved here at all, the error comes from deltarpm.

If the file content is expected to change then you need to flag it as such one way or the other, as people have already noted.
Basically the options are
- %config()
- %ghost
- %noverify(size,digest)

The best (or least worst) option depends on the actual content, I have no clue about that in this case.

Comment 14 Joel C Ewing 2019-01-22 06:35:01 UTC
What you are saying is that this is an inter-disciplinary problem, which is the kind that will languish for many versions of Fedora unless someone in one of the groups involved takes some initiative.  It appears those responsible for selinux-policy-targeted lack understanding of some subtle requirement of rpm, those responsible for rpm have no direct knowledge of selinux packaging internals, and the typical end-user who actually encounters the error from rpm is going to lack enough understanding of the internals of either to report this problem in a way that is likely to get it resolved.

Panu, 
Is there any chance that someone like yourself who seems to understand and be in a position explain the rpm issues could somehow drive this as an selinux problem and get into direct contact with a maintainer of the selinux package, so that the marriage of minds needed to actually solve this problem could be achieved?  It almost sounds like the resolution might be trivial if the right parties would just combine their knowledge.

Comment 15 Seth Alford 2019-04-08 16:06:22 UTC
Just saw this on Fedora 29:

(25/27): selinux-policy-targeted-3.14.2-51.fc29 621 kB/s | 7.4 MB     00:12    
[DRPM 4/8] dnf-4.2.2-1.fc29_4.2.2-2.fc29.noarch.drpm: done                     
[DRPM 5/8] python3-dnf-4.2.2-1.fc29_4.2.2-2.fc29.noarch.drpm: done             
(26/27): google-chrome-stable-73.0.3683.103-1.x 3.0 MB/s |  55 MB     00:18    
(27/27): glibc-all-langpacks-2.28-27.fc29.x86_6 947 kB/s |  25 MB     00:27    
[DRPM 6/8] gtk3-3.24.1-2.fc29_3.24.1-3.fc29.x86_64.drpm: done                  
[DRPM 7/8] wget-1.20.1-1.fc29_1.20.3-1.fc29.x86_64.drpm: done                  
/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 7249 bytes from offset 8457524)
cannot reconstruct rpm from disk files
Some packages were not downloaded. Retrying.
selinux-policy-targeted-3.14.2-53.fc29.noarch.r 1.6 MB/s |  14 MB     00:08    
--------------------------------------------------------------------------------
Total                                           2.0 MB/s | 112 MB     00:55     
Failed Delta RPMs increased 110.2 MB of updates to 112.2 MB (-1.1% wasted)
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
.
.
.
  Running scriptlet: selinux-policy-targeted-3.14.2-53.fc29.noarch        19/54 
  Upgrading        : selinux-policy-targeted-3.14.2-53.fc29.noarch        19/54 
  Running scriptlet: selinux-policy-targeted-3.14.2-53.fc29.noarch        19/54 
.
.
.
[and rpm --verify says:]
rpm --verify selinux-policy-targeted-3.14.2-53.fc29.noarch
S.5....T.  c /etc/selinux/targeted/contexts/files/file_contexts.local
..5....T.    /var/lib/selinux/targeted/active/commit_num
.......T.    /var/lib/selinux/targeted/active/file_contexts
.......T.    /var/lib/selinux/targeted/active/homedir_template
S.5....T.    /var/lib/selinux/targeted/active/policy.kern
.......T.    /var/lib/selinux/targeted/active/seusers
.......T.    /var/lib/selinux/targeted/active/users_extra

Comment 16 Seth Alford 2019-04-08 16:15:28 UTC
FWIW, I did a dnf reinstall of the package and it appeared to load successfully:

----begin cut and paste----

# dnf reinstall  selinux-policy-targeted-3.14.2-53.fc29.noarch
Last metadata expiration check: 0:20:09 ago on Mon 08 Apr 2019 08:48:24 AM PDT.
Dependencies resolved.
============================================================================================
 Package                        Architecture  Version                  Repository      Size
============================================================================================
Reinstalling:
 selinux-policy-targeted        noarch        3.14.2-53.fc29           updates         14 M

Transaction Summary
============================================================================================

Total download size: 14 M
Installed size: 50 M
Is this ok [y/N]: y
Downloading Packages:
selinux-policy-targeted-3.14.2-53.fc29.noarch.rpm           3.8 MB/s |  14 MB     00:03    
--------------------------------------------------------------------------------------------
Total                                                       3.5 MB/s |  14 MB     00:04     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                    1/1 
  Running scriptlet: selinux-policy-targeted-3.14.2-53.fc29.noarch                      1/2 
  Reinstalling     : selinux-policy-targeted-3.14.2-53.fc29.noarch                      1/2 
  Running scriptlet: selinux-policy-targeted-3.14.2-53.fc29.noarch                      1/2 
  Cleanup          : selinux-policy-targeted-3.14.2-53.fc29.noarch                      2/2 
  Running scriptlet: selinux-policy-targeted-3.14.2-53.fc29.noarch                      2/2 
  Verifying        : selinux-policy-targeted-3.14.2-53.fc29.noarch                      1/2 
  Verifying        : selinux-policy-targeted-3.14.2-53.fc29.noarch                      2/2 

Reinstalled:
  selinux-policy-targeted-3.14.2-53.fc29.noarch                                             

Complete!

----end cut and paste----

rpm --verify said, afterwards, the same thing:

---begin cut and paste----
S.5....T.  c /etc/selinux/targeted/contexts/files/file_contexts.local
..5....T.    /var/lib/selinux/targeted/active/commit_num
.......T.    /var/lib/selinux/targeted/active/file_contexts
.......T.    /var/lib/selinux/targeted/active/homedir_template
S.5....T.    /var/lib/selinux/targeted/active/policy.kern
.......T.    /var/lib/selinux/targeted/active/seusers
.......T.    /var/lib/selinux/targeted/active/users_extra
----end cut and paste----

Comment 17 David Canzi 2019-04-16 04:39:02 UTC
The first time I saw this error message, it took me half an hour
to figure out that I didn't need to do anything about it.  If
1000 other people each took a similar length of time to figure
that out, that's 500 hours of other people's time wasted.  That's
probably way more than the amount of time it takes one person
familiar with the relevant code to fix the problem.

Comment 18 Ben Cotton 2019-05-02 19:35:53 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 19 Dave Allan 2019-05-02 20:14:00 UTC
Per comment 15 this behavior is still present on F29.  Can someone with permissions bump the version again?

Comment 20 Ben Cotton 2019-08-13 19:22:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 21 Fedora Admin XMLRPC Client 2020-01-23 16:24:53 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 22 Naresh Sukhija 2020-02-01 18:41:33 UTC
The bug affects Fedora 31 as observed on 2nd February 2020, the package selinux-policy-targeted-3.14.4-44.fc31.noarch was installed and the drpm selinux-policy-targeted-3.14.4-44.fc31_3.14.4-45.fc31.noarch.drpm failed to rebuild, so it downloaded the complete package i.e. selinux-policy-targeted-3.14.4-45.fc31.noarch.rpm

I observe the following outputs before update:

# rpm -q selinux-policy-targeted
selinux-policy-targeted-3.14.4-44.fc31.noarch
# rpm -V selinux-policy-targeted
S.5....T.  c /etc/selinux/targeted/contexts/files/file_contexts.local
..5....T.    /var/lib/selinux/targeted/active/commit_num
.......T.    /var/lib/selinux/targeted/active/file_contexts
.......T.    /var/lib/selinux/targeted/active/homedir_template
S.5....T.    /var/lib/selinux/targeted/active/policy.kern
.......T.    /var/lib/selinux/targeted/active/seusers
.......T.    /var/lib/selinux/targeted/active/users_extra
# ls -ld /etc/selinux/targeted/contexts/files/file_contexts.local /var/lib/selinux/targeted/active/commit_num /var/lib/selinux/targeted/active/file_contexts /var/lib/selinux/targeted/active/homedir_template /var/lib/selinux/targeted/active/policy.kern /var/lib/selinux/targeted/active/seusers /var/lib/selinux/targeted/active/users_extra
-rw-r--r--. 1 root root     272 Jan 21 23:57 /etc/selinux/targeted/contexts/files/file_contexts.local
-rw-------. 1 root root      32 Jan 21 23:57 /var/lib/selinux/targeted/active/commit_num
-rw-------. 1 root root  397608 Jan 21 23:57 /var/lib/selinux/targeted/active/file_contexts
-rw-------. 1 root root   12503 Jan 21 23:57 /var/lib/selinux/targeted/active/homedir_template
-rw-------. 1 root root 8578932 Jan 21 23:57 /var/lib/selinux/targeted/active/policy.kern
-rw-------. 1 root root      73 Jan 21 23:57 /var/lib/selinux/targeted/active/seusers
-rw-------. 1 root root     101 Jan 21 23:57 /var/lib/selinux/targeted/active/users_extra
#

Comment 23 Ben Cotton 2020-11-03 17:29:51 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 24 Naresh Sukhija 2020-11-04 06:37:32 UTC
It seems Fedora 33 doesn't include drpm for selinux-policy-targeted package. Was this a conscious decision or due to some automation ?

Comment 25 Ben Cotton 2020-11-24 19:59:12 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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