Bug #7136
closed
Rudder doesn't store and display the IPV6 of the nodes
Added by Nicolas CHARLES about 9 years ago.
Updated almost 8 years ago.
Category:
Web - Nodes & inventories
Description
Even if the inventory gets the IPV6 of a node, this part is never parsed by the web interface; and so never displayed to the user
Nicolas CHARLES wrote:
Even if the inventory gets the IPV6 of a node, this part is never parsed by the web interface; and so never displayed to the user
It will be useful to have this information in node details over the API
- Target version changed from 2.10.17 to 2.10.18
- Target version changed from 2.10.18 to 2.10.19
- Target version changed from 2.10.19 to 2.10.20
- Target version changed from 2.10.20 to 277
- Target version changed from 277 to 2.11.18
- Assignee set to Vincent MEMBRÉ
Vincent, could you have a look at this one ? Fusion Inventory does send the ip, we simply ignore it
- Translation missing: en.field_tag_list set to Quick and important
- Target version changed from 2.11.18 to 2.11.19
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/ldap-inventory/pull/81
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Has duplicate Bug #8038: Rudder is not IPv6-Capable added
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Jonathan CLARKE 
Updated by 
Updated by