Bug 8014 - syslog configure fails on genericx86-64 LSB image
Summary: syslog configure fails on genericx86-64 LSB image
Status: VERIFIED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 1.9
Hardware: NUC x86_64
: Medium normal
Target Milestone: 1.9
Assignee: Lucian Musat
QA Contact: Cristina Agurida
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-07-15 14:16 UTC by Cristina Agurida
Modified: 2015-09-09 14:39 UTC (History)
3 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-07-15 14:16:02 UTC
STATUS: FAILED
BUILD: 1.9_M1.rc2: f9ea480e6c26fea46c3011c4e9d0e2de3d5c81b4
ENVIRONMENT: NUC(Next Unit of Computing)
BSP: genericx86-64
IMAGE TYPE: core-image-lsb-sdk

STEPS TO REPRODUCE: 
1. Get a yocto image from autobuilder or local build
2. Launch image and check if syslog is started by default in background with ps command: (ps -elf|grep syslog)
3. Modify /etc/syslog-startup.conf, change the LOGFILE to /var/log/messages.test
4. Restart syslog with command "/etc/init.d/syslog restart"
5. Check if syslog is started in background with ps command
6. Check if there is file generated under /var/log/messages.test

EXPECTED OUTCOME:
 Syslog could be configured by user and run without problem .

ACTUAL OUTCOME:
 This error appears during testing LSB image:

15:19:32 - bitbake-worker - RESULTS - Testcase 202: FAILED
15:19:32 - bitbake-worker - RESULTS - Testcase 202:
Traceback (most recent call last):
  File /work/weekly/runtime/genericx86-64-lsb_nuc/poky/meta/lib/oeqa/utils/decorators.py, line 102, in wrapped_f
    return func(*args)
  File /work/weekly/runtime/genericx86-64-lsb_nuc/poky/meta/lib/oeqa/utils/decorators.py, line 90, in wrapped_f
    return f(*args)
  File /work/weekly/runtime/genericx86-64-lsb_nuc/poky/meta/lib/oeqa/utils/decorators.py, line 90, in wrapped_f
    return f(*args)
  File /work/weekly/runtime/genericx86-64-lsb_nuc/poky/meta/lib/oeqa/runtime/syslog.py, line 46, in test_syslog_startup_config
    self.assertEqual(status, 0, msg=Test log string not found. Output: %s  % output)
AssertionError: 2 != 0 : Test log string not found. Output: grep: /var/log/test: No such file or directory 

Is this a valid bug or is because busybox is not present on LSB images?
Comment 1 Bruce Ashfield 2015-07-15 14:35:44 UTC
I could research these, but my plate is rather full at the moment. Sending this to PaulE, in the hopes that he can redirect or answer it more quickly than I can.
Comment 2 Paul Eggleton 2015-07-15 14:57:06 UTC
This configuration method looks like it is indeed specific to busybox, and LSB images include the real syslog which is configured differently. My suggestion would be to make the test check to see which syslog implementation is in use (perhaps just see if syslogd is a symlink to busybox) and skip the test if it isn't busybox.
Comment 4 Cristina Agurida 2015-08-12 10:07:53 UTC
This issue reappears on 1.9_M2.rc2: c75cefe8a382a63f625123c156137782db118f64
Comment 5 Costin 2015-09-08 14:49:59 UTC
Hello,

i tested this bug (was related to an other task of mine) and both for a poky and poky-lsb image built, it was fine. In the first case, (for DISTRO="poky") the core-image-sato passed the test, while for the second  (for DISTRO="poky-lsb") it skipped, it which is normal behavior.

As a conclusion, I guess the issue is solved now.

poky hash: c1df471feacaf2590216aa476ce242908dac38cf
OS build machine: Ubuntu 15.04
Comment 6 Costin 2015-09-09 08:13:22 UTC
Based on last comment, marking it as resolved
Comment 7 Cristina Agurida 2015-09-09 14:39:28 UTC
Verified on master: d4585fa23d56a58c583ee33db067a23177a936b1