Bug 15395 - Update Layer button does not display logs and creates two Update records in the database
Summary: Update Layer button does not display logs and creates two Update records in t...
Status: NEW
Alias: None
Product: Layer Index
Classification: Yocto Project Subprojects
Component: Layer Index (show other bugs)
Version: 5.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 6.2
Assignee: Tim Orling
QA Contact: apoorv sangal
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2024-02-09 16:02 UTC by Tim Orling
Modified: 2026-10-27 04:39 UTC (History)
0 users

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Orling 2024-02-09 16:02:09 UTC
When you click on the Update Layer button, e.g. for meta-maker, you see the Task View page but no dynamic log is displayed. Perhaps only when the task completes very quickly, the Success is also not detected.

Previously, the Update Layer button would launch a task view that showed nothing because the layerscelery container on the server did not have the database credentials. This has now been fixed.

From the admin interface, we can see that two Update records are created:

The first one is the actual task and shows the log:
https://layers.openembedded.org/admin/layerindex/update/39273/change/

which shows a proper task view after the fact:
https://layers.openembedded.org/layerindex/task/3ff5cb35-3c45-45f3-b973-353a0763502e/

The second one is empty with no task id and no record of what triggered it:
https://layers.openembedded.org/admin/layerindex/update/39274/change/

The update command is run in
https://git.yoctoproject.org/layerindex-web/tree/layerindex/tasks.py#n40

The update is generated in:
https://git.yoctoproject.org/layerindex-web/tree/layerindex/views.py#n125

Also, we should should double check that the lock is being respected/checked for. If a systemd timer/cronjob update is already running, we should queue the task and wait until the lock is freed. Some UI indication of the wait would be nice.