On Wed, Jun 15, 2016 at 08:45:02PM -0700, Amye Scavarda wrote: > Hi all, > > In the spirit of cleaning out access to various things, we're also > taking a look at Rackspace. We've got a great many accounts on there > that probably aren't needed, so we're removing the bulk of them. > > If you're currently needing access to Rackspace and it's been removed, > please file a bug and assign it to me. We'll work through the access > level required.
I do not need access, but by removing my account the associated API key probably has been revoked as well. That means /etc/rax-reboot.conf on build.gluster.org is not correct anymore. This file is used by the reboot-vm job we have in Jenkins. https://build.gluster.org/job/reboot-vm/ https://github.com/gluster/glusterfs-patch-acceptance-tests/tree/master/rax-reboot The VMs and tests seem to have been more stable recently, but it can be useful to reboot a Jenkins slave in case it has issues. This job allowed anyone with a Jenkins account to take care of that. You probably want to replace the /etc/rax-reboot.conf symlink with username and API key from someone else. Thanks! Niels
signature.asc
Description: PGP signature
_______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra