Thank You, Dan. My answers are below...
> Dan Williams <[EMAIL PROTECTED]> wrote on 07/06/2006 09:59:33 AM:
> On Tue, 2006-07-04 at 09:58 -0400, Joe Todaro wrote:
> >
> > Hi,
> > I'm having a problem *not* being able to build 'i686' packages (i.e.
> > optional_arches=i686) anymore *after* having upgraded our plague
> > server/builder (Opteron x86_64) a couple of weeks ago from
> > plague-0.4.3 to *plague-0.5.0*. The problem happens only with i686
> > (optional_arches=i686) -- not with i386 (base_arches=i386) which
> > continues to work flawlessly.
>
> Sounds like a bug; do the builder logs show anything, i.e. does the
> server farm the job out to builders?
The builder log shows nothing--the job is definitely *not* farmed out to the builder.
> Note that as of Jun 21st, I
> committed a fix to the builders that was causing stuff that needed
> setarch to not work correctly, but that doesn't sound like this problem.
I know--I installed your builder/BuilderMock.py updates on June 28th hoping that might help.
Also, a few days ago I upgraded Mock to the latest version, mock-0.6-1, hoping that might help.
I also forgot to mention sooner that we only use Passive Buliders -- not Active Builders.
>
> If the job doesn't go to the builder, there are some known issues where
> plague will just not farm the job out to anyone if the builder config
> files aren't just right. The builder doesn't think it supports a
> particular target and so of course the server won't try to build on that
> target. Try double-checking your plague-builder targets config files
> and make _sure_ they support every architecture you want to build on
> (i386, i686, i586, etc).
Hopefully these next five sections will help shed more light...
- - - - -
(1 of 5) Here's what our /etc/plague/builder/plague-builder.cfg file looks like (with hostname/server changes to protect the innocent--that's me;):
- - - - -
[Active]
fileserver_port = 8889
xmlrpc_port = 8888
[Passive]
fileserver_port = 8889
xmlrpc_port = 8888
[Directories]
target_configs_dir = /etc/plague/builder/targets
builder_work_dir = /build/builder_work
[SSL]
builder_key_and_cert_dir = /etc/plague/builder/certs
use_ssl = yes
ca_cert = /etc/plague/builder/certs/ca_cert.pem
[General]
builder_cmd = /usr/bin/mock
builder_user = plague-builder
hostname = lnxbuild1.abc.com
server = lnxbuild1.abc.com
debug = yes
comm_type = passive
- - - - -
(2 of 5) Here's what our /etc/plague/builder/targets/lnxaddons-100-i386-install.cfg file looks like (with distro change to protect the innocent):
- - - - -
[General]
distro=lnxaddons
target=100
basearch=i386
repo=install
mock_config=lnxaddons-100-i386-install
- - - - -
(3 of 5) Here's what our /etc/mock/lnxaddons-100-i386-install.cfg file looks like (with baseurl changes to protect the innocent):
- - - - -
#!/usr/bin/python -tt
import os
config_opts['root'] = 'lnxaddons-100-i386'
config_opts['basedir'] = '/var/lib/mock/'
config_opts['chroot'] = '/usr/sbin/mock-helper chroot'
config_opts['mount'] = '/usr/sbin/mock-helper mount'
config_opts['umount'] = '/usr/sbin/mock-helper umount'
config_opts['rm'] = '/usr/sbin/mock-helper rm'
config_opts['mknod'] = '/usr/sbin/mock-helper mknod'
config_opts['yum'] = '/usr/sbin/mock-helper yum'
config_opts['runuser'] = '/sbin/runuser'
config_opts['buildgroup'] = 'build'
config_opts['chrootuser'] = 'aobuild'
config_opts['chrootgroup'] = 'aobuild'
config_opts['chrootuid'] = os.geteuid()
config_opts['chrootgid'] = os.getegid()
config_opts['chroothome'] = '/builddir'
config_opts['clean'] = True
config_opts['target_arch'] = 'i386'
config_opts['yum.conf'] = """
[main]
cachedir=/var/cache/yum
debuglevel=1
logfile=/var/log/yum.log
reposdir=/dev/null
retries=20
obsoletes=1
gpgcheck=0
assumeyes=1
# repos
[install]
name=install
baseurl=http://.../rhel4/i386/install/
[updates]
name=updates
baseurl=http://.../rhel4/updates/
[updates-rhel]
name=updates-rhel
baseurl=http://.../rhel4/updates/
[groups]
name=groups
baseurl=file:///build/buildgroups/i386/
[plague]
name=plague
baseurl=file:///build/yum/lnxaddons-100-install/i386/
"""
- - - - -
(4 of 5) Here's the e-mail that plague sends to my inbox each time I try to build the i686 (optional arch) e1000 package:
- - - - -
Subject: Prep Error (Job 618): /afs/.../SRPMS/e1000/e1000-7.0.38-1_rhel4.src.rpm on lnxaddons-100-install
Package /afs/.../SRPMS/e1000/e1000-7.0.38-1_rhel4.src.rpm does not build on any architectures this build system supports.
Package: ['i686']
Build System: ['i386', 'i386']
- - - - -
(5 of 5) Here are all the arches our builders think they support--i got this info by clicking on the [Builder Status] button of the web interface:
- - - - -
lnxbuild1.abc.com (0/1)
x86_64, amd64, ia32e, noarch, i386, i486, i586, i686, athlon
lnxppc.abc.com (0/8)
ppc64, noarch
>
> I'll see if I can look a bit more over the weekend.
>
> Dan
>
> > PLAGUE-0.4.3 / PLAGUE 0.5.0 ARCHES CONFIGURATION:
> > Here's what the Arches section looks like in all
> > the /etc/plague/server/targets/*.cfg files:
> > [Arches]
> > base_arches=i386
> > optional_arches=i686 noarch
> >
> > PLAGUE-0.4.3 SERVER LOG:
> > Here's an example of how things used to work (snipped
> > from /var/log/plague-server.log) whenever an i686 package-build
> > request was submitted to our PLAGUE-0.4.3 server:
> > Request to enqueue 'e1000' tag
> > '/afs/pok/projects/devel/SRPMS/e1000/e1000-7.0.38-1_rhel4.src.rpm' for
> > target 'ao100' (user '[EMAIL PROTECTED]')
> > 503 (e1000): Starting tag
> > '/afs/pok/projects/devel/SRPMS/e1000/e1000-7.0.38-1_rhel4.src.rpm' on
> > target 'lnxaddons-100-install'
> > 503 (e1000): Requesting depsolve...
> > 503 (e1000): Starting depsolve for arches: ['i686'].
> > 503 (e1000): Finished depsolve (successful), requesting archjobs.
> > 503 (e1000/i686): https://lnxbuild1.abc.com:8888 - UID is
> > d90078ec928db631ae8f590e6d5491d514cfe4a8
> > 503 (e1000/i686): Build result files - [ 'mockconfig.log',
> > 'build.log', 'root.log',
> > 'kernel-module-e1000-7.0.38-1.6.9_34.EL_2_rhel4.i686.rpm', 'job.log',
> > 'e1000-7.0.38-1_rhel4.src.rpm',
> > 'kernel-smp-module-e1000-7.0.38-1.6.9_34.EL_2_rhel4.i686.rpm' ]
> > Repo 'lnxaddons-100-install': updating repository metadata...
> > 503 (e1000): Job finished.
> >
> > PLAGUE-0.5.0 SERVER LOG:
> > But here's what happens (snipped from /var/log/plague-server.log) now,
> > whenever the above i686 package-build request gets submitted to our
> > "upgraded" plague server/builder running PLAGUE-0.5.0 (absolutely
> > nothing!)
> > Request to enqueue 'e1000' tag
> > '/afs/pok/projects/devel/SRPMS/e1000/e1000-7.0.38-1_rhel4.src.rpm' for
> > target 'ao100' (user '[EMAIL PROTECTED]')
> > 508 (e1000): Starting tag
> > '/afs/pok/projects/devel/SRPMS/e1000/e1000-7.0.38-1_rhel4.src.rpm' on
> > target 'lnxaddons-100-install'
> > 508 (e1000): Job finished.
> >
> > OBSERVATIONS:
> > o The "last" function executed in the 'PackageJob.py' module (before
> > it returned to 'BuildMaster.py') was 'arch_handling(self, ba,
> > exclusive, exclude)'.
> > o Adding the following section to /etc/plague/server/targets/*.cfg
> > (including server/builder restart, request resubmit) did *not* help
> > 'PackageJob.py' to progress any further than the 'arch_handling(self,
> > ba, exclusive, exclude)' function.
> > [Additional Package Arches]
> > kernel=i686
> > o Moving 'i686' from the 'optional_arches' line up to the
> > 'base_arches' line (including server/builder restart, request
> > resubmit) *did* in fact cause 'i686' to be recognized by
> > 'PackageJob.py' (but only as a "base arch" -- not as an "optional
> > arch" like we need it to be)
> >
> > MY QUESTIONS:
> > 1. Why is the *optional_arches* tag -- in the [Arches] section of
> > our /etc/plague/server/*.cfg files -- *no longer* recognized *after*
> > upgrading to plague-0.5.0?
> > 2. What are some things I can try, that might help resolve the above
> > (i.e. getting *plague-0.5.0* to recognize 'i686' as an *optional
> > arch*?)
> >
> > Any help will be much appreciated! .. I have run out of ideas, and
> > things to try... ;-(
> >
> > Thanks,
> > --Joe
> > --
> > Fedora-buildsys-list mailing list
> > Fedora-buildsys-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
>
-Joe
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
