1229008 - Make usage of proxxy optional in different mozharness modules

Status: RESOLVED WONTFIX

(Release Engineering :: Applications: MozharnessCore, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

+++ This bug was initially created as a clone of Bug #1228544 +++

As we have seen on bug 1228544 the forced usage of proxxy can cause several scripts to fail which are not intended to be run in the releng network. For now this is definitely affecting the checkout step in combination with hgtool and gittool. But other modules might also be affected.

(In reply to Jordan Lund (:jlund) from comment bug 1228544 comment 11)
> > Is there a reason why we force setting the proxxy in install_module?
> > 
> > https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/
> > base/python.py#257
> 
> if I understand your question correctly, I think it's because we were
> focused on production. If you want, feel free to add a flag that skips using
> Proxxy for other use cases.

(In reply to Dustin J. Mitchell [:dustin] from comment bug 1228544 comment 12)
> > Dustin, maybe you have an idea about the networking related stuff... Our
> > Ubuntu nodes in qa.scl3.mozilla.com cannot download python packages from
> > http://pypi.pub.build.mozilla.org.proxxy1.srv.releng.scl3.mozilla.com/pub.
> > But I can ping this host. The network ACLs in place are set for all nodes in
> > qa.scl3.mozilla.com, so it should affect all platforms.
> 
> Proxxy isn't intended for use outside of the releng network, and the
> firewall rules enforce that.

Comment 1

[Chris AtLee [:catlee]]

proxxy is dead