Bug 14661 - [meta-aws] 245200 check-layer-nightly meta-aws absent dependency
Summary: [meta-aws] 245200 check-layer-nightly meta-aws absent dependency
Status: RESOLVED WORKSFORME
Alias: None
Product: Other YP Layers
Classification: Build System, Metadata & Runtime
Component: layers (show other bugs)
Version: 3.1.14
Hardware: Other other
: Undecided normal
Target Milestone: ---
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2021-12-15 11:54 UTC by valery chernous
Modified: 2021-12-16 15:43 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description valery chernous 2021-12-15 11:54:19 UTC 
autobuilder task 245200 check-layer-nightly failed for release dunfell
https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/414/steps/6/logs/stdio

ERROR: Layer 'meta-aws' depends on layer 'meta-python', but this layer is not enabled in your configuration
ERROR: Layer 'meta-aws' depends on layer 'networking-layer', but this layer is not enabled in your configuration
ERROR: Layer 'meta-aws' depends on layer 'openembedded-layer', but this layer is not enabled in your configuration
ERROR: Parse failure with the specified layer added, aborting.

====================================================================================================
ERROR: Command . ./oe-init-build-env; bitbake-layers add-layer /home/pokybuild/yocto-worker/check-layer-nightly/build/meta-aws failed with exit code 1, see errors above. (1639447268.0)

Looks like task download layer to one place but add layer from other place
Cloning into '/home/pokybuild/yocto-worker/check-layer-nightly/build/repos/meta-aws'...

. ./oe-init-build-env; bitbake-layers add-layer /home/pokybuild/yocto-worker/check-layer-nightly/build/meta-aws
Comment 1 Randy MacLeod 2021-12-16 15:43:27 UTC 
This seems to be working now so we suspect that it has been fixed.