Project

General

Profile

Actions

Bug #3040

closed

Package management for RHEL / CentOS / SuSE / RPM systems : Reporting about installation is wrong when a package is not available or met dependencies problem

Added by Nicolas PERRON over 11 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
1
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Using 'Package management for RHEL / CentOS / SuSE / RPM systems' Technique on a SLES 11 SP2 to install some packages returns me wrong reports:
  • If the package to install is not available in the repository of zypper, the report will returns a success
  • If the package to install met some problems with the dependencies, it will not try to install the package but will not return any report which lead to a 'No Answer' state in Rudder webUI.

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #7119: Wrong reporting in rpmPackageInstallation when trying to update a non-existent packageRejectedActions
Actions #1

Updated by François ARMAND over 11 years ago

  • Status changed from New to 8
  • Assignee set to Jonathan CLARKE

Perhaps that bug also exists in other packaging system.

Actions #2

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.3.9 to 2.3.10
Actions #3

Updated by Jonathan CLARKE over 11 years ago

  • Assignee deleted (Jonathan CLARKE)
Actions #4

Updated by Matthieu CERDA about 11 years ago

  • Target version changed from 2.3.10 to 2.3.11
Actions #5

Updated by Jonathan CLARKE about 11 years ago

  • Project changed from Rudder to 24
  • Category deleted (Techniques)
Actions #6

Updated by Matthieu CERDA almost 11 years ago

  • Target version changed from 2.3.11 to 2.3.12
Actions #7

Updated by Jonathan CLARKE almost 11 years ago

Sounds like we're not getting the right return codes from zypper.

Actions #8

Updated by Matthieu CERDA almost 11 years ago

  • Target version changed from 2.3.12 to 2.3.13
Actions #9

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.3.13 to 84
Actions #10

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 84 to 2.4.7
Actions #11

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions #12

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions #13

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.9 to 2.4.10
Actions #14

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.10 to 2.4.11
Actions #15

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.11 to 2.4.12
Actions #16

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.12 to 2.4.13
Actions #17

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.4.13 to 2.6.11

Since Support for 2.4 branch is over, retargeting this issue to 2.6

Actions #18

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions #19

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions #20

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions #21

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions #22

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions #23

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions #24

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions #25

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions #26

Updated by François ARMAND about 9 years ago

  • Subject changed from (ex PT/ Technique) Package management for RHEL / CentOS / SuSE / RPM systems : Reporting about installation is wrong when a package is not available or met dependencies problem to Package management for RHEL / CentOS / SuSE / RPM systems : Reporting about installation is wrong when a package is not available or met dependencies problem
  • Assignee set to Benoît PECCATTE
  • Target version changed from 2.6.20 to 2.10.10

Benoit, I think it's the same problem than other package manager. Can check if it is so, and if it is still the case in 2.10 and new version of the technique.

Actions #27

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions #28

Updated by Benoît PECCATTE about 9 years ago

  • Status changed from 8 to Discussion

On Rudder 2.10 technique 1.0:
- If the package to install is not available in the repository of zypper, there is no report at all

On Rudder 2.10 technique 7.0:
- The report is made properly

Actions #29

Updated by Benoît PECCATTE about 9 years ago

  • Category set to Techniques
Actions #30

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions #31

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 24 to Rudder
  • Category changed from Techniques to Techniques
Actions #32

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions #33

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions #34

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions #35

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions #36

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions #37

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions #38

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions #39

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions #40

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.20 to 2.11.18
Actions #41

Updated by Jonathan CLARKE over 8 years ago

  • Related to Bug #7119: Wrong reporting in rpmPackageInstallation when trying to update a non-existent package added
Actions #42

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #43

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #44

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #45

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #46

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #47

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #48

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions #49

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions #50

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #51

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #52

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #53

Updated by François ARMAND over 7 years ago

  • Status changed from Discussion to Rejected

Im' closing this one has almost anything doable on this technique was done, and the correct solution is to use: http://www.normation.com/en/blog/2016/10/17/discover-new-package-management-implementation-rudder/

Actions

Also available in: Atom PDF