Project

General

Profile

Actions
Copy link

Bug #2724

closed

During a migration from 2.3.8 to 2.4.0~beta3, rudder-upgrade script failed at rudder-server-root stage without any other error message than "Errors were encountered while processing"

Added by Nicolas PERRON over 12 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas PERRON
Category:
Packaging
Target version:
2.4.0~beta3
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Trying to upgrade Rudder from 2.3.8 to 2.4.0~beta3 displayed no error except this:

[master 202c8fc] Upgrade system Techniques - automatically done by rudder-upgrade script
 Committer: root <root@squeezedev.normation.com>
Your name and email address were configured automatically based
on your username and hostname. Please check that they are accurate.
You can suppress this message by setting them explicitly:

    git config --global user.name "Your Name" 
    git config --global user.email you@example.com

If the identity used for this commit is wrong, you can fix it with:

    git commit --amend --author='Your Name <you@example.com>'

 13 files changed, 1232 insertions(+), 163 deletions(-)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1304  100  1304    0     0   107k      0 --:--:-- --:--:-- --:--:--  115k
Restarting Rudder webapp and inventory-endpoint
Stopping Jetty: OK
Setting umask to 0027
Starting Jetty: OK
Errors were encountered while processing:
 rudder-server-root

Current status: 1 broken [+1], 0 updates [-8].
root@squeezedev:~# echo $?
255

Retrying to upgrade works perfectly and install rudder-agent package:

root@squeezedev:~# aptitude upgrade -v
Resolving dependencies...                
The following NEW packages will be installed:
  rudder-agent{a} 
The following partially installed packages will be configured:
  rudder-server-root 
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/21.9 MB of archives. After unpacking 95.0 MB will be used.
Do you want to continue? [Y/n/?] y
(Reading database ... 52014 files and directories currently installed.)
Unpacking rudder-agent (from .../rudder-agent_2.4.0~beta3~git201207290129-squeeze0_amd64.deb) ...
Setting up rudder-agent (2.4.0~beta3~git201207290129-squeeze0) ...
Installing new version of config file /opt/rudder/etc/uuid.hive ...
rudder-agent[4490]: [INFO] Using /etc/default/rudder-agent for configuration
rudder-agent[4493]: [INFO] Using /var/rudder/cfengine-community for CFEngine workdir
rudder-agent[4494]: [INFO] Halting CFEngine Community cf-serverd...
rudder-agent[4498]: [OK] CFEngine Community cf-serverd stopped after 2 seconds
rudder-agent[4499]: [INFO] Halting CFEngine Community cf-execd...
rudder-agent[4503]: [OK] CFEngine Community cf-execd stopped after 2 seconds
rudder-agent[4512]: [INFO] Using /etc/default/rudder-agent for configuration
rudder-agent[4515]: [INFO] Using /var/rudder/cfengine-community for CFEngine workdir
rudder-agent[4516]: [INFO] Launching CFEngine Community cf-serverd...
rudder-agent[4575]: [OK] CFEngine Community cf-serverd started after 1 seconds
rudder-agent[4577]: [INFO] Launching CFEngine Community cf-execd...
rudder-agent[4610]: [OK] CFEngine Community cf-execd started after 1 seconds
Setting up rudder-server-root (2.4.0~beta3~git201207290129-squeeze0) ...
Installing new version of config file /etc/init.d/rudder-server-root ...

Current status: 0 broken [-1], 0 updates [+0], 395 new [+0].

Could the problem be the order of packages to install ?

Actions
Copy link

Also available in: Atom PDF