Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1844467 - WARNING no greenboot logs were found!
Summary: WARNING no greenboot logs were found!
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: greenboot
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Christian Glombek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: IoT
TreeView+ depends on / blocked
 
Reported: 2020-06-05 13:34 UTC by Paul Whalen
Modified: 2020-06-22 19:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-22 19:47:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul Whalen 2020-06-05 13:34:50 UTC
Description of problem:
Seeing this in yesterday's F33 IoT compose. It worked fine in the previous compose and it looks like a new build landed yesterday. 

https://openqa.stg.fedoraproject.org/tests/874142#

Version-Release number of selected component (if applicable):
greenboot-0.10.2-1.fc33

Working:
greenboot-0.9-2.fc33.noarch

Comment 1 Christian Glombek 2020-06-05 16:25:59 UTC
Weird. If this was on f32 I'd see why this is happening: https://src.fedoraproject.org/rpms/fedora-release/pull-request/129 would be the fix.
Can you verify the greenboot-task-runner service is enabled and ran?

Comment 2 Paul Whalen 2020-06-05 19:25:12 UTC
It's still disabled in F33, no new fedora-release build since the change.

Comment 4 Mohan Boddu 2020-06-05 20:20:42 UTC
Also fedora-release-32-3 is built https://koji.fedoraproject.org/koji/buildinfo?buildID=1521363

Please push it along with the greenboot build for f32.

Comment 5 Paul Whalen 2020-06-22 19:47:23 UTC
This was fixed with fedora-release-33-0.9.


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