Bug 8526 - Parselogs error: creating IPv4 interface lo failed; interface ignored
Summary: Parselogs error: creating IPv4 interface lo failed; interface ignored
Status: RESOLVED WORKSFORME
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-runtime (show other bugs)
Version: 1.7.3
Hardware: MinnowBoard Max x86
: Medium normal
Target Milestone: 2.1
Assignee: Saul Wold
QA Contact: Cristina Agurida
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-10-16 09:16 UTC by Cristina Agurida
Modified: 2016-03-14 20:13 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
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 Cristina Agurida 2015-10-16 09:16:21 UTC
STATUS: FAILED
BUILD: 1.7.3: b38454c2e3a7a58f5397bb16d59e2b0aa71c4a94
ENVIRONMENT: genericx86-lsb on MMAX32bit
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 :
Central error: Oct  8 19:05:43 genericx86 named[956]: creating IPv4 interface lo failed; interface ignored
Comment 1 Alexandru Georgescu 2015-10-20 13:34:00 UTC
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!
Comment 2 Cristina Agurida 2015-10-30 10:04:28 UTC
Seems to be the same problem with the network configuration in the lab as in bug 8473 because at the desk the issue cannot be reproduced. 
Maybe this issue can be also added to the whitelist?
Comment 3 Saul Wold 2016-03-14 20:13:04 UTC
This message has not been seem with 1.8, 2.0 or 2.1 as far as I know. I have 
not been able to reproduce it.

If someone in QA sees this again, please re-open.