Project

General

Profile

Actions
Copy link

Bug #2093

closed

When a Node is deleted, or a Node is accepted in Rudder and something bad happen, the Machine on which the Node is is always deleted

Added by Nicolas CHARLES about 13 years ago. Updated over 12 years ago.

Status:
Rejected
Priority:
5 (lowest)
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
2.4.0~alpha7
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

There is no verification that another Node is linked to this Machine, so it might break consistency of data
It's not that important, because we don't have often several Node on the same Machine (it's not the VM host)

Actions
Copy link
 #1

Updated by Jonathan CLARKE about 13 years ago

  • Category changed from Architecture - Code maintenance to Web - Nodes & inventories
Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha2 to 2.4.0~alpha3
Actions
Copy link
 #3

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha3 to 2.4.0~alpha4
Actions
Copy link
 #4

Updated by François ARMAND almost 13 years ago

  • Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
Actions
Copy link
 #5

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6
Actions
Copy link
 #6

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7
Actions
Copy link
 #7

Updated by Nicolas CHARLES over 12 years ago

  • Status changed from New to Rejected

It as been resolved as a side effect of #2094

Actions
Copy link

Also available in: Atom PDF