Bug 5972 - "ls: cannot access /etc/rpm-postinsts" during boot
Summary: "ls: cannot access /etc/rpm-postinsts" during boot
Status: VERIFIED FIXED
Alias: None
Product: Installation
Classification: Runtime
Component: Installation (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.6
Assignee: Laurentiu Palcu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-03-14 13:47 UTC by Stoicescu Cornel
Modified: 2014-04-07 14:51 UTC (History)
3 users (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 Stoicescu Cornel 2014-03-14 13:47:33 UTC
Tested with poky master:1960f6b2ecbb793b40ebc9aed25c8f9cb7884c9a

The following message can be found in /var/log/boot:
Fri Mar 14 15:00:35 2014: Populating dev cache
Fri Mar 14 15:00:42 2014: ALSA: Restoring mixer settings...
Fri Mar 14 15:00:42 2014: /usr/sbin/alsactl: load_state:1729: No soundcards found...
Fri Mar 14 15:00:42 2014: ls: cannot access /etc/rpm-postinsts: No such file or directory
Fri Mar 14 15:00:42 2014: update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
Fri Mar 14 15:00:42 2014:  Removing any system startup links for run-postinsts ...
Fri Mar 14 15:00:42 2014:   /etc/rcS.d/S99run-postinsts
Fri Mar 14 15:00:42 2014: INIT: Entering runlevel: 5
Fri Mar 14 15:00:42 2014: Configuring network interfaces... done.
Fri Mar 14 15:00:43 2014: Starting system message bus: dbus.

Images tested: core-image-sato-sdk-qemux86-64, core-image-lsb-sdk-qemux86-64, core-image-lsb-sdk-genericx86-64

Steps to reproduce:
1) Build any of the above images with the specified commit and default settings (add meta-qt3 for poky-lsb distro)
2) boot the image (install it if it's a BSP)
3) notice during boot or in /var/log/boot the specified message
Comment 1 Laurentiu Palcu 2014-03-18 16:03:51 UTC
I have a fix for this in tests already.
Comment 3 Alexandru Palalau 2014-04-07 14:51:09 UTC
Verified on master branch.
Commit ID: bb66113bde5361b869dce2bdaece5b938f077ea8