So I noticed (by accident) that relengwebadm has python packages for at least relengapi installed *globally* (and installed in the relevant service python venvs) I'm doubtful that was intentional, but quite likely that *any* of us are responsible. (myself included). We should clean this up, but I didn't want to go uninstalling global python packages at-will here, since I don't know what is actually required globally for normal web-ops operations. I do fully expect this to be not-a-big-deal in the end. Relatedly I suspect we shouldn't be doing relengapi and related updates via root@ if we can help it (as in, either have a dedicated user that can do these updates, but doesn't need to have root privs for everything, or allow us all to be in a group that can sudo for the root-only needs, etc.) I'm also not sure how much effort is worth spending on this bug due to the eventual goal of moving releng's cluster to aws...

That was probably me while trying to get the update scripts running. 'pip' is, unfortunately, installed systemwide, which means forgetting to activate a virtualenv installs things globally. Uninstalling relengapi and any other blueprints on relengwebadm is not going to hurt anything -- nothing very Pythony runs there. And hopefully nothing's installed on the webheads. I wouldn't worry too much about chasing down any other global packages not installed via RPM -- they're unlikely to hurt anything.

:dustin, :callek, do you want a changewindow or CAB window for removing the [UNDEFINED] packages, or should we just coordinate on IRC sometime? :callek, what is the complete list of packages you propose we uninstall for cleanup?

(In reply to Richard Soderberg [:atoll] from comment #2) > :dustin, :callek, do you want a changewindow or CAB window for removing the > [UNDEFINED] packages, or should we just coordinate on IRC sometime? > > :callek, what is the complete list of packages you propose we uninstall for > cleanup? :atoll We can cleanup relengapi* easily. This won't need a downtime. As far as "the complete list we should cleanup" I was considering "anything not part of the normal webops deployment", which *should* be all safe and not need a downtime. That said, we have plans to move the stuff hosted on the cluster to AWS this year, so I'm not sure there is a strong reason for the added headspace/work. Nor am I aware of what packages we should clean. I mostly filed this as a "I noticed it, might as well file it -- we might decide to WONTFIX" I don't have strong feelings either way.

[root@relengwebadm.private.scl3 ~]# pip list | grep relengapi relengapi (0.1.1) I think we should leave it at that, unless you (Richard) have an easy way to determine which of the other packages in 'pip list' are not installed via yum. I don't think this is worth taking much time on.

Cleanup is nice, but this offers no value in exchange for slight risk, so I'm accepting the WONTFIX path. If there were any impact whatsoever to the presence of these packages, I might say otherwise. Feel free to reopen if desired.