Bug #3035
closed
Service Pack is not recognized in the inventory of a SLES 11 SP2 node
Added by Nicolas PERRON almost 12 years ago.
Updated almost 12 years ago.
Category:
Web - Nodes & inventories
Description
Using Rudder Server 2.4.0~rc1 on a SLES 11 SP1 machine, an inventory of a SLES 11 SP2 node in the WebUI doesn't have any information about Service Pack.
The output is "Service Pack: unknown" or "Service Pack: undefined".
I suppose this is related to Fusion Inventory ?
Pull request here : https://github.com/Normation/rudder-packages/pull/1
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Vincent is working on this.
A quick look at the code of FusionInventory agent 2.2.x shows that the Service Pack on SuSE is not detected if the "lsb_release" command is available. A simple workaround is therefore to remove the lsb_release tool.
The real fix will be to restablish Service Pack detection on SuSE even when lsb_release is installed.
There may also be an issue here with Rudder detecting the operating system name if it "SUSE LINUX" (returned by lsb_release) and not "SuSE" (no lsb_release).
The content of the <OPERATINGSYSTEM> tag in the generated inventory is:
<OPERATINGSYSTEM>
<FULL_NAME>SUSE Linux Enterprise Server 11 (x86_64)</FULL_NAME>
<KERNEL_NAME>linux</KERNEL_NAME>
<KERNEL_VERSION>3.0.13-0.27-default</KERNEL_VERSION>
<NAME>SUSE LINUX</NAME>
<VERSION>11</VERSION>
</OPERATINGSYSTEM>
Solution:
- create a patch for our Fusion version to take care of that, and package that in our distribution
- long term: made Fusion correctly take care of the SP version.
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:e16acee9ce0a679a7ecf98bbd77099012b306cf5.
- Description updated (diff)
Don't take care about the first commit in history, it had been made on a separated branch (bug_3035/...)
I made a mistake on my local repository when push it (forgot to change remote ...)
you should rather look here for the technical review: https://github.com/Normation/rudder-packages/pull/1
- Assignee changed from Vincent MEMBRÉ to Jonathan CLARKE
Jon, I believe you are the only one that can do the technical review for that one.
- Status changed from Pending technical review to Discussion
- Assignee changed from Jonathan CLARKE to Vincent MEMBRÉ
I will review the pull request ASAP. However:
Jonathan CLARKE wrote:
There may also be an issue here with Rudder detecting the operating system name if it "SUSE LINUX" (returned by lsb_release) and not "SuSE" (no lsb_release).
This point still needs adressing - Vincent please look into it and check we don't have a double problem here, and update this ticket with your progress.
- Status changed from Discussion to Pending technical review
Applied in changeset commit:e82cfda6ece5e93bafa60fe083bac50883e9d5c7.
- Status changed from Pending technical review to Discussion
Jonathan CLARKE wrote:
Applied in changeset commit:e82cfda6ece5e93bafa60fe083bac50883e9d5c7.
This looks good to me, I have merged it on rudder-packages in 2.4 branch.
This ticket can be closed as soon as the code has been checked for the "SUSE LINUX" value discussed above.
Argh, i thought i updated thé issue about ait, but clearly i forgot.
In ldap-inventory web check that OSNAME contains 'suse',
so it works for both 'suse' and 'suse Linux !
And i confirm as i have tested of both cases
- Status changed from Discussion to Released
Vincent MEMBRÉ wrote:
Argh, i thought i updated thé issue about ait, but clearly i forgot.
In ldap-inventory web check that OSNAME contains 'suse',
so it works for both 'suse' and 'suse Linux !
And i confirm as i have tested of both cases
OK, thanks for confirming.
- Status changed from Released to Pending release
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by 
Updated by