Bug 2233245 - Automatic Cloud Reboot On Updates
Summary: Automatic Cloud Reboot On Updates
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Major Hayden 🤠
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F39Changes
TreeView+ depends on / blocked
 
Reported: 2023-08-21 19:10 UTC by Adam Williamson
Modified: 2023-11-14 18:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-14 18:57:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2023-08-21 19:10:58 UTC
This is a tracking bug for Change: Automatic Cloud Reboot On Updates
For more details, see: https://fedoraproject.org/wiki/Changes/Automatic_Cloud_Reboot_On_Updates

Cloud users can provide cloud-init metadata when creating a Fedora cloud instance and that metadata can contain instructions to update all packages on the system and reboot the system if any of those updated packages need a reboot to go into effect. Fedora cloud instances should write the /var/run/reboot-required file if a reboot is needed after a dnf update so that cloud-init can reboot the instance.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Major Hayden 🤠 2023-08-21 19:30:58 UTC
This one is in F39/F40 already, but to test it, you would need to update a package that would require a service restart or a full instance restart... 🤔

Comment 2 Adam Williamson 2023-08-22 21:58:47 UTC
Still, that means it's fully implemented, so I think ON_QA is the appropriate status. (I don't think POST formally *means* anything for a Change tracker bug).

Comment 3 Aoife Moloney 2023-11-14 18:57:27 UTC
F39 was released on November 7th, so I am closing this tracker. If this Change was not completed, please notify me ASAP.


Note You need to log in before you can comment on or make changes to this bug.