Project

General

Profile

Actions

Bug #6161

closed

Rule details and Directive not accessible if technique version is missing

Added by Vincent MEMBRÉ about 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

I get errors (no page for Directive, and Server cannot be contacted at this time) When I tried to display a Directive tree where one Directive use a Technique in a missing version :(

The error in logs is:

java.util.NoSuchElementException: key not found: 7.0

I found that in 3.0, but it may be present in older versions

Actions #1

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from New to 8
Actions #2

Updated by Vincent MEMBRÉ about 6 years ago

  • Description updated (diff)
Actions #3

Updated by Vincent MEMBRÉ about 6 years ago

I found the origin of the problem in DisplayDirectiveTree... we are getting directly on a Map, which can fail ...

We have several possibilities:
  • Display The directive in the tree, even if some information are missing
  • Display an error in place of the directive
  • Display the directive in Error (so it can be unselected)
  • Display nothing in the tree, but have an error

What do you think Francois?

Actions #4

Updated by François ARMAND about 6 years ago

The good solution is to have the directive in error, so that the user can either delete it or migrate toward a new version. The directive should be disabled, to.

Actions #5

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 3.0.0 to 2.10.9
Actions #6

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.10.9 to 2.11.6
Actions #7

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.11.6 to 3.0.0
Actions #8

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from 8 to Pending technical review
  • Pull Request set to https://github.com/Normation/rudder/pull/803
Actions #9

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #11

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0, which was released on 2015/02/16

Actions

Also available in: Atom PDF