Page MenuHomePhabricator

/usr/local/bin/ is outdated
Closed, ResolvedPublic


While doing T156174, I found this It checks if it is on bastion, but accepts only tools-bastion-01, which doesn't even exist anymore. As the script is only installed on bastions, I'd question the usefulness of this check.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript references neither exec-manage nor the scripts under modules/toollabs/files/gridscripts/ at the moment :-) (and the SOP in README in the latter does not seem to be documented on either). The procedure in README has courtesy mails to the owners of jobs to be deleted/rescheduled, I don't know if this is necessary/useful to keep.

I would suggest to wait for the next time a node needs to be drained, then document which scripts were actually run at and afterwards remove everything unused.

scfc triaged this task as Low priority.Feb 16 2017, 7:17 PM
scfc moved this task from Backlog to Ready to be worked on on the Toolforge board.

Change 605345 had a related patch set uploaded (by BryanDavis; owner: Bryan Davis):
[operations/puppet@production] toolforge: remove legacy script

Change 605345 merged by Bstorm:
[operations/puppet@production] toolforge: remove legacy script

Mentioned in SAL (#wikimedia-cloud) [2020-06-15T21:28:27Z] <bstorm_> cleaned up on the tools bastions T157792

Mentioned in SAL (#wikimedia-cloud) [2020-06-15T21:54:27Z] <bstorm_> removed from toolsbeta bastion T157792

Bstorm claimed this task.