Hi,
Looks like there is some issue with cbs i.e. image-factory, because all vagrant builds are failing for me. The builds are failing for source files which had built fine previously.
For example build [1] is using the same source files (kickstart files etc) as build [2] but it failed where as build [2] has succeeded previously.
[1] https://cbs.centos.org/koji/taskinfo?taskID=51053 [2] http://cbs.centos.org/koji/taskinfo?taskID=38547
-Lala
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 21/10/15 12:30, Lalatendu Mohanty wrote:
Hi,
Looks like there is some issue with cbs i.e. image-factory, because all vagrant builds are failing for me. The builds are failing for source files which had built fine previously.
For example build [1] is using the same source files (kickstart files etc) as build [2] but it failed where as build [2] has succeeded previously.
[1] https://cbs.centos.org/koji/taskinfo?taskID=51053 [2] http://cbs.centos.org/koji/taskinfo?taskID=38547
-Lala
So, as discussed on irc, here are the details :
- - that build uses imagefactory - - imagefactory uses itself libvirt to setup a VM - - by default trying to use "default" network (aka NAT) , and that's where it failed
Explanations : Those kojid/koji builders are managed by puppet, including for iptables rules, but we didn't know that libvirt was installed/running. So I've fixed (through temporary fix) the iptables rules (as it would block by default) and I'll write a koji::builder::imagefactory puppet class that will take care of installing/configuring all components (including iptables rules for libvirt as a dep)
It already works with the "interim" fix : http://cbs.centos.org/koji/taskinfo?taskID=52451
Cheers,
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 27/10/15 17:10, Fabian Arrotin wrote:
On 21/10/15 12:30, Lalatendu Mohanty wrote:
Hi,
Looks like there is some issue with cbs i.e. image-factory, because all vagrant builds are failing for me. The builds are failing for source files which had built fine previously.
For example build [1] is using the same source files (kickstart files etc) as build [2] but it failed where as build [2] has succeeded previously.
[1] https://cbs.centos.org/koji/taskinfo?taskID=51053 [2] http://cbs.centos.org/koji/taskinfo?taskID=38547
-Lala
So, as discussed on irc, here are the details :
- that build uses imagefactory
- imagefactory uses itself libvirt to setup a VM
- by default trying to use "default" network (aka NAT) , and that's
where it failed
Explanations : Those kojid/koji builders are managed by puppet, including for iptables rules, but we didn't know that libvirt was installed/running. So I've fixed (through temporary fix) the iptables rules (as it would block by default) and I'll write a koji::builder::imagefactory puppet class that will take care of installing/configuring all components (including iptables rules for libvirt as a dep)
It already works with the "interim" fix : http://cbs.centos.org/koji/taskinfo?taskID=52451
thanks for getting this done Fabian, it was otherwise going to hit the monthly builds as well!
regards,
-
Fabian Arrotin -
Karanbir Singh -
Lalatendu Mohanty