Bug #3170
closed
Techniques 'Zypper Package Manager Configuration' and 'RUG / YaST package manager configuration (ZMD)': Broken Reporting when configuration more than one repository which should not be added
Added by Nicolas PERRON over 11 years ago.
Updated about 9 years ago.
Description
When using the Technique Zypper Package Manager Configuration, it seems that the only way to have a successful reporting is to configure no more than one repository and which should not be added into zypper.
Here are the differents behaviour:
- If one repository is set and should be added => All reporting of Rudder will be in an Unkown state
- If one repository is set and should not be added => Success
- If several repositories are set and should be added => reporting about the Directive is in a No Response state and no report appears in the Technical log of the node about this Directive
- If several repositories are set and should not be added => reporting about the Directive is in a No Response state and no report appears in the Technical log of the node about this Directive
Pull Request URL: https://github.com/Normation/rudder-techniques/pull/59 https://github.com/Normation/rudder-techniques/pull/46
Edit: This bug is present in the Technique 'RUG / YaST package manager configuration (ZMD)' too.
Files
- Category set to Techniques
- Assignee set to Nicolas PERRON
- Priority changed from N/A to 1
- Target version set to 2.3.10
Here is an extract from tail -f /var/log/rudder/reports/all.log | grep Repository on the server with two Repositories to set:
2013-01-10T16:04:23+01:00 sles-11-sp1-64 rudder[27535]: R: @@zypperPackageManagerSettings@@result_success@@f6061429-1565-4373-9a6f-e9c253a9cc91@@98874df5-9099-4632-bea5-075154ae4361@@6f6061429-1565-4373-9a6f-e9c253a9cc91@@98874df5-9099-4632-bea5-075154ae4361@@6@@Repository@@Rudder Project@@2013-01-10 16:04:17+01:00##59e66fe7-7f0e-497d-8055-a103116b4a08@#The Zypper source Rudder Project was already here. Skipping...
2013-01-10T16:04:23+01:00 sles-11-sp1-64 rudder[27535]: R: @@zypperPackageManagerSettings@@result_success@@f6061429-1565-4373-9a6f-e9c253a9cc91@@98874df5-9099-4632-bea5-075154ae4361@@6f6061429-1565-4373-9a6f-e9c253a9cc91@@98874df5-9099-4632-bea5-075154ae4361@@6@@Repository@@Rudder Project Unstable@@2013-01-10 16:04:17+01:00##59e66fe7-7f0e-497d-8055-a103116b4a08@#The Zypper source Rudder Project Unstable was already here. Skipping...
The bug seems to come from a misuse of a the Technique TrackingKey. Here is a fix for branch 2.3
- Description updated (diff)
- Status changed from New to Pending technical review
- % Done changed from 0 to 100
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
Jon, could you review this pull request, please ?
- Status changed from Pending technical review to Discussion
I suppose the pull request can be cancelled.
The reporting can't work since the Tracking Key used is based on a multivalued component which can be null:
- If the tracking key is null, Rudder will not be aware of relations between Directives and reports received.
- There is no any chance to have reports on the none multivalued components
The solution is to split this Technique into two:
- One Technique which will do the job for adding repositories
- Another Technique which will set general settings for zypper (install recommends)
I wonder: shouldn't we rename the Technique if the goals are altered ?
- Zypper package manager configuration rename into Zypper repositories management
- Add Zypper settings management
Jon, what do you think about ?
Nicolas PERRON wrote:
I suppose the pull request can be cancelled.
No need for that, just update it.
The reporting can't work since the Tracking Key used is based on a multivalued component which can be null:
- If the tracking key is null, Rudder will not be aware of relations between Directives and reports received.
- There is no any chance to have reports on the none multivalued components
The solution is to split this Technique into two:
- One Technique which will do the job for adding repositories
- Another Technique which will set general settings for zypper (install recommends)
I wonder: shouldn't we rename the Technique if the goals are altered ?
- Zypper package manager configuration rename into Zypper repositories management
Yep, sounds good.
- Add Zypper settings management
I'd prefer "Zypper package manager settings".
- Target version changed from 2.3.10 to 2.3.11
- Subject changed from Technique Zypper Package Manager Configuration: Broken Reporting when configuration more than one repository which should not be added to Techniques 'Zypper Package Manager Configuration' and 'RUG / YaST package manager configuration (ZMD)': Broken Reporting when configuration more than one repository which should not be added
- Description updated (diff)
- Status changed from Discussion to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
Updated the title of the ticket. This bug appears not only on 'Zypper Package Manager Configuration' but with 'RUG / YaST package manager configuration (ZMD) too.
Pull Request URL updated: https://github.com/Normation/rudder-techniques/pull/59
Nicolas, could you review it please ?
- Description updated (diff)
Pull Request URL updated on description.
- Status changed from Pending technical review to Pending release
Applied in changeset commit:f7cb8c5f1357e9d064d93ae85e914e4c83177532.
Applied in changeset commit:3025177c70f40490de20b0938e4eb456e2d5db0e.
Applied in changeset commit:98701b512e2dd63ca982dc6d0851a031277e0bc5.
Applied in changeset commit:ba2d070f49fd3a720679c23e2040c67993c3600b.
Applied in changeset commit:f6eed4b11b64fdcda160cc066c8b2ab20c783986.
- Status changed from Pending release to Released
- Project changed from 24 to Rudder
- Category changed from Techniques to Techniques
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by 
Updated by Matthieu CERDA 
Updated by 
Updated by