Actions
Bug #18014
closedrudder-reports-postinst errors during upgrade from 6.1.0 to 6.1.1
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
32
Name check:
To do
Fix check:
Checked
Regression:
Description
On suse 12, during upgrade from rudder 6.1.0 to 6.1.1, we got:
INFO: Waiting for PostgreSQL to be up... Done /opt/rudder/share/package-scripts/rudder-reports-postinst: line 112: [: too many arguments /opt/rudder/share/package-scripts/rudder-reports-postinst: line 120: [: too many arguments
Corresponding lines in script in rudder-package/rudder-reports/SOURCES/rudder-reports-postinst
:
CHK_PG_DB=$(su - postgres -c "psql -t -c \"select count(1) from pg_catalog.pg_database where datname = '${DBNAME}'\"") CHK_PG_USER=$(su - postgres -c "psql -t -c \"select count(1) from pg_user where usename = '${USERNAME}'\"") # Rudder user if [ ${CHK_PG_USER} -eq 0 ] # <- line 112 then ... # Rudder database if [ ${CHK_PG_DB} -eq 0 ] # <- line 120 then ...
Updated by Benoît PECCATTE over 4 years ago
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
Updated by Benoît PECCATTE over 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2347
Updated by Benoît PECCATTE over 4 years ago
su - invokes a login shell and with some machines prints a banner, which is not what we want
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.2 to 6.1.3
Updated by Benoît PECCATTE over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|9a9293e6b222b90857ec120ef2b64561dbd8e741.
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.3 to 6.1.2
Updated by François ARMAND over 4 years ago
- Fix check changed from To do to Checked
Updated by François ARMAND over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.2 which was released today.
Actions