Resolved -
This incident has been resolved.
Dec 12, 07:08 UTC
Monitoring -
The fix for the 7.5 upgrade issue was rolled to all regions in Azure, along with AWS and GCP. We will monitor the issue for the next 6 hours before closing the incident.
Dec 12, 00:16 UTC
Update -
We have rolled out the fix for the 7.5 upgrade issue to all regions in AWS and GCP. The fix for Azure was rolled back in the other currently open incident. The estimated time to fix for Azure will be within the next 24 hours. We will update when Azure is resolved as well.
Dec 11, 18:14 UTC
Update -
We've identified a fix for this issue and are currently testing before deploying the fix into production. We expect to have this fix deployed by the end of next week (December 13th).
We will update this status page when the fix has been deployed and validated in production, or if the situation changes.
Dec 6, 06:30 UTC
Update -
We are continuing to work on a fix for this issue.
We will update this incident within the next 12 hours with further details on when this issue will be fixed.
If you encounter any other issues, or need further help upgrading your clusters to 7.5 please contact us via
support@elastic.co
Dec 5, 19:32 UTC
Identified -
We've uncovered an issue with upgrading a small percentage of clusters to the latest 7.5 release.
Clusters which have previously been monitored by a different Cloud deployment, but currently have monitoring disabled or are self monitored, will fail to elect new master nodes when attempting to upgrade to 7.5. Clusters with monitoring currently enabled, or which have never had external monitoring enabled will not be impacted by this issue.
We're working on fixing this workflow, and will update this incident when we have an estimate on a fix becoming available. In the meantime, customers can upgrade affected clusters by re-enabling external monitoring before attempting the upgrade.
As part of this issue, customers are unable to disable external monitoring on 7.5 clusters via the Cloud console. External monitoring can be disabled in 7.5 clusters by:
* Disabling monitoring in the Cloud Console
* Sending the following request in the API Console
PUT _cluster/settings
{
"persistent": {
"xpack.monitoring.collection.enabled": false,
"xpack.monitoring.exporters.found-user-defined": {
"type": "http",
"enabled": false
}
}
}
We will update this incident within the next 12 hours with further details on when this issue will be fixed.
If you encounter any other issues, or need further help upgrading your clusters to 7.5 please contact us via
support@elastic.co
Dec 5, 04:55 UTC