Actions
Bug #7597
closed
When upgrading from 2.11 to 3.1.5, the root server gets components in No Reports
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:
27
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 :'(
Updated by 
Updated by 
Updated by
Actions