2743 2012-07-12 06:37:48 +0000 Useradd command fails after 10 retries with 1.1.2 20120630 build 2013-03-06 02:27:57 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.1.2 x86 Multiple RESOLVED FIXED Medium normal 1.1.2 1 yi.zhao liezhi.yang jiajun.xu laurentiu.serban liang.li2 meta.mr.watcher meta.watcher msm-oss richard.purdie sgw yi.zhao --- --- --- oldest_to_newest 23023 0 yi.zhao 2012-07-12 06:37:48 +0000 Tree/Branch: poky/edison Commit: 8886aee5b9741c05886994967d9ecf420331c600 This issue is same as bug 2218 and fixed in 1.2. Seems the patch also need to be merged into edison tree. http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0923ee40ae59133c91a95e0727eb1ab95aca13b8 Steps: Following the wiki page: https://wiki.yoctoproject.org/wiki/PAM_Integration to build a image with PAM support. Image do_rootfs failed: ################# | libical ################################################## | libpcre0 ################################################## | libattr1 ################################################## | -- | WARNING: useradd command did not succeed. Retrying... | WARNING: useradd command did not succeed. Retrying... | WARNING: useradd command did not succeed. Retrying... | WARNING: useradd command did not succeed. Retrying... | WARNING: useradd command did not succeed. Retrying... | ERROR: tried running useradd command 10 times without success, giving up | xserver-nodm-init ################################################## | Adding system startup for /buildarea2/yzhao-test/poky-build/build-pam/tmp/work/qemuarm-poky-linux-gnueabi/core-image-sato-1.0-r0/rootfs/etc/init.d/xserver-nodm. | xrandr ################################################## | update-rc.d ################################################## | sysvinit-pidof ################################################## | | ERROR: Function 'do_rootfs' failed (see /buildarea2/yzhao-test/poky-build/build-pam/tmp/work/qemuarm-poky-linux-gnueabi/core-image-sato-1.0-r0/temp/log.do_rootfs.1120 for further information) ################ 23103 1 josh 2012-07-13 16:00:18 +0000 Is this only when enabling the PAM integration? IIRC I avoided that patch as it's not a clean cherry-pick, the RPM package back-end changed quite a lot in 1.2 I'll start working on a fix for this issue on Monday. 23110 2 yi.zhao 2012-07-16 04:45:20 +0000 (In reply to comment #1) > Is this only when enabling the PAM integration? Now I can only reproduce this issue when enabling PAM. Just add one line in local.conf: DISTRO_FEATURES_append = " pam" > > IIRC I avoided that patch as it's not a clean cherry-pick, the RPM package > back-end changed quite a lot in 1.2 > > I'll start working on a fix for this issue on Monday. 24713 3 sgw 2012-08-31 21:46:07 +0000 Is this similar to 3073? 24726 4 liezhi.yang 2012-09-02 07:43:57 +0000 (In reply to comment #3) > Is this similar to 3073? Not very sure currently, need more investigation. 24790 5 liezhi.yang 2012-09-04 11:41:34 +0000 This is not similar to 3073, and 1.3 doesn't have this problem, so change its milestone to 1.1.2 24825 6 liang.li2 2012-09-05 02:53:58 +0000 (In reply to comment #5) > This is not similar to 3073, and 1.3 doesn't have this problem, so change > its milestone to 1.1.2 it means bug 3047. 29831 7 msm-oss 2013-02-14 18:55:28 +0000 Autobuilder is now seeing these issues... -M 29840 8 richard.purdie 2013-02-14 21:13:39 +0000 (In reply to comment #7) > Autobuilder is now seeing these issues... I think those were from the pseudo update and have been resolved now... 30462 9 liezhi.yang 2013-03-06 02:27:57 +0000 See the comments from Richard, this has been fixed now.