Bug #4227
closed
A Xen Hypervisor on SLES does not make a valid inventory and can't be accepted into Rudder since binary path to xenstore is wrong on SLES 11 and does not exist on SLES 10
Added by Nicolas PERRON over 11 years ago.
Updated over 9 years ago.
Category:
System techniques
Description
On SLES, if Xen is installed, during the inventory creation, the VM will be checked by the command xenstore. Nevertheless, the path is wrong and the inventory will not be valid and will never be accepted in Rudder.
I suppose that we have here two problems:
- To retrieve information about the VMs on SLES 11 we should use /usr/bin/xenstore instead of /bin/xenstore and on SLES 10 by the use of /usr/sbin/xm list (not really equivalent)
- No be able to retrieve information should not prevent from completing the inventory otherwise it causes machines to never be accepted
I've tried on Rudder agent 2.6.9 but it could be the same on 2.4.12.
- Description updated (diff)
The bug has the same symptom as #3138 but for SLES instead of CentOS
Erratum: On SLES 10 SP3, the package xen-tools-3.2.3_17040_16-0.4.9 contains the same binary: /usr/bin/xenstore-read
Another rectification:
It depends of the tools used.
- On guest (domU), the package xen-tools-domU is installed with the binary /bin/xenstore-read
- On Host (dom0), the package xen-tools is installed with the binary /usr/bin/xenstore-read
- Project changed from 24 to Rudder
- Category set to System techniques
- Status changed from New to In progress
- Assignee set to Jonathan CLARKE
- Priority changed from N/A to 3
This is an easy fix, just a separate classes case for SLES_10 and/or SuSE. I'm on it.
Nicolas, if you know the fix, it would be so much quicker for you just to provide a pull request.
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/257
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:746e6b09d5751a8bdae67686727ae48eefc8424b.
Applied in changeset policy-templates:commit:358c2250e9f03df10469e6171aba5ff651ad250b.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.10 which was released today.
Check out:
- Target version changed from 2.6.10 to 2.4.12
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by Jonathan CLARKE 
Updated by 
Updated by 
Updated by