Cannot build FUEL ISO

[TorstenSchlabach]

I am following the instructions at

http://docs.mirantis.com/fuel-dev/develop/env.html

using a clean Ubuntu 14.04 LTS system.

(I have also set LANG=C which is not in the instructions, by the way ...)

I get stuck somewhere in the build process:

touch /home/torsten/fuel-main/build/mirror/ubuntu/boot.done
mkdir -p /home/torsten/fuel-main/local_mirror/ubuntu/chroot
# Prevent services from being started inside the staging chroot
policy_rc_d="/home/torsten/fuel-main/local_mirror/ubuntu/chroot/usr/sbin/policy-rc.d"; \
 mkdir -p "${policy_rc_d%/*}"; \
 echo "${POLICY_RC_D}" > "${policy_rc_d}"; \
 chmod 755 "${policy_rc_d}"
/bin/sh: 3: cannot create /home/torsten/fuel-main/local_mirror/ubuntu/chroot/usr/sbin/policy-rc.d: Permission denied
chmod: cannot access '/home/torsten/fuel-main/local_mirror/ubuntu/chroot/usr/sbin/policy-rc.d': No such file or directory
make: *** [/home/torsten/fuel-main/build/mirror/ubuntu/createchroot.done] Error 1

Any pointers?

Regards,
Torsten

[Stanislav Makar (smakar)]

Hi
Looks like there is a problem with the permissions
As I see you did it as usual user ?
Could you please do it as root ?

[TorstenSchlabach (tschlabach)]

You mean I shall run the whole

make iso

as root, i.e.:

sudo make iso

?

Will try ...

Actually, there seems to be some sudoing in the makefiles anyway; the directory local_mirror/ubuntu/chroot is indeed owned by root:root (even despite I started the build as a regular user) which possibly is the reason why the directory cannot be created.

[Stanislav Makar (smakar)]

Yes, run as sudo
looks like there is a problem with running as usual user
related bug https://bugs.launchpad.net/fuel/+bug/1348599

[TorstenSchlabach (tschlabach)]

Well; the related bug says that the build scripts will require sudo rights and that this is considered a bad idea. (Agree, by the way.) So it's related but it's not a duplicate, actually.

Will do some more experiments.

[TorstenSchlabach (tschlabach)]

Seems like you really don't want to have any HTTP proxy involved.
I tried this again on a machine with an open Internet connection and everything worked fine.