How to stop fabric service cluster upgrade downtime?

Question

I have a working tissue cluster that seems to be stuck in the rollback phase of automatic updates for more than seven days.

This is the result of Get-ServiceFabricClusterUpgrade:

TargetCodeVersion             : 5.5.216.0
TargetConfigVersion           : 2
StartTimestampUtc             : 15/06/2017 23:44:40
FailureTimestampUtc           : 16/06/2017 01:41:48
FailureReason                 : HealthCheck
UpgradeState                  : RollingBackInProgress
UpgradeDuration               : 7.14:13:10
CurrentUpgradeDomainDuration  : 7.12:16:03
CurrentUpgradeDomainProgress  : 0

NodeName            : xxxxxxxxxxxxxxxxxxxxx
UpgradePhase        : PreUpgradeSafetyCheck
PendingSafetyChecks :
WaitForInbuildReplica - PartitionId: xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx
NextUpgradeDomain             : 1
UpgradeDomainsStatus          : { "0" = "InProgress";
                                  "1" = "Pending";
                                  "2" = "Pending";
                                  "3" = "Pending";
                                  "4" = "Pending" }

The only other cmdlets in the Service Fabric powershell module that seem to be related are Start-ServiceFabricClusterUpgrade, Resume-ServiceFabricClusterUpgradeand Update-ServiceFabricClusterUpgrade.

I tried Start-ServiceFabricClusterUpgradeusing the switch -Force, hoping that it will cancel the existing dangling one and launch a new one, but unfortunately not. I also restarted the node, which is running, but that doesn't matter either.

In the absence of a Stop-ServiceFabricClusterUpgrade, is there anything else I can do to stop this process?

Answer 1

, , , .

, . VMSS, , , , . , , .

Answer 2

, :

• ( ). , Powershell, Azure.

Answer 3

,

"Upgrading UpgradePhase PreUpgradeSafetyCheck means that before it was completed, there were problems with preparing the upgrade domain. The most common problems in this case are service errors when closing or downgrading the main code paths."

Thus, probably, SF could not close the service executable. The easiest way is to deactivate (restart) the node mentioned in the output from SF Explorer.