Bug 9109 - Apply sleep 0.5 to other database operations
Summary: Apply sleep 0.5 to other database operations
Status: NEW
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: Future
Assignee: Toaster default assignee
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-02-12 16:38 UTC by Belen Barros Pena
Modified: 2023-12-14 04:24 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2016-02-12 16:38:34 UTC 
The 'sleep 5' trick we are applying to the save operations works well to avoid database locking issues. It would be good to apply it to other operations, since we are seeing new locking issues in the image customisation section, particularly in the 'custom images' page, and potentially in the 'custom image details' page also.

This is what Brian Avery said: "we can extend ed's trick to the other operations but initially it would be nice to add his warning messages to them to see what/where it's happening.  If you aren't doing a build, the only thing poking the database is the bldcontroller. So, it would be nice to turn that off and see if it still happens. e,g, is it our multi access causing hte issue or something else..."