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? 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.
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).
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 'jstodaro(a)abc.com')
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 'jstodaro(a)abc.com')
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(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list