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.
Created attachment 1729145[details]
Proposed fix for issue.
Description of problem:
cloud-final.service wil fail if NetworkManager is not installed.
journal -u cloud-final.service would show:
cloud-init[5328]: Cloud-init v. 19.4 finished at ...
echo[5346]: try restart NetworkManager.service
systemctl[5349]: Failed to reload-or-try-restart
NetworkManager.service: Unit not found.
systemd[1]: cloud-final.service: control process exited,
code=exited status=5
systemd[1]: Failed to start Execute cloud user/final scripts.
systemd[1]: Unit cloud-final.service entered failed state.
systemd[1]: cloud-final.service failed.
Note that both of 'try-reload-or-restart' and 'reload-or-try-restart'
will fail if the service is not present. So this would also
affect rhel 8 systems that do not use NetworkManager.
Version-Release number of selected component (if applicable): cloud-init-19.4-7.el7_7
How reproducible: Always
Just for the record, the same problem will occur in rhel 8.
Both both of 'try-reload-or-restart' and 'reload-or-try-restart'
will exit non-zero if the service provided is not present.
For the record, as we already agreed on IRC on that, this is a very specific corner case as RHEL is always shipped with NetworkManager. The chance of having a customer running into this problem if very unlikely. This won't be fixed for RHEL-7.9 but I'll add as a lower priority for RHEL-8.
Thanks for reporting that!
(In reply to Joerg Lehmann from comment #4)
> Just experienced this same problem when updating to CentOS 7.9.2009 on a
> Hetzner Cloud Server. This is not really a "specific corner case", IMHO :-)
Sure we can reopen this BZ in this case. As you mentioned on BZ#1829713, you do have NM installed and you're still facing this issue. Can you post the logs?
I do not have NM installed. This explains the error, not sure why there is no RPM-dependency to NM if it is required though. It's not a big deal, but to have failed services after a normal update is just not so nice.
(In reply to Joerg Lehmann from comment #7)
> I do not have NM installed. This explains the error, not sure why there is
> no RPM-dependency to NM if it is required though. It's not a big deal, but
> to have failed services after a normal update is just not so nice.
Agreed. I'll raise the priority on this one and will fix on the coming week.
Thanks for sharing the bug!
Comment 10Giedrius Tuminauskas
2020-12-20 11:10:18 UTC
(In reply to Eduardo Otubo from comment #3)
> For the record, as we already agreed on IRC on that, this is a very specific
> corner case as RHEL is always shipped with NetworkManager. The chance of
> having a customer running into this problem if very unlikely. This won't be
> fixed for RHEL-7.9 but I'll add as a lower priority for RHEL-8.
>
> Thanks for reporting that!
FYI: CentOS-7-x86_64-GenericCloud-yymm.qcow2 images have been shifted without NetworkManager.
There are hundreds of such VMs in the cloud infrastructure, and suddenly after upgrading from 7.x to 7.9, somebody decided to add dependency for NM, which was not present all the time. Does not sound fair
Comment 13Jukka Nousiainen
2021-05-12 12:27:30 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 (cloud-init bug fix and enhancement update), 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-2021:2810
Created attachment 1729145 [details] Proposed fix for issue. Description of problem: cloud-final.service wil fail if NetworkManager is not installed. journal -u cloud-final.service would show: cloud-init[5328]: Cloud-init v. 19.4 finished at ... echo[5346]: try restart NetworkManager.service systemctl[5349]: Failed to reload-or-try-restart NetworkManager.service: Unit not found. systemd[1]: cloud-final.service: control process exited, code=exited status=5 systemd[1]: Failed to start Execute cloud user/final scripts. systemd[1]: Unit cloud-final.service entered failed state. systemd[1]: cloud-final.service failed. Note that both of 'try-reload-or-restart' and 'reload-or-try-restart' will fail if the service is not present. So this would also affect rhel 8 systems that do not use NetworkManager. Version-Release number of selected component (if applicable): cloud-init-19.4-7.el7_7 How reproducible: Always