Bug 9385

Summary: After a project's initial image build of sato, building a custom minimal never shows packages
Product: [Build System, Metadata & Runtime] Toaster Reporter: Dave Lerner <dave.lerner>
Component: toasterAssignee: Toaster default assignee <toaster>
Status: VERIFIED NOTABUG QA Contact: Alexandru Roman <alexandru.costinx.roman>
Severity: normal    
Priority: Medium+ CC: belen.barros.pena, jessica.zhang, stanciux.mihail
Version: 2.1   
Target Milestone: 2.1 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Dave Lerner 2016-04-04 21:20:30 UTC
In clean disto, that is after fetching, rebasing I've done the following 3 times all with the same symptom, no package info after my first custom image build:

cd poky-install
   rm -rf /tmp/toast*
   rm -rf build
   rm -rf _toaster*
start toaster,
create a new project, myproject
select core-image-sato,
build core-image-sato,
select all projects,
pick myproject
click New Custom Image
name the project myminimal
select core-image-minimal
build core-image-minimal

Now either clicking All Builds, picking core-image-minimal, then packages or else
All Projects, myproject, then myminimal the pages say no package information available:
Either for custom project mymin
"Toaster has no package information for mymin...
or for All Builds mymin
"No packages were built. How did this happen...

This behaviour seems different than versions 4 weeks ago and after IRC with Elliot it doesn't seem like the expected/desired behaviour.
Comment 1 Dave Lerner 2016-04-04 21:27:20 UTC
Same results after 
Creating a second project 'proj2'.
Creating a new custom image based 'mysato' based on 'core-image-sato
Comment 2 Dave Lerner 2016-04-05 19:24:34 UTC
Actually a simpler case is
Create project
Create new custom image
BUild new custom image
All Projects | yourProject | yourCustomImage 
Then note that Add | Remove packages says "Toaster has not package info..."
Comment 3 Dave Lerner 2016-04-06 21:43:44 UTC
In toaster-next, [just to be sure doing this from scratch: 
git clone git://git.yoctoproject.org/poky-contrib && cd poky-contrib && git checkout toaster-next ]

after creating my project then either just building core-image-sato or core-image-minimal, the build runs for the usual duration but in the end I get the following 10 errors: 

Taskhash mismatch 146fdfa66c809a41885631aa604d5e13 verses 95d962d08cb8852d957996245ddad6d8 for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_rootfs

Taskhash mismatch 146fdfa66c809a41885631aa604d5e13 verses 95d962d08cb8852d957996245ddad6d8 for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_rootfs

Taskhash mismatch 3e4c1eeb5673f5813a2ab231223caea6 verses 0aa86511bc7a9d6d69847d745474c988 for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image

Taskhash mismatch 3e4c1eeb5673f5813a2ab231223caea6 verses 0aa86511bc7a9d6d69847d745474c988 for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image

Taskhash mismatch 79ee612b6d33281d18e0acd727758262 verses 51a2060b090976bea50ee66d0e62757a for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image_ext3

Taskhash mismatch 79ee612b6d33281d18e0acd727758262 verses 51a2060b090976bea50ee66d0e62757a for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image_ext3

Taskhash mismatch c6e2d3aef2203bd473ace95ea9b67b06 verses da961f8296f083c435481b5a3ef5dabb for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image_tar

Taskhash mismatch c6e2d3aef2203bd473ace95ea9b67b06 verses da961f8296f083c435481b5a3ef5dabb for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image_tar

Taskhash mismatch 7edda097bf7bed0cb7486e66595c7e5a verses e09e422c56cd3171d4473e8c999799ae for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image_jffs2


If I try to create a core-image-minimal custom image, I get the same failure.  After the custom image completes with errors, navigating to the Add / Remove page shows this defect's original symptom "Toaster has no package information for <my image name>..."

The toaster_ui.log claims to have exited with errorcode 0 even though the tail looks like:

ERROR: Taskhash mismatch 7edda097bf7bed0cb7486e66595c7e5a verses e09e422c56cd3171d4473e8c999799ae for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image_jffs2
NOTE: Logfile for task /ord-dlerner-d81/dlerner/git/poky-contrib/build/tmp/work/qemux86-poky-linux/min/1.0-r0/temp/log.do_image_jffs2.17858
NOTE: Logging error 2: {'lineno': 100, 'message': 'Taskhash mismatch 7edda097bf7bed0cb7486e66595c7e5a verses e09e422c56cd3171d4473e8c999799ae for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image_jffs2', 'pathname': '/ord-dlerner-d81/dlerner/git/poky-contrib/bitbake/lib/bb/__init__.py', 'build': <Build: 2 aproj (Release master (master), BBV master (Branch: master)) min>, 'level': 2}
ERROR: Taskhash mismatch 7edda097bf7bed0cb7486e66595c7e5a verses e09e422c56cd3171d4473e8c999799ae for /ord-dlerner-d81/dlerner/git/poky-contrib/build/toaster-custom-images/recipes/min.bb.do_image_jffs2
NOTE: Logfile for task /ord-dlerner-d81/dlerner/git/poky-contrib/build/tmp/work/qemux86-poky-linux/min/1.0-r0/temp/log.do_image_complete.17960
NOTE: Logfile for task /ord-dlerner-d81/dlerner/git/poky-contrib/build/tmp/work/qemux86-poky-linux/min/1.0-r0/temp/log.do_image_complete.17960
NOTE: Tasks Summary: Attempted 2075 tasks of which 2064 didn't need to be rerun and all succeeded.
NOTE: Build exited with errorcode 0
NOTE: ToasterUI build done 1, brbe: None
NOTE: ToasterUI build done 2

Is this the same original symptom but now the Taskhash mismatch errors  are printing?  The overt symptom of no package info is the same as the original defect.
Dav
Comment 4 Dave Lerner 2016-04-07 16:10:21 UTC
After rebasing again this morning, this problem is no longer reproducible.  Withdrawing.
Comment 5 Alexandru Roman 2016-04-28 11:00:57 UTC
Verified.