| Summary: | [QA 2.6 M1 rc1 ][Build Appliance]: proxy issue in VM ware | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Runtime | Reporter: | pankaj yadav <pankaj-y> |
| Component: | build-appliance | Assignee: | Anuj Mittal <anuj.mittal> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | nagarajagopalx.velu |
| Version: | 2.6 | ||
| Target Milestone: | 2.6 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Used to work) |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
pankaj yadav
2018-06-20 13:09:21 UTC
STATUS - FAILED ENVIRONMENT - VMWare(14.1.1) on Ubuntu OS (16.04) BUILD: 2.6_M1.rc1 - ddbd7b0cd6580ee26e11aa87e426fb294b372d64 STEPS TO REPRODUCE : - Boot the build appliance image in VMWare - configure the proxy setting, export http_proxy=http://proxy.png.intel.com:911 export https_proxy=https://proxy.png.intel.com:911 export ftp_proxy=http://proxy.png.intel.com:911 export socks_server=proxy.png.intel.com:1080 export ALL_PROXY=socks://proxy.png.intel.com:1080 - run "bitbake core-image-minimal" ACTUAL RESULT: Getting below error, WARNING: Host distribution "poky-2.5+snapshot-20180607" has not been validated with this version of the build system; you may possibly experience unexpected failure. It is recommended that you use a tested distribution. ERROR: OE-core's config sanity checker detected a potential misconfiguraition. 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: Fetcher failure for URL: 'https://www.example.com/' . URL https://www.example.com/ doesn't work. Please ensure your host's network is configured correctly. or set BB_NO_NETWORK = "1" to disable network access if all required sources are on local disk. Summary: There was 1 WARNING message shown Summary: There was 1 ERROR message shown, returning a non-zero exit code. EXPECTED RESULT : "bitbake core-image-minimal" should run and build successfully. REGRESSION : Regression done with 2.4.3.rc2 and 2.5. Both these images booted in VMWare and proxy can be configured. bitbake core-image-minimal is running successfully. The problem is that we're passing a static IP using ip= from the kernel command line. So, if we do a 'ip set link eth0 down' and then 'up' after the image is up, eth0 should get ip using dhcp and network would work again. The change in behavior happened because of a change I had done that had enabled qemux86-directdisk.wks instead of directdisk.wks for qemux86* images. build-appliance-image with qemux86-64 MACHINE type uses this wks as well and as a result, isn't able to set the IP correct when booting up. I will change this to not pass the static IP. |