Project

General

Profile

Actions

Bug #8175

closed

Transitory error message when upgrading to 3.1 to 3.2 in rudder agent run

Added by Nicolas CHARLES almost 8 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
4
Assignee:
-
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I upgraded Rudder server from 3.1 to 3.2
right after, I ran rudder agent run, and got following error message:

success  server-roles              Check WebDAV credentials                     The Rudder WebDAV user and password are OK
Formal =  {'message','old_class_prefix'}, Actual =  {'Check if the service httpd is started using ps','service_check_running_httpd','','@{args}'}
   error: While constructing scope '_logger_default'
   error: Fatal CFEngine error: Augment scope, formal and actual parameter mismatch is fatal

error    Rudder agent was interrupted during execution by a fatal error
         Run with -i to see log messages.
(this is the output with -i)
It self corrected as soon as failsafe kicked in.
This is because we changed the signature in ncf, but it take a while for ncf to go from /usr/share/ncf to /var/rudder/ncf/common


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #9416: Transient error during upgrade from 3.1 to 4.0RejectedActions
Actions #1

Updated by Jonathan CLARKE almost 8 years ago

Happens on CentOS

Actions #2

Updated by Jonathan CLARKE almost 8 years ago

  • Priority changed from N/A to 4

Jonathan CLARKE wrote:

Happens on CentOS

This is likely due to the fact that yum doesn't respect package order during upgrade. We upgrade /var/rudder* from /usr/share/ncf in the postinst script from rudder-webapp (which depends on ncf), but if rudder-webapp is upgraded before ncf, this can happen, when "rudder agent run" is run manually.

Running "rudder agent update && rudder agent run" should work though.

Actions #3

Updated by Jonathan CLARKE almost 8 years ago

  • Status changed from New to Rejected

As explained above, this is a transitory situation that only occured because the agent was run manually. We do not think it makes sense to change the "rudder agent run" command to auto-update, so rejecting this.

Actions #4

Updated by Nicolas CHARLES over 7 years ago

  • Related to Bug #9416: Transient error during upgrade from 3.1 to 4.0 added
Actions

Also available in: Atom PDF