Bug 1058980

Summary:

[kernel] nothing to do when installing kernel-devel kernel-headers

Product:

[Fedora] Fedora

Reporter:

Chris Murphy <bugzilla>

Component:

dnf

Assignee:

Packaging Maintenance Team <packaging-team-maint>

Status:

CLOSED DUPLICATE

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

unspecified

Docs Contact:

Priority:

low

Version:

CC:

akozumpl, bugzilla, packaging-team-maint, pnemade, rholy

Target Milestone:

---

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-01-29 12:33:15 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:

Attachments:

Description	Flags
strace	none

Description Chris Murphy 2014-01-28 22:22:50 UTC

Description of problem:
Currently running kernel-3.13.0-1.fc21.x86_64 and I want to install kernel-devel and kernel-headers; download them from koji and use dnf install *rpm. dnf reports there's nothing to do.

Version-Release number of selected component (if applicable):
dnf-0.4.12-1.fc20.noarch
hawkey-0.4.8-1.fc20.x86_64
kernel-3.13.0-1.fc21.x86_64

How reproducible:
Always

Steps to Reproduce:
0. Booted kernel-3.13.0-1.fc21.x86_64, with kernel-devel-3.13.0-1.fc21.x86_64.rpm and kernel-headers-3.13.0-1.fc21.x86_64.rpm in ~
1. # dnf install kernel-devel-3.13.0-1.fc21.x86_64.rpm kernel-headers-3.13.0-1.fc21.x86_64.rpm 

Actual results:

Error: Nothing to do.

Expected results:

Install packages


Additional info:
# rpm -qa kernel\*
kernel-3.13.0-1.fc21.x86_64
kernel-3.11.10-301.fc20.x86_64
kernel-modules-extra-3.11.10-301.fc20.x86_64
kernel-modules-extra-3.12.8-300.fc20.x86_64
kernel-3.12.8-300.fc20.x86_64

Comment 1 Chris Murphy 2014-01-28 22:24:58 UTC

Using --debugsolver produces no folder to troubleshoot. Will attach strace.

Comment 2 Chris Murphy 2014-01-28 22:25:37 UTC

Created attachment 856858 [details]
strace

strace dnf install kernel-devel-3.13.0-1.fc21.x86_64.rpm kernel-headers-3.13.0-1.fc21.x86_64.rpm

Comment 3 Chris Murphy 2014-01-28 22:29:32 UTC

The system is in a vbox VM which was paused for ~30 minutes prior to downloading files from koji and running the dnf command. journal reports the following:


Jan 28 14:50:44 f20v.localdomain systemd[1]: Starting dnf makecache...
Jan 28 14:50:44 f20v.localdomain dnf[1721]: Config time: 0.037
Jan 28 14:50:44 f20v.localdomain dnf[1721]: cachedir: /var/cache/dnf/x86_64/20
Jan 28 14:50:44 f20v.localdomain dnf[1721]: dnf version: 0.4.12
Jan 28 14:50:44 f20v.localdomain dnf[1721]: Making cache files for all metadata files.
Jan 28 14:50:44 f20v.localdomain dnf[1721]: Metadata cache refreshed recently.
Jan 28 14:50:44 f20v.localdomain systemd[1]: Started dnf makecache.
Jan 28 14:54:59 f20v.localdomain chronyd[400]: Can't synchronise: no majority
Jan 28 14:55:02 f20v.localdomain chronyd[400]: Selected source 129.250.35.250
Jan 28 14:55:02 f20v.localdomain chronyd[400]: System clock wrong by 458.604666 seconds, adjustment started
Jan 28 14:55:44 f20v.localdomain systemd[1]: Starting Cleanup of Temporary Directories...
Jan 28 14:55:44 f20v.localdomain systemd[1]: Started Cleanup of Temporary Directories.
Jan 28 14:56:02 f20v.localdomain chronyd[400]: Selected source 23.227.161.103
Jan 28 14:56:02 f20v.localdomain chronyd[400]: System clock wrong by 601.157990 seconds, adjustment started
Jan 28 14:56:03 f20v.localdomain chronyd[400]: Selected source 155.101.3.115
Jan 28 14:56:03 f20v.localdomain chronyd[400]: System clock wrong by 105.915191 seconds, adjustment started
Jan 28 14:56:04 f20v.localdomain chronyd[400]: Selected source 162.243.243.206
Jan 28 14:56:04 f20v.localdomain chronyd[400]: System clock wrong by 1.445572 seconds, adjustment started
Jan 28 14:56:07 f20v.localdomain chronyd[400]: Selected source 129.250.35.250
Jan 28 14:56:07 f20v.localdomain chronyd[400]: System clock wrong by -17.381687 seconds, adjustment started
Jan 28 14:57:07 f20v.localdomain chronyd[400]: Selected source 23.227.161.103
Jan 28 14:57:07 f20v.localdomain chronyd[400]: System clock wrong by 190.353633 seconds, adjustment started
Jan 28 14:57:08 f20v.localdomain chronyd[400]: Selected source 155.101.3.115
Jan 28 14:57:08 f20v.localdomain chronyd[400]: System clock wrong by 114.984167 seconds, adjustment started
Jan 28 14:57:12 f20v.localdomain chronyd[400]: Selected source 129.250.35.250
Jan 28 14:57:12 f20v.localdomain chronyd[400]: System clock wrong by -113.503781 seconds, adjustment started
Jan 28 14:58:11 f20v.localdomain chronyd[400]: Selected source 23.227.161.103
Jan 28 14:58:11 f20v.localdomain chronyd[400]: System clock wrong by 142.631107 seconds, adjustment started
Jan 28 14:58:13 f20v.localdomain chronyd[400]: Selected source 162.243.243.206
Jan 28 14:58:13 f20v.localdomain chronyd[400]: System clock wrong by -180.038029 seconds, adjustment started
Jan 28 14:58:16 f20v.localdomain chronyd[400]: Selected source 129.250.35.250
Jan 28 14:58:16 f20v.localdomain chronyd[400]: System clock wrong by 78.435731 seconds, adjustment started
Jan 28 14:59:17 f20v.localdomain chronyd[400]: Selected source 23.227.161.103
Jan 28 14:59:17 f20v.localdomain chronyd[400]: System clock wrong by 252.167850 seconds, adjustment started
Jan 28 14:59:18 f20v.localdomain chronyd[400]: Selected source 155.101.3.115
Jan 28 14:59:18 f20v.localdomain chronyd[400]: System clock wrong by -147.403118 seconds, adjustment started
Jan 28 14:59:21 f20v.localdomain chronyd[400]: Selected source 129.250.35.250
Jan 28 14:59:21 f20v.localdomain chronyd[400]: System clock wrong by -146.000536 seconds, adjustment started
Jan 28 15:00:21 f20v.localdomain chronyd[400]: Selected source 162.243.243.206
Jan 28 15:00:21 f20v.localdomain chronyd[400]: System clock wrong by -186.540360 seconds, adjustment started
Jan 28 15:01:01 f20v.localdomain systemd[1]: Starting Session 2 of user root.
Jan 28 15:01:01 f20v.localdomain systemd[1]: Started Session 2 of user root.
Jan 28 15:01:01 f20v.localdomain dbus-daemon[376]: dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":
Jan 28 15:01:01 f20v.localdomain dbus-daemon[376]: dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":
Jan 28 15:01:01 f20v.localdomain dbus-daemon[376]: dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":
Jan 28 15:01:01 f20v.localdomain dbus-daemon[376]: dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":
Jan 28 15:01:01 f20v.localdomain dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.32" (uid=42 pid=
Jan 28 15:01:01 f20v.localdomain dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.30" (uid=42 pid=
Jan 28 15:01:01 f20v.localdomain CROND[1775]: (root) CMD (run-parts /etc/cron.hourly)
Jan 28 15:01:01 f20v.localdomain dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.32" (uid=42 pid=
Jan 28 15:01:01 f20v.localdomain dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.30" (uid=42 pid=
Jan 28 15:01:01 f20v.localdomain run-parts[1778]: (/etc/cron.hourly) starting 0anacron
Jan 28 15:01:01 f20v.localdomain run-parts[1784]: (/etc/cron.hourly) finished 0anacron
Jan 28 15:01:01 f20v.localdomain run-parts[1786]: (/etc/cron.hourly) starting mcelog.cron
Jan 28 15:01:01 f20v.localdomain run-parts[1790]: (/etc/cron.hourly) finished mcelog.cron
Jan 28 15:01:01 f20v.localdomain dbus-daemon[376]: dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":
Jan 28 15:01:01 f20v.localdomain dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.32" (uid=42 pid=
Jan 28 15:01:01 f20v.localdomain dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.30" (uid=42 pid=
Jan 28 15:01:01 f20v.localdomain dbus-daemon[376]: dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":
Jan 28 15:01:01 f20v.localdomain dbus-daemon[376]: dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":
Jan 28 15:01:01 f20v.localdomain dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.32" (uid=42 pid=
Jan 28 15:01:01 f20v.localdomain dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.30" (uid=42 pid=
Jan 28 15:01:01 f20v.localdomain dbus-daemon[376]: dbus[376]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":
Jan 28 15:01:27 f20v.localdomain chronyd[400]: Selected source 23.227.161.103


The previously attached strace also contains many unexpected time related messages:

clock_gettime(CLOCK_MONOTONIC, {1505, 364644937}) = 0

Comment 4 Chris Murphy 2014-01-28 23:01:33 UTC

Poweroff VM, quite vbox, restart, same message:

# dnf -d10 --debugsolver install *rpm
Config time: 0.050
cachedir: /var/cache/dnf/x86_64/20
dnf version: 0.4.12
Command: dnf -d10 --debugsolver install kernel-devel-3.13.0-1.fc21.x86_64.rpm kernel-headers-3.13.0-1.fc21.x86_64.rpm 
Installroot: /
Base command: install
Extra commands: ['kernel-devel-3.13.0-1.fc21.x86_64.rpm', 'kernel-headers-3.13.0-1.fc21.x86_64.rpm']
repo: using cache for: fedora
not found deltainfo for: Fedora 20 - x86_64
repo: using cache for: updates
hawkey sack setup time: 0.709
Error: Nothing to do.

Comment 5 Chris Murphy 2014-01-28 23:14:29 UTC

Succeeds with yum, and there were a bunch of dependencies that also needed to be installed that for some reason dnf isn't picking up.

Comment 6 Ales Kozumplik 2014-01-29 07:15:18 UTC

(In reply to Chris Murphy from comment #1)
> Using --debugsolver produces no folder to troubleshoot. Will attach strace.

Without it we have no chance of debugging this. Can you please try again and then look in the CWD for a folder called debugdata? (if you run DNF through sudo it might be only root readable).

Thanks.

Comment 7 Chris Murphy 2014-01-29 08:38:35 UTC

Tried at least a dozen times, always as root. Also tried dnf clean all.

Comment 8 Ales Kozumplik 2014-01-29 08:47:39 UTC

that means the first step here will be generating a message where the debuginfo is stored.

Comment 9 Ales Kozumplik 2014-01-29 12:33:15 UTC

Hm, I see what is happening now, this is a dupe of bug 1056400.

*** This bug has been marked as a duplicate of bug 1056400 ***

Comment 10 Chris Murphy 2014-01-29 18:41:54 UTC

(In reply to Ales Kozumplik from comment #9)
> Hm, I see what is happening now, this is a dupe of bug 1056400.

The rpm files were locally stored in ~, downloaded from koji using curl, so I don't see how bug 1056400 "url installation" applies to this bug.

Comment 11 Ales Kozumplik 2014-01-30 07:37:58 UTC

(In reply to Chris Murphy from comment #10)
> (In reply to Ales Kozumplik from comment #9)
> > Hm, I see what is happening now, this is a dupe of bug 1056400.
> 
> The rpm files were locally stored in ~, downloaded from koji using curl, so
> I don't see how bug 1056400 "url installation" applies to this bug.

Don't take our word for it, test with the nightlies: http://dnf.baseurl.org/2014/01/29/nightly-builds-of-dnf-available/