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-infrastructure | Assignee: | Nigel Babu <nigelb> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | 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
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. Yeah, it throws up an error. I'm contemplating if it's worth changing it to be the default domain. 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. |