Project

General

Profile

Actions

Bug #4310

closed

Upgrade to 2.9.0 fails when upgrading from 2.8/2.7 due to a missing script

Added by Vincent MEMBRÉ about 10 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

upgrade from Rudder 2.8 / 2.7 to 2.9.0 fails:

Setting up rudder-webapp (2.9.0-squeeze0) ...

Configuration file `/opt/rudder/etc/rudder-web.properties'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** rudder-web.properties (Y/I/N/O/D/Z) [default=N] ? 
INFO: Restarting syslog...Done
INFO: Restarting Apache HTTPd... Done
INFO: Launching script to check if a migration is needed
INFO: Checking if rudder-web.properties database access credentials are all right... LDAP OK,  SQL OK
INFO: Checking if inventory-web.properties database access credentials are all right... LDAP OK,  SQL skipped
INFO: Checking LDAP service status... OK
INFO: Checking PostgreSQL service status... OK
dpkg: error processing rudder-webapp (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of rudder-server-root:
 rudder-server-root depends on rudder-webapp (= 2.9.0-squeeze0); however:
  Package rudder-webapp is not configured yet.
dpkg: error processing rudder-server-root (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      configured to not write apport reports
                                                                            Errors were encountered while processing:
 rudder-webapp
 rudder-server-root
E: Sub-process /usr/bin/dpkg returned an error code (1)

However rudder will work right after the upgrade, all features from RUdder 2.9 will work, main problem will be that all your previous events logs and change request will not be displayed.

To workaround this:

THis due of a not packaged file for rudder-webapp


Related issues 1 (0 open1 closed)

Related to Rudder - User story #4300: Add migration script checking for fileformat 4ReleasedVincent MEMBRÉ2013-12-30Actions
Actions #1

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/203
Actions #2

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset commit:be745eb2d522c90118497e1154ffccb9d1cc0246.

Actions #3

Updated by Matthieu CERDA about 10 years ago

Applied in changeset commit:2e752f3c1e718106c05241f030e1e77951ef5659.

Actions #4

Updated by Jonathan CLARKE about 10 years ago

  • Assignee changed from Jonathan CLARKE to Vincent MEMBRÉ

What ticket introduced this change but forgot this originally? Please link all issues to related ones! Not doing so makes it impossible to track changes.

Actions #5

Updated by Vincent MEMBRÉ about 10 years ago

This bug was introduced in #4300

Actions #6

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.9.1, which was released today.
Check out:

Actions #7

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions

Also available in: Atom PDF