Bug 7968 - empty page states for no information in the database
Summary: empty page states for no information in the database
Status: RESOLVED WONTFIX
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.9
Hardware: x86 Multiple
: Low normal
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard: GUI design pending
Depends on:
Blocks:
 
Reported: 2015-07-08 11:56 UTC by Alexandru Damian
Modified: 2018-10-04 12:39 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Damian 2015-07-08 11:56:22 UTC
It is possible, and a valid state, that Toaster starts running with no information in the database.

This happens commonly when setting it up as a service (not starting through normal scripts), or when importing information from the Layer Index or toaster config file fails (due to invalid config file, Layer Index being down, etc).

We need to have proper page designs and implementation for this situation.
Comment 1 Belen Barros Pena 2015-08-20 17:10:01 UTC
There should be empty states in place for all pages. That work was covered by bug 6755 (see the attached design document). 

This doesn't mean they cannot be improved. Maybe we can look into that during 2.1
Comment 2 David Reyna 2018-10-04 12:39:07 UTC
The Toaster manager should insure that the database is populated before deploying to other users. We should not need extra actions.