Bug #1884

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

Added by Matthieu CERDA almost 4 years ago. Updated 23 days ago.

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

0%

Category:Techniques
Target version:2.10.17
Pull Request: How to reproduce:

Reproduced: Found in version(s):

Description

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


Related issues

Related to Rudder - User story #4298: Install / upgrade packages New 2013-12-30
Duplicated by Rudder - Bug #6957: You can't do install+update in one shot in the install pa... Rejected 2015-07-10

History

#2 Updated by Jonathan CLARKE almost 4 years ago

  • Target version set to 18

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

  • Target version changed from 18 to 2.4.0~alpha1

#4 Updated by Jonathan CLARKE almost 4 years ago

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

#5 Updated by Jonathan CLARKE over 3 years ago

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

#6 Updated by Matthieu CERDA over 3 years ago

  • Status changed from New to Discussion

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 over 3 years ago

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

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

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

#9 Updated by Jonathan CLARKE over 3 years ago

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

#10 Updated by Jonathan CLARKE over 3 years ago

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

#11 Updated by Jonathan CLARKE over 3 years ago

  • Target version changed from 2.4.0~alpha7 to 2.3.8

#12 Updated by Jonathan CLARKE about 3 years ago

  • Target version changed from 2.3.8 to 24

#13 Updated by Jonathan CLARKE about 3 years ago

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

#14 Updated by Nicolas CHARLES 9 months ago

  • Status changed from Discussion to 8
  • 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 9 months 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 9 months 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É 9 months ago

  • Target version changed from 2.10.8 to 2.10.9

#18 Updated by Jonathan CLARKE 9 months 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 9 months 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 9 months ago

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

#21 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 2.10.9 to 2.10.10

#22 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 2.10.10 to 2.10.11

#23 Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 2.10.11 to 2.10.12

#24 Updated by Benoît PECCATTE 6 months ago

  • Project changed from Techniques to Rudder
  • Category changed from Policy Templates to Techniques

#25 Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 2.10.12 to 2.10.13

#26 Updated by Benoît PECCATTE 5 months ago

  • Status changed from 8 to New

#27 Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 2.10.13 to 2.10.14

#28 Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 2.10.14 to 2.10.15

#29 Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 2.10.15 to 2.10.16

#30 Updated by Vincent MEMBRÉ 23 days ago

  • Target version changed from 2.10.16 to 2.10.17

#31 Updated by Jonathan CLARKE 23 days ago

  • Subject changed from The addupdate target on the package installation PT is broken. We should enable it again when possible to The addupdate target on the package installation Technique is broken. We should enable it again when possible

#32 Updated by Jonathan CLARKE 23 days ago

  • Duplicated by Bug #6957: You can't do install+update in one shot in the install package technique added

#33 Updated by Jonathan CLARKE 23 days ago

Also available in: Atom PDF