Closed Bug 1396266 Opened 7 years ago Closed 7 years ago

Intermittent OSX "The executable '/tools/buildbot/bin/python' is not found; not creating virtualenv!"

Categories

(Release Engineering :: General, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: intermittent-bug-filer, Assigned: dhouse)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

ITYM "t-yosemite-r7-394 is broken".
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
And t-yosemite-r7-0115 apparently...
Can we please give r7-0115 the same treatment as 0394?
Flags: needinfo?(aobreja)
This machine t-yosemite-r7-0115 like all machines between t-yosemite-r7-[030-390] is configured to ran job in Taskcluster so it doesn't need /tools/buildbot at all.The problem here was that it seems to have been enabled (I don't know why or by whom) and this caused these issues since the machine is configured to use generic workers. The problem is now solved,machine was disabled from buildbot so will ran under Taskcluster and I re-image it. For more details please check the link bellow: https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slavetype.html?class=test&type=t-yosemite-r7
Flags: needinfo?(aobreja)
Flags: needinfo?(aobreja)
In bug 1335353 I removed all references to /tools/buildbot. I then reimaged this machine to no longer have /tools/buildbot and observed it to run a bunch of tasks successfully. But I didn't think to uplift the fix to beta.. that was dumb. So this particular host (and anything else reimaged in the interim) is going to fail to build beta pushes until uplift. I've killed the worker on the host. Once it's uplifted (I'll reopen bug 1335353), it will be good to go. Buildduty folks: until that's done, please don't put reimaged yosemite machines into production.
Assignee: nobody → dustin
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
This is not the same as t-yosemite-r7-394: /tools/buildbot/bin/virtualenv vs. /tools/virtualenv/bin/virtualenv
I think the easier fix will be to add some symlinks so that this keeps working, and let the change ride the trains. A few symlinks and the virtualenv works: [root@t-yosemite-r7-0115.test.releng.scl3.mozilla.com ~]# mkdir -p /tools/buildbot/bin [root@t-yosemite-r7-0115.test.releng.scl3.mozilla.com ~]# ln -s /tools/python27/bin/python2.7 /tools/buildbot/bin/python [root@t-yosemite-r7-0115.test.releng.scl3.mozilla.com ~]# mkdir -p /tools/misc-python [root@t-yosemite-r7-0115.test.releng.scl3.mozilla.com ~]# ln -s /tools/virtualenv/bin/virtualenv /tools/misc-python/virtualenv.py [root@t-yosemite-r7-0115.test.releng.scl3.mozilla.com ~]# /tools/buildbot/bin/python /tools/misc-python/virtualenv.py You must provide a DEST_DIR Usage: virtualenv.py [OPTIONS] DEST_DIR
Flags: needinfo?(aobreja)
Jake has agreed to write up, test, and land a patch to make the dirs and symlinks above. I think this can go away after ESR52 is closed.
Assignee: dustin → jwatkins
Comment on attachment 8905194 [details] [diff] [review] Creates dirs and symlinks Review of attachment 8905194 [details] [diff] [review]: ----------------------------------------------------------------- ::: modules/toplevel/manifests/worker/releng/generic_worker/test.pp @@ +33,5 @@ > + ensure => link, > + target => '/tools/virtualenv/bin/virtualenv', > + require => Class[ 'dirs::tools::misc_python', > + 'packages::mozilla::py27_virtualenv' ]; > + } This refers to classes from toplevel::worker::releng.. maybe it would be better there? I'm happy with this too - whatever you think is best.
Attachment #8905194 - Flags: review?(dustin) → review+
Assignee: jwatkins → dhouse
I looked at changing the location, but I don't know enough context and I'm guessing that applying the fix only to toplevel::worker::releng::generic_worker::test is enough.
Attachment #8905194 - Flags: checked-in+
Orange factor doesn't show anything on or after the 7th when this landed.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
(In reply to Dustin J. Mitchell [:dustin] from comment #12) > Comment on attachment 8905194 [details] [diff] [review] > This refers to classes from toplevel::worker::releng.. maybe it would be > better there? > > I'm happy with this too - whatever you think is best. :dhouse, Dustin has a good point. Could you make sure this moved to the toplevel::worker::releng just to clean this up?
Status: RESOLVED → REOPENED
Flags: needinfo?(dhouse)
Resolution: FIXED → ---
(In reply to Jake Watkins [:dividehex] from comment #17) > (In reply to Dustin J. Mitchell [:dustin] from comment #12) > > Comment on attachment 8905194 [details] [diff] [review] > > > This refers to classes from toplevel::worker::releng.. maybe it would be > > better there? > > > > I'm happy with this too - whatever you think is best. > > :dhouse, Dustin has a good point. Could you make sure this moved to the > toplevel::worker::releng just to clean this up? Jake, I did not move the worker symlink definitions up a level. Can I close this out or hold it until ESR52 goes away and I can remove the workaround (reverting the patch)? I'm expecting that we will keep using generic-worker on Darwin and that we do not need to move it.
Flags: needinfo?(dhouse) → needinfo?(jwatkins)
QA Contact: catlee
Leave it be.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Flags: needinfo?(jwatkins)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: