Bug 2265671

Summary:	systemd presets request - waagent.service
Product:	[Fedora] Fedora	Reporter:	Jeremy Cline <jeremy>
Component:	fedora-release	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	alciregi, davdunc, fedoraproject, kevin, mboddu, ngompa13, pbrobinson, samyak.jn11, sgallagh, thrcka, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	fedora-release-40-0.37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-03-23 00:24:21 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 Jeremy Cline 2024-02-23 14:57:41 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.

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

It does not. However, like other guest agents, it does attempt to connect to a TCP endpoint provided by the host for deployment and topology configuration (in addition to reading from a boot-time attached DVD). This is similar to the google-guest-agent.service (https://bugzilla.redhat.com/show_bug.cgi?id=1926331) and other guest agents.

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

No, it continues to run.

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

waagent.service

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

All deliverables.

Comment 1 Stephen Gallagher 2024-02-27 20:35:30 UTC

(In reply to Jeremy Cline from comment #0)
> * Does the service listen on a network socket for connections originating on
> a separate physical or virtual machine?
> 
> It does not. However, like other guest agents, it does attempt to connect to
> a TCP endpoint provided by the host for deployment and topology
> configuration (in addition to reading from a boot-time attached DVD). This
> is similar to the google-guest-agent.service
> (https://bugzilla.redhat.com/show_bug.cgi?id=1926331) and other guest agents.
> 

OK, similar to https://bugzilla.redhat.com/show_bug.cgi?id=1926331 this cannot be auto-approved because it receives configuration from a remote source. As such, it requires FESCo approval (which I expect it will be granted).

I've opened https://pagure.io/fesco/issue/3176 with FESCo to get this reviewed.

Comment 2 Jeremy Cline 2024-02-28 16:25:44 UTC

Thanks.

Since it looks like all this has happened before, in an effort to ensure all this doesn't happen again I submitted https://src.fedoraproject.org/rpms/fedora-release/pull-request/318

Comment 3 Fedora Update System 2024-02-28 18:21:40 UTC

FEDORA-2024-2ccb6da164 (fedora-release-40-0.37) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-2ccb6da164

Comment 4 Fedora Update System 2024-02-29 01:08:03 UTC

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

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

Comment 5 Fedora Update System 2024-03-23 00:24:21 UTC

FEDORA-2024-2ccb6da164 (fedora-release-40-0.37) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.