Bug 7592 - No detailed explanation of a sanity checker connectivity issue
Summary: No detailed explanation of a sanity checker connectivity issue
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: configuration (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.9 M1
Assignee: Mariano Lopez
QA Contact: Cristina Agurida
URL:
Whiteboard: Backport to daisy and dizzy
Depends on:
Blocks:
 
Reported: 2015-04-09 15:40 UTC by Laszlo Papp
Modified: 2015-10-21 14:19 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laszlo Papp 2015-04-09 15:40:04 UTC
Our setup seems to have been working fine with dylan, but once we try to migrate to daisy, it seems that we face this issue;

bitbake foo-core-image
Pseudo is not present but is required, building this first before the main build
WARNING: Host distribution "Debian-7.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Failed to fetch test data from the network. Please ensure your network is configured correctly.

ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1

Summary: There was 1 WARNING message shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

I do not know why this is appearing as the setup used to work with dylan and that has not changed. Either way, some more explanation about the exact issue would be nice!
Comment 1 Paul Eggleton 2015-04-17 16:23:42 UTC
To clarify, there are two problems here based on IRC discussion with Laszlo and some investigation:

1) The sanity error doesn't tell you which URL failed to fetch nor how it failed, so we should change it so it does show that information.

2) The trigger for this was Laszlo was using a copied and modified poky.conf from an older release with a previous value of CONNECTIVITY_CHECK_URIS that still included a git:// URI (we removed it some time ago in http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=029a74407836390acc29201309130e3860caf072 ). This shouldn't have been an issue, except it appears that the old git URI ("git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=HEAD", which we still show as an example within poky.conf) no longer works - our call to 'git ls-remote' when rev=HEAD doesn't return anything. That seems like it might be a bug; if it's not then at the very least we need to update the example in poky.conf.
Comment 3 Cristina Agurida 2015-10-21 14:19:56 UTC
The poky.conf file looks fine.
Verified on master: a9053ac0829eb01f6f002587854d01e47a78e6f0