nbslave7{d..f} were the entries created by Vijay last week, which were
resolving to nbslave71; there were no actual vms on rackspace. I had
disabled nbslave71 at that point in time to reboot it, but I think I
forgot to re-enable it.~kaushal On Wed, Jun 17, 2015 at 7:21 PM, Emmanuel Dreyfus <[email protected]> wrote: > Status of NetBSD slave VM: > > 1 booked: nbslave71 > It is noted to be disconnected by amarts. Is usage over? > > 3 removed from rackspace but still in jenkins: nbslave7d, nbslave7e, nbslave7f > > 6 active: nbslave72, nbslave77, nbslave7c, nbslave7g, nbslave7i, nbslave7j > > 3 offline: nbslave74 nbslave75 nbslave79 > The 3 DNS records do not resolve (timeout) from build.gluster.org, > while they do at mine. Adding them to /etc/hosts helps a lot on the > command line, and it becomes possible to connect to port 22. > But jenkins is still unable to connect and launch the agent. > tcpdump on build.gluster;org shows it does not even tries. > > Perhaps there is a name cache in jenkisn and it needs to be restarted? > I am leaving the /etc/hosts file loaded with nbslave74 nbslave75 nbslave79 > > -- > Emmanuel Dreyfus > [email protected] > _______________________________________________ > Gluster-infra mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-infra _______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
