Project

General

Profile

Actions

Bug #16009

closed

Missing method in the internal API in 5.0.15

Added by Félix DALLIDET over 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
API
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
67
Name check:
To do
Fix check:
To do
Regression:

Description

This make the nodes webpage unusable nor readable! They are constantly loading when the external-report plugin is installed.

When trying to use the node-external-reports plugin I am blocked by a missing method in the internal API:

2019-10-21 14:00:52.545:WARN:oejs.HttpChannel:qtp943010986-10: /rudder/lift/ajax/F9164678667234DGNM4-00/
java.lang.NoSuchMethodError: com.normation.rudder.web.components.ShowNodeDetailsFromNode.nodeId()Lcom/normation/inventory/domain/NodeId;
        at com.normation.plugins.nodeexternalreports.extension.CreateNodeDetailsExtension.addExternalReportTab(CreateNodeDetailsExtension.scala:66)
        at com.normation.plugins.nodeexternalreports.extension.CreateNodeDetailsExtension.$anonfun$pluginCompose$2(CreateNodeDetailsExtension.scala:56)
        at com.normation.plugins.PluginExtensionPoint.guard(ExtendableSnippet.scala:82)
        at com.normation.plugins.PluginExtensionPoint.guard$(ExtendableSnippet.scala:82)
        at com.normation.plugins.nodeexternalreports.extension.CreateNodeDetailsExtension.guard(CreateNodeDetailsExtension.scala:52)

The method ShowNodeDetailsFromNode.nodeId(id: NodeId) is missing and so, displaying the nodes tabs can not terminate.

Actions #1

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 76 to 75
Actions #2

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 75 to 72
Actions #3

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 72 to 70
Actions #4

Updated by François ARMAND almost 4 years ago

  • Status changed from New to Resolved
  • Priority changed from 70 to 67

It was an internal API compat problem. Rebuilding/publishing plugin corrected it.

Actions

Also available in: Atom PDF