Bug 1449773

Summary:	Finish the installation and freebsd10.3.rht and clean password in jenkins
Product:	[Community] GlusterFS	Reporter:	Michael S. <misc>
Component:	project-infrastructure	Assignee:	Nigel Babu <nigelb>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, mscherer, nigelb
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-04 02:11:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael S. 2017-05-10 16:04:15 UTC

A 2nd freebsd builder was installed in the community cage. However, the jenkins authentication is not done by ansible, and is pretty messy, as there is 5 differents password, written nowhere (but can be extracted from jenkins configuration), and all listed as "not used" by Jenkins (which by itself is what I would qualify as "fake news" if I was president, but I disgress). 

We should switch to ssh keys for authentication, and if possible, restrict it by ip. And place that in ansible.

Comment 1 Nigel Babu 2017-05-22 03:03:52 UTC

The actual passwords are on my machine and I have code to put it in Ansible. We currently have two sets of passwords. One for the RAX machines and one for the cage machine. I'll commit it into the private repo and make it part of the jenkins-builder role. Assigning this bug to me to fix that.

Comment 2 Amar Tumballi 2018-08-29 03:53:37 UTC

Lot of time since no activity on this bug. We have either fixed it already or it is mostly not critical anymore!

Please re-open the bug if the issue is burning for you, or you want to take the bug to closure with fixes.

Comment 3 Nigel Babu 2019-02-04 02:11:48 UTC

This is now fixed. We build on the internal freebsd builder now.