| Summary: | Custom images created from the build history pages fail to build | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Belen Barros Pena <belen.barros.pena> |
| Component: | toaster | Assignee: | David Reyna <david.reyna> |
| Status: | ACCEPTED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | belen.barros.pena, david.reyna, jessica.zhang, jose.perez.carranza, stanciux.mihail |
| Version: | unspecified | ||
| Target Milestone: | 5.99 | ||
| 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-04-20 14:09:22 UTC
I spent some time looking at this, but haven't resolved it. The issue might be that the base recipe you get if you create a custom image from the build dashboard is different from the base recipe if you create it from the "New custom image" page. For example, if I create a custom image from the "New custom image" page based on core-image-minimal, the base recipe ID is 8718. If I then build core-image-minimal, go to the build dashboard, and create a new custom image from there, the base recipe ID is 10626. My guess is that the recipes associated with a build are different from the ones associated with the project, and don't have the same layer information. (We use the recipes from the build when creating a new custom image from the build dashboard, but use the recipes from the project when creating one via the "New custom image" page.) The fix may be to retrieve the project recipes to populate the list of available recipes shown in the build dashboard new custom image popup. Bulk move from 4.99 or 0.00 to 5.99 |