Bug 9109

Summary: Apply sleep 0.5 to other database operations
Product: [Build System, Metadata & Runtime] Toaster Reporter: Belen Barros Pena <belen.barros.pena>
Component: toasterAssignee: Toaster default assignee <toaster>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium CC: belen.barros.pena, david.reyna, jessica.zhang, jose.perez.carranza, stanciux.mihail
Version: 2.0   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

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..."