Project

General

Profile

Actions
Copy link

Bug #5745

closed

User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems

User story #5296: Create the logic to get execution reports for "error only" mode

Bug #5710: Rudder 3.0 is missing migration elements (SQL script and property)

Rudder 3.0 configid migration uses the wrong condition

Added by Matthieu CERDA over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1
Assignee:
Jonathan CLARKE
Category:
System integration
Target version:
3.0.0~beta1
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

In:

# 3.0.0: Add the nodeConfigId column in the ReportsExecution table and add the nodes_info table
STEP="Add the nodeConfigId column in the ReportsExecution table and add the nodes_info table" 

RES=$(${PSQL} -t -d rudder -c "select count(1) from pg_class where relname = 'nodes_info'")
if [ $RES -ne 0 ]; then
  ${PSQL} -d rudder -f ${RUDDER_UPGRADE_TOOLS}/dbMigration-2.11-2.12-add-nodeconfigids-columns.sql > /dev/null 2>&1
fi

"if [ $RES -ne 0 ]; then" should be "if [ $RES -eq 0 ]; then"

Actions
Copy link

Also available in: Atom PDF