Bug 9118

Summary: Dead paths for meta-toaster-custom layer left behind in bblayers.conf
Product: [Build System, Metadata & Runtime] Toaster Reporter: Michael Wood <michael.g.wood>
Component: toasterAssignee: Toaster default assignee <toaster>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Low CC: belen.barros.pena, david.reyna, jessica.zhang, jose.perez.carranza, stanciux.mihail
Version: 2.1   
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 Michael Wood 2016-02-15 16:45:47 UTC
If you've got a build directory which you've previously used and it contains a bblayers.conf and you've got a (dynamically) created toaster-custom-images layer defined which doesn't exist the check on the path bitbake does will stop it from starting up.

ERROR: Traceback (most recent call last):
  File "/home/michael/dev/yocto/poky/bitbake/lib/bb/cookerdata.py", line 179, in wrapped
    return func(fn, *args)
  File "/home/michael/dev/yocto/poky/bitbake/lib/bb/cookerdata.py", line 201, in parse_config_file
    return bb.parse.handle(fn, data, include)
  File "/home/michael/dev/yocto/poky/bitbake/lib/bb/parse/__init__.py", line 113, in handle
    return h['handle'](fn, data, include)
  File "/home/michael/dev/yocto/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py", line 124, in handle
    abs_fn = resolve_file(fn, data)
  File "/home/michael/dev/yocto/poky/bitbake/lib/bb/parse/__init__.py", line 136, in resolve_file
    raise IOError(errno.ENOENT, "file %s not found" % fn)
IOError: [Errno 2] file /home/michael/dev/yocto/poky/_meta-toaster-custom/conf/layer.conf not found

ERROR: Unable to parse /home/michael/dev/yocto/poky/_meta-toaster-custom/conf/layer.conf: [Errno 2] file /home/michael/dev/yocto/poky/_meta-toaster-custom/conf/layer.conf not found
Bitbake server start failed
WARNING: Could not connect to server at 0.0.0.0:50216 ([Errno 111] Connection refused)
ERROR: Could not connect to server 0.0.0.0:50216
: [Errno 111] Connection refused