Bug 2263304 - IoT Simplified Provisioning
Summary: IoT Simplified Provisioning
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Whalen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F40Changes
TreeView+ depends on / blocked
 
Reported: 2024-02-08 08:58 UTC by Aoife Moloney
Modified: 2024-04-29 09:29 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-04-29 09:29:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Aoife Moloney 2024-02-08 08:58:03 UTC
This is a tracking bug for Change: IoT Simplified Provisioning
For more details, see: https://fedoraproject.org/wiki/Changes/IoTSimplifiedProvisioning

Offer Fedora IoT users a new, non-release blocking deliverable to deploy and configure Fedora IoT systems using a new tool called Simplified Provisioning.

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 Adam Williamson 2024-02-21 06:26:38 UTC
Can we have an update on the status of this Change? We are past the "testable" deadline at which it should be implemented sufficiently to be testable. Please set the bug to MODIFIED if it is "testable", or ON_QA if it is "100% complete". Thanks.

Comment 2 Paul Whalen 2024-02-21 15:01:24 UTC
> Can we have an update on the status of this Change? We are past the
> "testable" deadline at which it should be implemented sufficiently to be
> testable. Please set the bug to MODIFIED if it is "testable", or ON_QA if it
> is "100% complete". Thanks.

This change is now testable in Koji by submitting manual builds, we still need a small patch to Pungi to have it included in our composes.

Comment 3 Aoife Moloney 2024-04-29 09:29:27 UTC
F40 was released on 2024-04-23, 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.