Bug 1809407

Summary:	earlyoom.service resets to disabled
Product:	[Fedora] Fedora	Reporter:	Chris Murphy <bugzilla>
Component:	earlyoom	Assignee:	Vitaly <vitaly>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	vitaly
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	earlyoom-1.4-2.fc31	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-04 21:31: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:
Bug Depends On:	1809408
Bug Blocks:

Description Chris Murphy 2020-03-03 05:00:59 UTC

Loaded: loaded (/usr/lib/systemd/system/earlyoom.service; disable; vendor preset: disabled)

earlyoom-1.4-1.fc31.x86_64

Previousy I had 1.3.1 enabled, and after updating and reboot, it's not running, and for some reason it's been reset back to disabled.

Comment 1 Vitaly 2020-03-03 09:01:20 UTC

Related to 1809408. Unit file was accidentally changed and systemd reset it to its default state.

Comment 2 Fedora Update System 2020-03-03 20:28:08 UTC

earlyoom-1.4-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4820400ce8

Comment 3 Fedora Update System 2020-03-04 21:31:15 UTC

earlyoom-1.4-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.