Closed
Bug 569790
Opened 14 years ago
Closed 14 years ago
Maemo Try slaves don't get updates from puppet
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(2 files, 1 obsolete file)
3.73 KB,
text/plain
|
Details | |
1.11 KB,
patch
|
lsblakk
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
Several issues here * the slaves (try-linux-slave02 and 03) have different version of buildbot, because they're not rebooting and hence not running puppet * as a result try-linux-slave03 still has buildbot 0.8.0rc3, and 02 still has 0.7.10p1 * on 03 we are failing to scp the files up to build.m.o because the path is a unicode string. The exception in the slave log is the attached with this comment.
Assignee | ||
Comment 1•14 years ago
|
||
Sprinkle some str() around so that buildbot 0.8.0 doesn't barf. This is almost deprecated code, only maemo is using it still.
Assignee: nobody → nrthomas
Attachment #448957 -
Flags: review?(rail)
Comment 2•14 years ago
|
||
Comment on attachment 448957 [details] [diff] [review] Potential fix str() should fix it. I had the similar problems passing int to setCommand without wrapping it with str().
Attachment #448957 -
Flags: review?(rail) → review+
Assignee | ||
Comment 3•14 years ago
|
||
Comment on attachment 448957 [details] [diff] [review] Potential fix Letting puppet update the two slaves gets green builds without this patch. Thanks for the r+ anyway.
Attachment #448957 -
Attachment is obsolete: true
Assignee | ||
Comment 4•14 years ago
|
||
Morphing this now ... The remaining issues are * these two slaves don't reboot after a build, so they never run puppet to pick up fixes * anything distributed via http://production-puppet doesn't work because the firewall doesn't allow that traffic out of the sandbox network The latter means we don't install the yasm rpm.
Blocks: 520227
Priority: -- → P2
Summary: Maemo Try builds half-busted → Maemo Try slaves don't get updates from puppet
Assignee | ||
Comment 5•14 years ago
|
||
This should get us polling puppet.
Attachment #448967 -
Flags: review?(lsblakk)
Assignee | ||
Comment 6•14 years ago
|
||
Bug 569806 to open the firewall up.
Comment 7•14 years ago
|
||
(In reply to comment #6) > Bug 569806 to open the firewall up. Thanks for catching this, Nick.
Updated•14 years ago
|
Attachment #448967 -
Flags: review?(lsblakk) → review+
Assignee | ||
Comment 8•14 years ago
|
||
Comment on attachment 448967 [details] [diff] [review] Rebooting after each build http://hg.mozilla.org/build/buildbot-configs/rev/7a767539bd27
Attachment #448967 -
Flags: checked-in+
Assignee | ||
Comment 9•14 years ago
|
||
sm-try-master reconfig'd but there was an exception: 2010-06-03 14:30:39-0700 [Broker,16,10.2.76.36] BuildSlave.sendBuilderList (<BuildSlave 'try-mac-slave04', current builders: >) failed 2010-06-03 14:30:39-0700 [Broker,16,10.2.76.36] Unhandled Error Traceback (most recent call last): Failure: twisted.spread.pb.PBConnectionLost: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion. which is odd given there are no mac builders anymore, and this master had a restart after they got removed. Also no 'configuration update finished', but it looks like the maemo factory got updated. Letting it run before more drastic action.
Assignee | ||
Comment 10•14 years ago
|
||
Factory was updated. There's a ~7 minute hang in puppet before it gives up on pulling the yasm rpm, which will go away when the firewall is modified.
Assignee | ||
Comment 11•14 years ago
|
||
These two slaves are up to date and will stay that way.
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•