Bug 1995495

Summary:	systemd presets request - rpm-ostree-countme.timer
Product:	[Fedora] Fedora	Reporter:	Timothée Ravier <travier>
Component:	fedora-release	Assignee:	Mohan Boddu <mboddu>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	fedoraproject, jkeating, jlebon, kellin, kevin, mboddu, pbrobinson, sgallagh, thrcka, zbyszek
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	fedora-release-34-37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-15 18:20:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Timothée Ravier 2021-08-19 09:14:05 UTC

* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)?

No, uses the existing repository configuration as is.

* Does the service listen on a network socket for connections originating on a separate physical or virtual machine?

No, connections are outgoing.

* Is the service non-persistent (i.e. run once at startup and exit)?

No, this is a timer for a recurring even.

* What is the exact name (or names) of the systemd unit files to be enabled?

rpm-ostree-countme.timer

* Is this request for all Fedora deliverables or only for some Editions (list them)?

This is for all rpm-ostree based Fedora variants, thus applies to IoT, Silverblue/Kinoite, CoreOS.
This will only be enabled on systems where rpm-ostree is installed (only rpm-ostree based systems right now).
The timer unit is also conditioned with a check that it is running on an rpm-ostree based system and the binary itself also perform the same check.

Comment 1 Timothée Ravier 2021-08-19 09:27:18 UTC

This is mostly a tracking issue for the following PRs:

- Rawhide PR: https://src.fedoraproject.org/rpms/fedora-release/pull-request/199
- F35 & F34 PR in progress

See also:

- https://fedoraproject.org/wiki/Changes/DNF_Better_Counting
- https://github.com/coreos/fedora-coreos-tracker/issues/717
- https://fedoramagazine.org/getting-better-at-counting-rpm-ostree-based-systems/

Existing implementation:

- https://src.fedoraproject.org/rpms/fedora-release/pull-request/173
- https://src.fedoraproject.org/rpms/fedora-release/pull-request/182

Comment 2 Timothée Ravier 2021-08-24 15:41:02 UTC

F35: https://src.fedoraproject.org/rpms/fedora-release/pull-request/200

Comment 3 Timothée Ravier 2021-08-30 17:33:33 UTC

Won't make a PR for F34 as we don't strictly need it.

Comment 4 Timothée Ravier 2021-09-13 10:42:48 UTC

Had to make one for 34 as we need it for IoT: https://src.fedoraproject.org/rpms/fedora-release/pull-request/203

Comment 5 Fedora Update System 2021-09-13 12:00:17 UTC

FEDORA-2021-49e1ee35b2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-49e1ee35b2

Comment 6 Fedora Update System 2021-09-13 14:29:24 UTC

FEDORA-2021-49e1ee35b2 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-49e1ee35b2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-49e1ee35b2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2021-09-15 18:20:12 UTC

FEDORA-2021-49e1ee35b2 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.