Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1791758

Summary: avoid warning from systemd for nm-cloud-setup.service using unsupported settings
Product: Red Hat Enterprise Linux 8 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Thomas Haller <thaller>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.2CC: acardace, atragler, bgalvani, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.22.6-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:54:11 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:

Description Thomas Haller 2020-01-16 12:37:46 UTC 
The upstream nm-cloud-setup.service unit ([1]) contains various flags that are not supported by systemd in rhel-8.2. That causes warnings:

Jan 15 11:43:48 ip-10-0-0-79.eu-west-1.compute.internal systemd[1]: /usr/lib/systemd/system/nm-cloud-setup.service:24: Unknown lvalue 'ProtectHostname' in section 'Service'
Jan 15 11:43:48 ip-10-0-0-79.eu-west-1.compute.internal systemd[1]: /usr/lib/systemd/system/nm-cloud-setup.service:25: Unknown lvalue 'ProtectKernelLogs' in section 'Service'
Jan 15 11:43:48 ip-10-0-0-79.eu-west-1.compute.internal systemd[1]: /usr/lib/systemd/system/nm-cloud-setup.service:32: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'


Those settings should be disabled on rhel-8.2.


[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/b1b69c1c7b77dfcacb942fe9f6bca5f56593230f/clients/cloud-setup/nm-cloud-setup.service.in#L16
Comment 1 Thomas Haller 2020-01-16 12:51:16 UTC 
pushed to dist-git. The package build is at the moment still waiting to collect more changes...
Comment 3 Vladimir Benes 2020-02-12 17:03:07 UTC 
device_reapply_routes test altered to do reapply when the DHCP request is not yet done. This showed the bug and also shows the bug fix now.
Comment 4 Vladimir Benes 2020-02-12 17:05:58 UTC 
(In reply to Vladimir Benes from comment #3)
> device_reapply_routes test altered to do reapply when the DHCP request is
> not yet done. This showed the bug and also shows the bug fix now.

wrong bug, sorry
Comment 5 Vladimir Benes 2020-02-19 17:01:03 UTC 
with 1.22.4-1
Feb 19 11:58:52 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com systemd[1]: /usr/lib/systemd/system/nm-cloud-setup.service:24: Unknown lvalue 'ProtectHostname' in section 'Service'
Feb 19 11:58:52 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com systemd[1]: /usr/lib/systemd/system/nm-cloud-setup.service:25: Unknown lvalue 'ProtectKernelLogs' in section 'Service'
Feb 19 11:58:52 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com systemd[1]: /usr/lib/systemd/system/nm-cloud-setup.service:32: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'


with 1.22.6-1
Feb 19 11:48:03 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com nm-cloud-setup[57610]: [92286.08181] <debug> nm-cloud-setup 1.22.6-1.el8 starting...
Feb 19 11:48:03 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com nm-cloud-setup[57610]: [92286.08187] <debug> start detecting ec2 provider...
Feb 19 11:48:03 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com nm-cloud-setup[57610]: [92286.08188] <debug> http-request[494c674988234290, "http://169.254.169.254/latest/meta-data/"]: start get ...
Feb 19 11:48:06 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com nm-cloud-setup[57610]: [92289.08196] <debug> http-request[494c674988234290, "http://169.254.169.254/latest/meta-data/"]: failed with HTTP request timed >
Feb 19 11:48:07 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com nm-cloud-setup[57610]: [92290.08200] <debug> http-request[6549bce98041260c, "http://169.254.169.254/latest/meta-data/"]: start get ...
Feb 19 11:48:10 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com nm-cloud-setup[57610]: [92293.08197] <trace> http-request[6549bce98041260c, "http://169.254.169.254/latest/meta-data/"]: cancelled
Feb 19 11:48:10 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com nm-cloud-setup[57610]: [92293.08198] <info>  provider ec2 not detected: failure to detect EC2 metadata
Feb 19 11:48:10 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com nm-cloud-setup[57610]: [92293.08198] <info>  no provider detected
Feb 19 11:48:10 gsm-r6s14-01.wlan.rhts.eng.bos.redhat.com systemd[1]: Started Automatically configure NetworkManager in cloud.


no errors visible
Comment 7 errata-xmlrpc 2020-04-28 16:54:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1847