Bug 12804 - [QA 2.6 M1 rc1 ][Build Appliance]: proxy issue in VM ware
Summary: [QA 2.6 M1 rc1 ][Build Appliance]: proxy issue in VM ware
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Build System, Metadata & Runtime
Component: build-appliance (show other bugs)
Version: 2.6
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.6 M3
Assignee: Anuj Mittal
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-06-20 13:09 UTC by pankaj yadav
Modified: 2018-08-02 23:21 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pankaj yadav 2018-06-20 13:09:21 UTC
Test Case ID : https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=340

Description :
core-image-minimal is succesfully builded in Previous release (2.4.3.rc2) with proxy setting.
2.6_M1.rc1 is not building the core-image-minimal , attached error log file.
wget g.co is not working with proxy configuration in 2.6_M1.rc1 build appliance image.
We will compile build-appliance-image using 2.6_M1.rc1 commit id and try to boot in VM ware , and run the test cases.

Please find the logs for the same :
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.
Comment 1 nagarajagopal 2018-06-21 09:02:40 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.
Comment 2 Anuj Mittal 2018-06-22 08:41:36 UTC
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.