Troubleshoot guide for node replacement #205

scalar-boney · 2020-09-14T06:13:36Z

Troubleshoot guide for node replacement

Recover from accidental deletion of a node
Recover a node with existing data disk from accidental deletion of a node

docs/TroubleshootingGuide.md

feeblefakie · 2020-09-15T00:45:05Z

docs/TroubleshootingGuide.md

@@ -0,0 +1,34 @@
+# Troubleshoot Guide
+
+This guide explains how to replace a node when the node cannot be replaced with normal procedures. This is especially useful when the node or os-disk is accidentally terminated in the **Azure** environment.


It should be a general troubleshooting guide, so it's weird to see one of the cases in the introductory sentence. It should be just one of the cases.

Sorry for the inconvenience.
Document modified based on the review comment.

Co-authored-by: Hiroyuki Yamada <mogwaing@gmail.com>

docs/TroubleshootingGuide.md

Co-authored-by: Hiroyuki Yamada <mogwaing@gmail.com>

feeblefakie

Overall the doc is too specific to what you did and not really generalized and formatted as a troubleshooting guide.
I left some suggestions on only part of it but anyways please update all based on them.
The point is that the readers of the doc don't really know what you did, and faced some troubles and came here to fix the troubles. Please assume that.

feeblefakie · 2020-09-17T00:47:36Z

docs/TroubleshootingGuide.md

+
+This is a guide for troubleshooting scalar-terraform environment. 
+
+Use this Troubleshooting Guide to:


We don't need it.

feeblefakie · 2020-09-17T00:50:46Z

docs/TroubleshootingGuide.md

+- Accidental deletion of resources
+
+## Accidental deletion of resources
+These troubleshooting steps can be used when the node cannot be replaced with normal procedures. This is especially useful when the node or os-disk is accidentally terminated in the **Azure** environment.


Not consistent with the title and not really explaining the situation so it's not understandable...

Suggested change

These troubleshooting steps can be used when the node cannot be replaced with normal procedures. This is especially useful when the node or os-disk is accidentally terminated in the **Azure** environment.

When you accidentally delete a resource manually without terraform, it causes some inconsistencies between the actual state of resources and the state that terraform knows. Thus, you might need to take some extra actions to recover from such situations depending on the Cloud you use. The following explains how to recover from such cases.

Thank you for your suggestion.
Review changes updated.

feeblefakie · 2020-09-17T00:53:08Z

docs/TroubleshootingGuide.md

+- Replace accidentally removed node or os-disk
+- Replace accidentally removed cassandra node or os-disk with existing data disk
+
+### Replace accidentally removed node or os-disk


Suggested change

### Replace accidentally removed node or os-disk

### Recover from accidental deletion of a node or an OS disk

Thank you for your suggestion.
Review changes updated.

feeblefakie · 2020-09-17T00:56:43Z

docs/TroubleshootingGuide.md

+* Terminate the node If the os-disk is deleted.
+* Follow [Node Replacement](NodeReplacement.md)
+
+### Replace accidentally removed cassandra node or os-disk with existing data disk


Suggested change

### Replace accidentally removed cassandra node or os-disk with existing data disk

### Recover from accidental deletion of a Cassandra node ... (not sure how to fix)

What do you mean os-disk with existing data disk ?

Thank you for your suggestion.
Review changes updated.

What do you mean os-disk with existing data disk ?
Sorry for the inconvenience.
I mean recover accidentally removed node with existing data disk.

tei-k · 2020-09-18T00:16:16Z

docs/TroubleshootingGuide.md

+
+Please try the following
+* Delete the os-disk If the node is terminated.
+* Terminate the node If the os-disk is deleted.


Is this is a very rare case ? I think we can't delete only os-disk from console. 🤔

Thank you for your valuable comment.
Yes, It is not possible through the console because os-disk deletion not possible without terminating VM.

I have modified the document accordingly.

feeblefakie · 2020-09-23T05:51:48Z

docs/TroubleshootingGuide.md

+- Recover from accidental deletion of a node
+- Recover a node with existing data disk from accidental deletion of a node
+
+### Recover from accidental deletion of a node


Is it needed for AWS as well? Only for Azure?
It must be described.

Is it needed for AWS as well?

no

Only for Azure?

yes

It must be described.

Document modified respectively.

When you accidentally delete a resource manually without terraform, it causes some inconsistencies between the actual state of resources and the state that terraform knows. Thus, you might need to take some extra actions to recover from such situations depending on the Cloud you use. The following explains how to recover from such cases in the AZURE scalar-terraform environment.

feeblefakie · 2020-09-23T06:21:40Z

docs/TroubleshootingGuide.md

+This is a guide for troubleshooting scalar-terraform environment. 
+
+## Accidental deletion of resources
+When you accidentally delete a resource manually without terraform, it causes some inconsistencies between the actual state of resources and the state that terraform knows. Thus, you might need to take some extra actions to recover from such situations depending on the Cloud you use. The following explains how to recover from such cases in the AZURE scalar-terraform environment.


This sentence is a general one. Write azure thing in each section below.

Sorry for the inconvenience.
Document updated with suggestions.

feeblefakie · 2020-09-23T06:21:48Z

docs/TroubleshootingGuide.md

+## Accidental deletion of resources
+When you accidentally delete a resource manually without terraform, it causes some inconsistencies between the actual state of resources and the state that terraform knows. Thus, you might need to take some extra actions to recover from such situations depending on the Cloud you use. The following explains how to recover from such cases in the AZURE scalar-terraform environment.
+
+- Recover from accidental deletion of a node


We don't need the list.

Thank you for your suggestion.
document updated without list.

feeblefakie · 2020-09-23T06:22:02Z

docs/TroubleshootingGuide.md

+- Recover from accidental deletion of a node
+- Recover a node with existing data disk from accidental deletion of a node
+
+### Recover from accidental deletion of a node


Suggested change

### Recover from accidental deletion of a node

### Recover from accidental deletion of a node in Azure

Thank you for your suggestion.
Document updated with suggestions.

feeblefakie · 2020-09-23T06:22:21Z

docs/TroubleshootingGuide.md

+* Delete the os-disk If the node is terminated.
+* Follow [Node Replacement](NodeReplacement.md)
+
+### Recover a node with existing data disk from accidental deletion of a node


Suggested change

### Recover a node with existing data disk from accidental deletion of a node

### Recover a node with existing data disk from accidental deletion of a node in Azure

Thank you for your suggestion.
Document updated with suggestions.

feeblefakie · 2020-09-23T06:22:46Z

docs/TroubleshootingGuide.md

+- Recover a node with existing data disk from accidental deletion of a node
+
+### Recover from accidental deletion of a node
+If you accidentally delete a node that does not have an additional data disk, you can recover it in the following steps. It is mainly applicable for scalardl, envoy, cassy, reaper, monitor and ca nodes.


Suggested change

If you accidentally delete a node that does not have an additional data disk, you can recover it in the following steps. It is mainly applicable for scalardl, envoy, cassy, reaper, monitor and ca nodes.

If you accidentally delete a node that does not have an additional data disk in Azure, you can recover it in the following steps. It is mainly applicable for scalardl, envoy, cassy, reaper, monitor and ca nodes.

Thank you for your suggestion.
Document updated with suggestions.

feeblefakie · 2020-09-23T06:22:56Z

docs/TroubleshootingGuide.md

+* Follow [Node Replacement](NodeReplacement.md)
+
+### Recover a node with existing data disk from accidental deletion of a node
+If you accidentally delete a node that contains an additional data disk, you can recover that node with an existing data disk using the following steps.


Suggested change

If you accidentally delete a node that contains an additional data disk, you can recover that node with an existing data disk using the following steps.

If you accidentally delete a node that contains an additional data disk in Azure, you can recover that node with an existing data disk using the following steps.

Thank you for your suggestion.
Document updated with suggestions.

feeblefakie · 2020-09-23T06:23:24Z

docs/TroubleshootingGuide.md

+This is a guide for troubleshooting scalar-terraform environment. 
+
+## Accidental deletion of resources
+When you accidentally delete a resource manually without terraform, it causes some inconsistencies between the actual state of resources and the state that terraform knows. Thus, you might need to take some extra actions to recover from such situations depending on the Cloud you use. The following explains how to recover from such cases in the AZURE scalar-terraform environment.


Suggested change

When you accidentally delete a resource manually without terraform, it causes some inconsistencies between the actual state of resources and the state that terraform knows. Thus, you might need to take some extra actions to recover from such situations depending on the Cloud you use. The following explains how to recover from such cases in the AZURE scalar-terraform environment.

When you accidentally delete a resource manually without terraform, it causes some inconsistencies between the actual state of resources and the state that terraform knows. Thus, you might need to take some extra actions to recover from such situations depending on the Cloud you use.

Thank you for your suggestion.
Document updated with suggestion details.

feeblefakie

LGTM

scalar-boney added 3 commits September 14, 2020 14:02

troubleshoot doc [skip ci]

1447c73

troubleshoot doc modified [skip ci]

62cf823

troubleshoot doc modified [skip ci]

7e40ef5

scalar-boney requested review from feeblefakie and tei-k September 14, 2020 06:14

feeblefakie requested changes Sep 15, 2020

View reviewed changes

scalar-boney and others added 2 commits September 15, 2020 10:02

Update docs/TroubleshootingGuide.md

3121a72

Co-authored-by: Hiroyuki Yamada <mogwaing@gmail.com>

review modification [skip ci]

c2c74d8

feeblefakie requested changes Sep 16, 2020

View reviewed changes

docs/TroubleshootingGuide.md Outdated Show resolved Hide resolved

scalar-boney and others added 2 commits September 16, 2020 14:39

Update docs/TroubleshootingGuide.md

449a8db

Co-authored-by: Hiroyuki Yamada <mogwaing@gmail.com>

modified based on review

19bdb67

feeblefakie requested changes Sep 17, 2020

View reviewed changes

tei-k reviewed Sep 18, 2020

View reviewed changes

document modification [skip ci]

17c02a3

feeblefakie requested changes Sep 23, 2020

View reviewed changes

review modification [skip ci]

0284a8f

scalar-boney requested a review from feeblefakie September 23, 2020 06:11

feeblefakie requested changes Sep 23, 2020

View reviewed changes

Review suggestion added [skip ci]

920e858

scalar-boney requested a review from feeblefakie September 23, 2020 06:54

feeblefakie approved these changes Sep 25, 2020

View reviewed changes

feeblefakie merged commit eaf41b7 into master Sep 25, 2020

feeblefakie deleted the troubleshoot-guide branch September 25, 2020 00:42

		@@ -0,0 +1,34 @@
		# Troubleshoot Guide

		This guide explains how to replace a node when the node cannot be replaced with normal procedures. This is especially useful when the node or os-disk is accidentally terminated in the Azure environment.


		This is a guide for troubleshooting scalar-terraform environment.

		Use this Troubleshooting Guide to:

	These troubleshooting steps can be used when the node cannot be replaced with normal procedures. This is especially useful when the node or os-disk is accidentally terminated in the Azure environment.
	When you accidentally delete a resource manually without terraform, it causes some inconsistencies between the actual state of resources and the state that terraform knows. Thus, you might need to take some extra actions to recover from such situations depending on the Cloud you use. The following explains how to recover from such cases.

	### Replace accidentally removed node or os-disk
	### Recover from accidental deletion of a node or an OS disk

	### Replace accidentally removed cassandra node or os-disk with existing data disk
	### Recover from accidental deletion of a Cassandra node ... (not sure how to fix)

	### Recover a node with existing data disk from accidental deletion of a node
	### Recover a node with existing data disk from accidental deletion of a node in Azure

	If you accidentally delete a node that does not have an additional data disk, you can recover it in the following steps. It is mainly applicable for scalardl, envoy, cassy, reaper, monitor and ca nodes.
	If you accidentally delete a node that does not have an additional data disk in Azure, you can recover it in the following steps. It is mainly applicable for scalardl, envoy, cassy, reaper, monitor and ca nodes.

	If you accidentally delete a node that contains an additional data disk, you can recover that node with an existing data disk using the following steps.
	If you accidentally delete a node that contains an additional data disk in Azure, you can recover that node with an existing data disk using the following steps.

Troubleshoot guide for node replacement #205

Troubleshoot guide for node replacement #205

Uh oh!

Conversation

scalar-boney commented Sep 14, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

feeblefakie left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

feeblefakie left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

scalar-boney commented Sep 14, 2020 •

edited

Loading