Bug 7470 - Smart module not found on OpenSUSE 13.2
Summary: Smart module not found on OpenSUSE 13.2
Status: VERIFIED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.6.3
Assignee: Mihail Stanciu
QA Contact: Alexandru Georgescu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-03-17 13:01 UTC by Mihail Stanciu
Modified: 2015-06-05 12:24 UTC (History)
3 users (show)

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


Attachments
full log file (1.29 KB, application/octet-stream)
2015-03-17 13:01 UTC, Mihail Stanciu
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mihail Stanciu 2015-03-17 13:01:09 UTC
Created attachment 2448 [details]
full log file

Tested on 1.6.3_RC2: 6b8f7999c3e86d6e834af95ffe4c33d0d53db34a

Task do_rootfs for qemux86-64 failed on OpenSUSE 13.2 AB machine with error message:

ERROR: Could not invoke smart. Command '/home/autobuilder/yocto-autobuilder/yocto-worker/nightly-qa-targetbuilds/build/build/tmp/sysroots/x86_64-linux/usr/bin/smart --data-dir=/home/autobuilder/yocto-autobuilder/yocto-worker/nightly-qa-targetbuilds/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato-sdk/1.0-r0/rootfs/var/lib/smart config --set rpm-root=/home/autobuilder/yocto-autobuilder/yocto-worker/nightly-qa-targetbuilds/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato-sdk/1.0-r0/rootfs' returned 1:
Traceback (most recent call last):
  File "/home/autobuilder/yocto-autobuilder/yocto-worker/nightly-qa-targetbuilds/build/build/tmp/sysroots/x86_64-linux/usr/bin/smart.real", line 27, in <module>
    from smart import init, initDistro, initPlugins, initPycurl, initPsyco
ImportError: No module named smart

ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/autobuilder/yocto-autobuilder/yocto-worker/nightly-qa-targetbuilds/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato-sdk/1.0-r0/temp/log.do_rootfs.26928
NOTE: recipe core-image-sato-sdk-1.0-r0: task do_rootfs: Failed
ERROR: Task 7 (/home/autobuilder/yocto-autobuilder/yocto-worker/nightly-qa-targetbuilds/build/meta/recipes-sato/images/core-image-sato-sdk.bb, do_rootfs) failed with exit code '1'

Autoconf content:
INHERIT += "report-error"
DISTRO = "poky"
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
BB_NUMBER_THREADS = "10"
PARALLEL_MAKE = "-j 10"
SDKMACHINE ?= "x86_64"
BB_TASK_NICE_LEVEL = "5"
IMAGE_FSTYPES_append = "  tar.gz"
BB_TASK_NICE_LEVEL_task-testimage = "0"
DL_DIR = "/home/autobuilder/yocto-autobuilder/downloads"
SSTATE_DIR ?= "/home/autobuilder/sstate/" 
MACHINE = "qemux86-64"
PREMIRRORS = ""
ADTREPO = "http://adtrepo.yoctoproject.org//1.6.2"
Comment 1 Saul Wold 2015-03-20 20:41:04 UTC
I tried to reproduce this one and the other related RPM issue today on a 
Suse13.2 machine and was not able to get either of these failures.  One thought 
from RP was there is some host contamination going on, if possible I would like 
to get access to the failing machine or if you can confirm is any rpm packages 
are installed besides the standard one.  Specifically if there is a librpm 
installed in /usr/lib or /lib
Comment 2 Saul Wold 2015-03-21 23:25:37 UTC
see prior comment
Comment 3 Mihail Stanciu 2015-03-23 07:50:24 UTC
Looks like there is no librpm in the 2 locations you've mentioned:

autobuilder@ab-opensuse:~> ll /usr/lib | grep rpm
drwxr-xr-x   7 root root    4096 Jan 22 23:10 rpm
drwxr-xr-x   4 root root    4096 Nov 19 20:52 rpmrebuild
autobuilder@ab-opensuse:~> ll /lib | grep rpm
autobuilder@ab-opensuse:~>
Comment 4 Alexandru Georgescu 2015-03-23 13:31:59 UTC
changed the regression field to unknown. This distro wasn't supported during 1.6 release development cycle, so the previous flag (regression, used to work) is invalid
Comment 5 Saul Wold 2015-04-17 17:56:18 UTC
Can you reproduce this issue again, I still have not been able to
Comment 6 Alexandru Georgescu 2015-05-13 06:44:35 UTC
Assigning this to Mihai
Comment 7 Mihail Stanciu 2015-05-27 12:07:44 UTC
Unable to replicate for 1.6.3.

Marking as "WORKSFORME"

Will reopen if issue reappears.
Comment 8 Mihail Stanciu 2015-06-05 12:24:14 UTC
(In reply to comment #7)
> Unable to replicate for 1.6.3.
> 
> Marking as "WORKSFORME"
> 
> Will reopen if issue reappears.

Marking as verified.