Bug 1408364

Summary: Let's have failurestat.gluster.org pointing to the same IP as fstat.gluster.org
Product: [Community] GlusterFS Reporter: Nigel Babu <nigelb>
Component: project-infrastructureAssignee: Nigel Babu <nigelb>
Status: CLOSED WORKSFORME QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, gluster-infra, mscherer
Target Milestone: ---   
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: 2017-11-24 09:32:08 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 Nigel Babu 2016-12-23 05:25:41 UTC
The naming is causing confusion. So I'm going to 301 redirect fstat.gluster.org -> failurestat.gluster.org. And eventually phase out fstat.gluster.org.

Comment 1 M. Scherer 2017-08-30 16:39:46 UTC
So I went ahead and added the alias in DNS and on the proxy. I am not sure it is gonna work fine with our letsencrypt automation, I think that's a untested configuration.

Comment 2 Nigel Babu 2017-08-31 02:10:40 UTC
Yeah, it throws up an error. I'm contemplating if it's worth changing it to be the default domain.

Comment 3 M. Scherer 2017-08-31 08:59:47 UTC
Yeah, we would have to force LE to renew the certificate. I did verify that it should work, but on first deployment only. I am gonna fix it manually.