Bug #1884

The addupdate target on the package installation PT is broken. We should enable it again when possible

Added by Matthieu CERDA about 3 years ago. Updated 2 days ago.

Status:Qualified Start date:2011-09-30
Priority:4 Due date:
Assignee:Nicolas CHARLES % Done:

0%

Category:Policy Templates
Target version:Rudder - 2.10.9
Pull Request:

Description

The addupdate target on the package installation PT is broken. We should enable it again when possible

History

#2 Updated by Jonathan CLARKE about 3 years ago

  • Target version set to Ideas (2.4 specific)

#3 Updated by François ARMAND about 3 years ago

  • Target version changed from Ideas (2.4 specific) to 2.4.0~alpha1

#4 Updated by Jonathan CLARKE about 3 years ago

  • Target version changed from 2.4.0~alpha1 to 2.4.0~alpha2

#5 Updated by Jonathan CLARKE almost 3 years ago

  • Target version changed from 2.4.0~alpha2 to 2.4.0~alpha3

#6 Updated by Matthieu CERDA almost 3 years ago

  • Status changed from New to Discussion
  • Needs translating set to No

This still seems broken in CFengine, no class gets raised when the package is already installed and up to date.

rudder> Checking if package (nano,*,*) is at the desired state (installed=1,matched=1)
rudder>  -> Package promises to refer to itself as "nano" to the manager
rudder>  -> Package version seems to match criteria
rudder> Checking if latest available version is newer than installed...
rudder> Looking for an installed package older than (nano,*,*)
rudder> Found installed package (nano,2.2.4-1,default)
rudder> Installed package is up to date, not updating

For reference, here is the add flavor output :

rudder> Checking if package (nano,*,*) is at the desired state (installed=1,matched=1)
rudder>  -> Package promises to refer to itself as "nano" to the manager
rudder>  -> Package version seems to match criteria
rudder>  -> Package "nano" already installed, so we never add it again
rudder>  ?> defining promise result class debian_install_kept_nano

#7 Updated by Jonathan CLARKE almost 3 years ago

  • Target version changed from 2.4.0~alpha3 to 2.4.0~alpha4

#8 Updated by François ARMAND almost 3 years ago

  • Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5

#9 Updated by Jonathan CLARKE almost 3 years ago

  • Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6

#10 Updated by Jonathan CLARKE over 2 years ago

  • Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7

#11 Updated by Jonathan CLARKE over 2 years ago

  • Target version changed from 2.4.0~alpha7 to 2.3.8

#12 Updated by Jonathan CLARKE over 2 years ago

  • Target version changed from 2.3.8 to Ideas (2.5 specific)

#13 Updated by Jonathan CLARKE over 2 years ago

  • Target version changed from Ideas (2.5 specific) to Ideas (not version specific)

#14 Updated by Nicolas CHARLES 16 days ago

  • Status changed from Discussion to Qualified
  • Assignee set to Nicolas CHARLES
  • Target version changed from Ideas (not version specific) to 2.10.8

i hope it's been fixed in CFEngine

#15 Updated by Nicolas CHARLES 16 days ago

Ok, this is actually like the standart update: we cannot simply latest to have latest version
We have a nice solution on RPM, so i'll be using it on RPM
It has not yet been implemented on DEB however

#16 Updated by Nicolas CHARLES 12 days ago

hum, i've been a bit optimisstic
addupdate still doesn't work as expected... i get always repaired state, or no reports

trying to tinker with it, forcing target version when available, or considering it as an update all fails

#17 Updated by Vincent MEMBRÉ 10 days ago

  • Target version changed from 2.10.8 to 2.10.9

#18 Updated by Jonathan CLARKE 3 days ago

The link to the old bugtracker has been updated: http://auth.cfengine.com/bugtracker/view.php?id=532

It seems we need to define a specific classes body with return code outcomes for this to work. Could you test again?

#19 Updated by Nicolas CHARLES 3 days ago

addupdate is more broken than that: it simply does not install if you specify a target version and package was not there, it does not update if it is installed

#20 Updated by Nicolas CHARLES 2 days ago

but we could "simply" convert the addupdate to "install" and then "update", and aggregate the reports from both

Also available in: Atom PDF