Hide Forgot
Description of problem: When you create a LiveCD, on stage createLiveCD, livecd-creator freezes when working in an isolated layout. The problem with livecd-creator can decide board installation version, able to use the --noudevsync for a workaround (see https://bugzilla.redhat.com/show_bug.cgi?id=1001063#c1). But I have not found a true test in kojid way to pass a parameter --noudevsync for livecd-creator. Version-Release number of selected component (if applicable): CentOS 6.4 + EPEL 6: koji-builder-1.8.0-2.el6.noarch livecd-tools-13.4.4-2.el6.x86_64 (see https://bugzilla.redhat.com/show_bug.cgi?id=1001063) Additional info: I propose to add a kojid ability to set parameters for transmission to the livecd-creator.
(In reply to Aleksey Avdeev from comment #0) > I propose to add a kojid ability to set parameters for transmission to the > livecd-creator. I propose a solution: https://github.com/solooboroten/koji/commit/b655a7f7b070f4489346b664beb06495dea5f301 . When using the modified livecd-creator (see https://bugzilla.redhat.com/show_bug.cgi?id=1001063#c1), it allows you to collect images of the livecd in the presence of /etc/kojid/kojid.conf lines: ; configuration for livecd-tools livecd_creator_opts = - noudevsync
I myself decided to create a LiveCD problem as follows: 1. Built and installed on the building server package with the proposed koji (Comment 1) patch (see https://github.com/solooboroten/koji/commit/d611ec2f3aa8ae8f155785a6056a87d4b2002717). 2. In /etc/kojid/kojid.conf added the line: livecd_creator_opts = --noudevsync 3. Package with the patched livecd-creator (understanding the key --noudevsync, see https://bugzilla.redhat.com/show_bug.cgi?id=1001063#c1) added to the repository that is used to build the LiveCD. After this LiveCD began to gather normally.
This is a enhancement type of request and we prefer all such requests are handled upstream as we have no resources to do new development, nor do we want to diverge from upstream if possible. Would you be willing to refile this upstream at https://pagure.io/koji/issues ? If there's some reason you would prefer not to, I can do so, but note that you might have more interest in convincing koji developers to work on your request than I might. Thanks!