Hi Xiexs, Definitely make sure you run nodepool commands as nodepool and not root: sudo su - nodepool
Before starting nodepool on a fresh install, I usually manually build the image first as it is easier to debug issues: sudo su - nodepool nodepool image-build <image-name> Ramy -----Original Message----- From: Xie, Xianshan [mailto:[email protected]] Sent: Wednesday, July 29, 2015 10:44 PM To: OpenStack Development Mailing List (not for usage questions) <[email protected]> Subject: [openstack-dev] 答复: [CI] No image was created after running "nodepoold -d $DAEMON_ARGS" Hi Wienand, Thanks for your reply. >So, nothing after this? Yes, there is nothing anymore since that line in the nodepool.log. But, the the polling thread still goes on , according to the log message in the debug.log. > Nothing jumps out; first thought was to check if disk-image-create is running > and go from there. If it's stuck, pointing strace() at it might give a clue. The disk-image-create is still running(with ps command). I don’t know how to debug disk-image-create while it spawned by nodepoold. (I had tried to add set -x into disk-image-create, but it did not work) Could you give me some tips? >Something I just thought of that has caused problems is check your users; I >think running things by hand as root and then switching back to a unprivileged >user can cause problems as the second run hits things it can't modify. Yes, you are definitely right, I really once met this problem. But right now, I checked the disk-image-create by hand with user "nodepool" which also used by "nodepoold -d $DAEMON_ARGS". Thanks again. Xiexs -----邮件原件----- 发件人: Ian Wienand [mailto:[email protected]] 发送时间: 2015年7月30日 11:51 收件人: OpenStack Development Mailing List (not for usage questions) 主题: Re: [openstack-dev] [CI] No image was created after running "nodepoold -d $DAEMON_ARGS" On 07/30/2015 12:34 PM, Xie, Xianshan wrote: > DEBUG nodepool.NodePool: Finished node launch calculation INFO > nodepool.DiskImageBuilderThread: Running disk-image-create ... So, nothing after this? Nothing jumps out; first thought was to check if disk-image-create is running and go from there. If it's stuck, pointing strace() at it might give a clue. Full logs and config help, but my best suggestion is to jump on irc in #openstack-infra; during USA awake hours you'll get the best response. -i __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
