Bug #7597: When upgrading from 2.11 to 3.1.5, the root server gets components in No Reports - Rudder - Issue Tracker

Actions

Copy link

Bug #7597

closed

When upgrading from 2.11 to 3.1.5, the root server gets components in No Reports

Added by Nicolas CHARLES over 8 years ago. Updated almost 7 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Web - Config management

Target version:

Pull Request:

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Technique editor | Rudder settings

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

I upgraded Rudder 2.11 to 3.1.5, and got No Reports status for component "Check jetty boot script" on the server root. This component was removed in 3.1, so it should not expect reports.
Generated promises don't contains this part, and the metadata.xml neither

Upgrade logs do show that the techniques where reloaded, and that promises were regenerated
Policy update started automatically
Policy update finished successfully

Reloading tehcnique don't change anything, but clearing caches do fix the issue

Happens in 3.1.5, but may happen on any version :'(

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Alexis Mousset over 8 years ago

Related to Bug #7645: Missing reporting for jetty and slapd on relay added

Actions

Copy link

Updated by Jonathan CLARKE over 8 years ago

I have seen a similar issue on a 3.1.5 version where the expected reports clearly did not match the reports in the current policy. Clearing caches solved my issue too.

Actions

Copy link

Updated by Jonathan CLARKE about 7 years ago

Severity set to Minor - inconvenience | misleading | easy workaround
User visibility set to Operational - other Techniques | Technique editor | Rudder settings

Actions

Copy link