Bug 8473

Summary: Parselogs error: Online check failed for 0xb77b2ab0 Wired on lsb image
Product: [Build System, Metadata & Runtime] BSPs Reporter: Cristina Agurida <cristina-danielax.agurida>
Component: bsps-runtimeAssignee: Saul Wold <sgw>
Status: VERIFIED WONTFIX QA Contact: Cristina Agurida <cristina-danielax.agurida>
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, georgex.l.musat, jku, yp.kernel.watcher, yp.watcher
Version: 1.8   
Target Milestone: 2.1   
Hardware: MinnowBoard Max   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: New (Never tested)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
daemon log none

Description Cristina Agurida 2015-10-09 13:03:57 UTC
STATUS: FAILED
BUILD: 1.8.1: b74ea963cefffad9fbd91d4eb9b240f6a8c86cd0
ENVIRONMENT: genericx86-lsb on Minnow Max
IMAGE: core-image-lsb-sdk

STEPS TO REPRODUCE: 
  
 Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc.
Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored.



EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

Actual outcome:

This error appears on /var/log//daemon.log :

genericx86 connmand[812]: Online check failed for 0xb77b2ab0 Wired
Comment 1 Cristina Agurida 2015-10-16 09:10:46 UTC
This error appears also on genericx86-64-lsb on NUC (model D54250WYK), core-image-lsb-sdk image.
Comment 2 Saul Wold 2015-10-19 16:41:21 UTC
Can you confirm if you had an ethernet cable plugged in at the time of this error?
Comment 3 Cristina Agurida 2015-10-20 10:48:58 UTC
Yes, the hardware was connected to the internet via DHCP. The iptables, sudoku and cvs tests download the archives from the internet, so the network worked for other tests.
Comment 4 Cristina Agurida 2015-10-20 10:52:12 UTC
Please set this back to NEEDINFO if there are more questions.
Comment 5 Alexandru Georgescu 2015-10-20 13:36:02 UTC
Same comment as bug 8526 Talked with Cristina, the board wasn't tested during 1.7, 1.7.1  and 1.7.2 point releases so this is not a regression!

Seems it also appears in 1.8. The issues appeared now since we deprecated the AtomPC HW and switched to MMAX32 boards for testing.
Comment 6 Saul Wold 2015-10-26 15:32:07 UTC
This could be related to being inside Intel Firewall and connman attempting to 
phone home.
Comment 7 Lucian Musat 2015-10-29 08:31:38 UTC
Created attachment 2831 [details]
daemon log
Comment 8 Lucian Musat 2015-10-29 08:33:18 UTC
Could not reproduce this at my desk, but I ran again the tests on the minnowmax in the lab and it's the same error. It could be the network configuration in the lab. I attached the daemon log if it helps.
Comment 9 Jussi Kukkonen 2015-10-29 11:52:53 UTC
(In reply to comment #6)
> This could be related to being inside Intel Firewall and connman attempting
> to 
> phone home.

Yes, that's what "online check failed" means: it's checking that
  A) connman.net responds and
  B) the http reply includes a special header

This message should be whitelisted if the machine is not expected to have a connection that allows the above: this has already been done on jethro I believe.
Comment 10 Lucian Musat 2015-10-29 14:43:55 UTC
Indeed this error is whitelisted in jethro and should be backported. I think this could be closed wontfix.
Comment 11 Saul Wold 2015-11-02 16:05:43 UTC
Closing as wont fix as this is a connectivity issue with connman with in the 
lab and has been marked for whitelisting.
Comment 12 Cristina Agurida 2015-11-03 07:44:35 UTC
As per last comment set it as verified.