On 07/07/15 20:05, Andres Toomsalu wrote:
Solved the "connection refused" issue - seems that it was complaining about internet connection from imagefactory build VM - which was blocked because shutting down firewalld changed libvirt iptables ruleset (and libvirtd wasnt restarted after shutting down firewalld). Im still puzzled why image build process requires outside connection - if ostree repo should be coming from host (192.168.122.1)?
should not need outside connection, when its built in the centos bsys, the machine does not even have an outside connection to the internet.
Andres Toomsalu mailto:andres@opennodecloud.com 7. juuli 2015 16:45 Update:
As of https://github.com/CentOS/sig-atomic-buildscripts/commit/44a145ebf65fd610103... Im now able to build and commit ostree (by executing build_ostree_components.sh) - and installer images build step seems to complete successfully.
But imagefactory build fails when executing:
rpm-ostree-toolbox imagefactory --overwrite --tdl ${GitDir}/atomic-7.1.tdl -c ${GitDir}/config.ini -i kvm -i vagrant-libvirt -i vagrant-virtualbox -k ${GitDir}/atomic-7.1-cloud.ks --vkickstart ${GitDir}/atomic-7.1-vagrant.ks -o ${BuildDir}/virt |& tee ${LogFile}
Debug info
# Build host is CentOS 7.1 as Parallels Desktop 10 VM - with nested virtualization for running imagefactory KVM VMs.
# Error screenshot from imagefactory VM: http://prntscr.com/7ptic2
# HTTPServer log from build host: [root@nf-builder builddir]# Serving HTTP on 0.0.0.0 port 8000 ... 192.168.122.1 - - [06/Jul/2015 23:41:19] "HEAD /installer/images/ HTTP/1.1" 200 - 192.168.122.1 - - [06/Jul/2015 23:41:19] "HEAD /installer/images//.treeinfo HTTP/1.1" 200 - 192.168.122.1 - - [06/Jul/2015 23:41:19] "GET /installer/images//.treeinfo HTTP/1.1" 200 - 192.168.122.1 - - [06/Jul/2015 23:41:19] "HEAD /installer/images/images/pxeboot/vmlinuz HTTP/1.1" 200 - 192.168.122.1 - - [06/Jul/2015 23:41:19] "HEAD /installer/images/images/pxeboot/initrd.img HTTP/1.1" 200 - 192.168.122.236 - - [06/Jul/2015 23:41:44] "GET /installer/images//.treeinfo HTTP/1.1" 200 - 192.168.122.236 - - [06/Jul/2015 23:41:44] "GET /installer/images//LiveOS/squashfs.img HTTP/1.1" 200 - 192.168.122.236 - - [06/Jul/2015 23:41:52] code 404, message File not found 192.168.122.236 - - [06/Jul/2015 23:41:52] "GET /installer/images//images/updates.img HTTP/1.1" 404 - 192.168.122.236 - - [06/Jul/2015 23:41:52] code 404, message File not found 192.168.122.236 - - [06/Jul/2015 23:41:52] "GET /installer/images//images/product.img HTTP/1.1" 404 -
# Program log screenshot from Anaconda installer: http://prntscr.com/7ptiz7
# Anaconda log screenshot: http://prntscr.com/7ptjl0
# Network ping test from imagefactory build VM to host 192.168.122.1: http://prntscr.com/7ptk3w
# Successful curl http://192.168.122.1:8000/repo/ test from imagefactory build VM : http://prntscr.com/7ptku6
# Ostreesetup line from kickstart:
[root@nf-builder sig-atomic-buildscripts]# cat atomic-7.1-cloud.ks | grep ostreesetup ostreesetup --osname="centos-atomic-host" --remote="centos-atomic-host" --ref="centos-atomic-host/7/x86_64/standard" --url="http://192.168.122.1:8000/repo/" --nogpg
# Installer images: [root@nf-builder sig-atomic-buildscripts]# ls -lh /srv/builddir/installer/images/images/ total 686M -rw-r--r-- 1 root root 6.3M Jul 7 01:00 efiboot.img -rw-r--r-- 1 root root 680M Jul 7 01:00 installer.iso drwxr-xr-x 2 root root 55 Jul 7 01:00 pxeboot
[root@nf-builder sig-atomic-buildscripts]# ls -lh /srv/builddir/installer/images/LiveOS/ total 594M -rw-r--r-- 1 root root 594M Jul 7 00:56 squashfs.img
Any ideas why anaconda gets "connection refused" in ostreesetup step? Any ideas how to debug it further?
Kind regards,
-- http://www.getpostbox.com----------------------------------------------
Andres Toomsalu, andres@opennodecloud.com mailto:andres@opennodecloud.com
Andres Toomsalu mailto:andres@opennodecloud.com 27. juuni 2015 20:01 Hi,
Im trying to do custom centos-atomic-host build - from unmodified https://github.com/CentOS/sig-atomic-buildscripts configuration source and following instruction in https://developerblog.redhat.com/2015/01/08/creating-custom-atomic-trees-ima... blog post series.
Im able to produce ostree and installer.iso image - BUT rpm-ostree-toolbox creates ostree tree with missing grub file, resulting in a failing installer. More details about this problem here: https://github.com/projectatomic/rpm-ostree-toolbox/issues/77
Commands used for ostree and installer creation were:
rpm-ostree-toolbox treecompose -c ~/repos/sig-atomic-buildscripts/config.ini --ostreerepo /srv/rpm-ostree/centos-atomic-host/7/
rpm-ostree-toolbox installer -c /root/repos/sig-atomic-buildscripts/config.ini \ --ostreerepo /srv/rpm-ostree/centos-atomic-host/7/ \ --outputdir /var/www/html/latest/ --overwrite
cp ~/repos/sig-atomic-buildscripts/centos-atomic-host-7.ks /var/www/html/ virt-install --name=atomic-iso --memory=1024 --vcpus=1 \ --disk=/var/lib/libvirt/images/test.qcow2,size=5 \ --location /var/www/html/latest/images/installer.iso \ --noautoconsole --accelerate --os-type=linux --os-variant=rhel7 \ --extra-args "ks=http://192.168.122.1/centos-atomic-host-7.ks"
Another issue is that also imagefactory KVM centos-atomic-host image build fails in anaconda install stage - complaining about unknown missing file - might be the same problem - not sure...
Command used for kvm image creation:
rpm-ostree-toolbox imagefactory \ -c /root/repos/sig-atomic-buildscripts/config.ini -i kvm \ --ostreerepo /srv/rpm-ostree/centos-atomic-host/7/ \ --outputdir /srv/rpm-ostree/centos-atomic-host/7/images
Error screenshot from imagefactory launched build VM console: http://prntscr.com/7lq38e
From the build VM /tmp/anaconda.log:
21:40:35,454 INFO anaconda: Creating xfs on /dev/vda1 21:40:36,242 INFO anaconda: executing ostreesetup=<pykickstart.commands.ostreesetup.RHEL7_OSTreeSetup object at 0x7fdd038d3110> 21:40:36,570 ERR anaconda: Failed to pull from repository: Server returned status 404: Not Found
Last lines from the build VM /tmp/program.log:
21:40:36,339 INFO program: Running... ostree --repo=/mnt/sysimage/ostree/repo remote add --set=gpg-verify=false installmedia http://192.168.122.1:47990/ 21:40:36,377 DEBUG program: Return code: 0
Any suggestions how to debug it further? Where should I file a bug report?
Kind regards,
-- http://www.getpostbox.com----------------------------------------------
Andres Toomsalu, andres@opennodecloud.com mailto:andres@opennodecloud.com
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel