Bug 1120368 - dnf-makecache.service runs on traditional installer images, fails
Summary: dnf-makecache.service runs on traditional installer images, fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lorax
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-16 19:17 UTC by Adam Williamson
Modified: 2014-11-06 00:32 UTC (History)
5 users (show)

Fixed In Version: lorax-21.18-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-06 00:32:31 UTC


Attachments (Terms of Use)

Description Adam Williamson 2014-07-16 19:17:03 UTC
dnf is included in the installer environment, now. dnf ships:

/usr/lib/systemd/system/dnf-makecache.service
/usr/lib/systemd/system/dnf-makecache.timer

the timer is WantedBy=basic.target , so it's enabled by default. The timer runs the service ten minutes after boot, then every hour after that. The service tries to update dnf's metadata cache. In the installer environment, it fails.

Presuming we want to turn it off for the installer, I can think of a few options. anaconda could just disable the timer at some point during boot. lorax could strip the service and timer files out. Or the service could grow some kind of Condition to disable it in the installer environment - it already has:

ConditionKernelCommandLine=!rd.live.image

to stop it running in live environments, there are various Conditions that could be used somehow to disable it in the installer environment, though I don't know if any of them is entirely bulletproof (could check for stage2 on the cmdline, or the presence/absence of some particular file or directory that indicates strongly we're in the installer).


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