I looked into the kojid.conf and everything seems correct.
[kojid] ; The number of seconds to sleep between tasks ; sleeptime=15
; The maximum number of jobs that kojid will handle at a time ; maxjobs=10
; The minimum amount of free space (in MBs) required for each build root ; minspace=8192
; The directory root where work data can be found from the koji hub topdir=/mnt/koji
; The directory root for temporary storage workdir=/tmp/koji
; The directory root for mock mockdir=/var/lib/mock
; The user to run as when doing builds mockuser=kojiadmin
; The vendor to use in rpm headers ; vendor=Koji
; The packager to use in rpm headers ; packager=Koji
; The distribution to use in rpm headers ; distribution=Koji
; The _host string to use in mock ; mockhost=koji-linux-gnu
; The URL for the xmlrpc server server=http://vos-cm20/kojihub
; The URL for the file access topurl=http://vos-cm20/kojifiles
; A space-separated list of hostname:repository[:use_common] tuples that kojid is authorized to checkout from (no quotes). ; Wildcards (as supported by fnmatch) are allowed. ; If use_common is specified and is one of "false", "no", "off", or "0" (without quotes), then kojid will not attempt to checkout ; a common/ dir when checking out sources from the source control system. Otherwise, it will attempt to checkout a common/ ; dir, and will raise an exception if it cannot. ;allowed_scms=scm.example.com:/cvs/example git.example.org:/example svn.example.org:/users/*:no
; The mail host to use for sending email notifications ;smtphost=example.com
; The From address used when sending email notifications ;from_addr=Koji Build System buildsys@example.com
;configuration for Kerberos authentication
;the format of the principal used by the build hosts ;%s will be replaced by the FQDN of the host ;host_principal_format = compile/%s@EXAMPLE.COM
;location of the keytab ;keytab = /etc/kojid/kojid.keytab
;the service name of the principal being used by the hub ;krbservice = host
;configuration for SSL authentication
;client certificate cert = /etc/pki/koji/kojid.pem
;certificate of the CA that issued the client certificate ca = /etc/pki/koji/koji_ca_cert.crt
;certificate of the CA that issued the HTTP server certificate serverca = /etc/pki/koji/koji_ca_cert.crt
-----------------------------------------------------
I created new tags to make sure I have set up the packages and the groups correctly
[kojiadmin@vos-cm20 koji]$ koji taginfo ncp-build Tag: ncp-build [7] Arches: x86_64 This tag is a buildroot for one or more targets Current repo: repo#11: 2013-09-05 13:21:13.623486 Targets that build from this tag: ncp External repos: 5 dist-ncp-external-repo (/auto/tps/centos/6/x86_64/) Inheritance: 0 .... ncp [5]
1 .... ncp-basedeps [8]
-------------------------------------------------------------------------
kojiadmin@vos-cm20 koji]$ koji list-pkgs Package ----------------------- MAKEDEV acl attr audit authconfig basesystem bash binutils bzip2 ca-certificates centos-release checkpolicy chkconfig coreutils cpio cracklib cryptsetup-luks curl cyrus-sasl dash db4 dbus-glib device-mapper-multipath diffutils dracut e2fsprogs ethtool expat file filesystem findutils fipscheck gamin gawk gcc gdbm glib2 glibc gmp gnupg2 gpgme grep groff grub grubby gzip hwdata initscripts iproute iptables iputils kbd kernel less libaio libcap libcap-ng libcgroup libdrm libedit libffi libgcrypt libgpg-error libidn libnih libpciaccess libselinux libsemanage libsepol libssh2 libusb libuser libutempter libxml2 logrotate lua m4 mingetty module-init-tools ncurses net-tools newt nspr nss nss-softokn nss-util ntp openldap openssh openssl pam passwd pcre perl pinentry plymouth policycoreutils popt procps psmisc pth pygpgme python python-iniparse python-pycurl python-urlgrabber readline redhat-logos rootfiles rpm rsync rsyslog sed selinux-policy setup shadow-utils slang sqlite tar tzdata udev upstart ustr util-linux-ng which yum yum-metadata-parser zlib tzdata-2012j
I still see the same error.
Thanks, Radha.
-----Original Message----- From: buildsys-bounces@lists.fedoraproject.org [mailto:buildsys-bounces@lists.fedoraproject.org] On Behalf Of Michael Cronenworth Sent: Wednesday, September 04, 2013 5:54 PM To: buildsys@lists.fedoraproject.org Subject: Re: ERROR: Could not find useradd in chroot, maybe the install failed? in mock_output.log
On 09/04/2013 05:58 PM, Radha Venkatesh (radvenka) wrote:
DEBUG util.py:264: Warning: Group build does not have any packages.
Here's the problem. I don't know your full koji setup but something is not setup correctly. The build target for tag dist-ncp is not right. -- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys