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 almost 12 years ago.
Updated about 9 years ago.
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 ?
It could be that there is a conflict between rudder-server-root and rudder-agent.
If I try to install rudder-agent 2.4 on a Rudder server 2.3 an error about the owner of the configuration file /opt/rudder/etc/uuid.hive :
root@squeezedev:~# aptitude install rudder-agent
The following NEW packages will be installed:
rudder-agent{b} uuid-runtime{a}
0 packages upgraded, 2 newly installed, 0 to remove and 10 not upgraded.
Need to get 21.9 MB of archives. After unpacking 95.1 MB will be used.
The following packages have unmet dependencies:
rudder-agent: Conflicts: rudder-cfengine-community but 2.3.8-squeeze0 is installed and it is kept back.
The following actions will resolve these dependencies:
Remove the following packages:
1) rudder-cfengine-community
Accept this solution? [Y/n/q/?] y
The following NEW packages will be installed:
rudder-agent uuid-runtime{a}
The following packages will be REMOVED:
rudder-cfengine-community{a}
[...]
dpkg: rudder-cfengine-community: dependency problems, but removing anyway as you requested:
rudder-server-root depends on rudder-cfengine-community.
[...]
Unpacking rudder-agent (from .../rudder-agent_2.4.0~beta3~git201207300935-squeeze0_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/rudder-agent_2.4.0~beta3~git201207300935-squeeze0_amd64.deb (--unpack):
trying to overwrite '/opt/rudder/etc/uuid.hive', which is also in package rudder-server-root 2.3.8-squeeze0
configured to not write apport reports
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/rudder-agent_2.4.0~beta3~git201207300935-squeeze0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
[...]
It could be related to this issue, because:
- rudder-agent should be installed before rudder-server-root in 2.4 branch
- rudder-server-root must be migrated before in order to allow rudder-agent to be installed (if not the conflict about the config file uuid.hive will appears like above)
Nicolas PERRON wrote:
It could be that there is a conflict between rudder-server-root and rudder-agent.
If I try to install rudder-agent 2.4 on a Rudder server 2.3 an error about the owner of the configuration file /opt/rudder/etc/uuid.hive :
[...]
It could be related to this issue, because:
- rudder-agent should be installed before rudder-server-root in 2.4 branch
- rudder-server-root must be migrated before in order to allow rudder-agent to be installed (if not the conflict about the config file uuid.hive will appears like above)
It could be due to an instruction missing in the control file like Replaces and/or Breaks about rudder-server-root in the rudder-agent-control (cf http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces).
- Status changed from New to In progress
It seems that these instuctions don't work:
Replaces: rudder-server-root (<< 2.4.0~beta2)
Breaks: rudder-server-root (<< 2.4.0~beta2)
I have to revert my commit
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Nicolas PERRON wrote:
It seems that these instuctions don't work:
[...]
I have to revert my commit
The only error was because of the missing of comma. This is fixed, now
Looks good to me ! Thanks NPE :D
- Status changed from Pending technical review to Released
I'm not convinced that this adresses the problem originally described, but there is not enough information to do anything about that. The fix is valid, and necessary, so I'm validating this one.
Jonathan CLARKE wrote:
I'm not convinced that this adresses the problem originally described, but there is not enough information to do anything about that. The fix is valid, and necessary, so I'm validating this one.
If I remember, the problem was that rudder-agent wasn't installed (and didn't replace rudder-cfengine-community) before upgrading rudder-server-root, which failed because of missing dependencies.
- Project changed from Rudder to 34
- Category deleted (
11)
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by Matthieu CERDA 
Updated by 
Updated by