Actions
Bug #13807
closed
Fusion does not parse network gateway correctly
Added by François ARMAND over 5 years ago. Updated 6 months ago.
Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
No
Description
It at least happen when one interface has one ip in ipv4 and one in ipv6.
Updated by François ARMAND over 5 years ago
- Related to Bug #13803: Network, mask and gateway not correctly parsed from inventory added
Updated by François ARMAND over 5 years ago
- Related to Bug #13804: Missing gateway, network in network interface details added
Updated by François ARMAND over 5 years ago
- Related to Bug #13772: Network group criteria not working added
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.17 to 4.1.18
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.18 to 4.1.19
- Priority changed from 52 to 51
Updated by Alexis Mousset about 5 years ago
- Target version changed from 4.1.19 to 4.1.20
- Priority changed from 51 to 50
Updated by François ARMAND about 5 years ago
- Target version changed from 4.1.20 to 4.1.21
- Priority changed from 50 to 49
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 4.1.21 to 4.1.22
- Priority changed from 49 to 48
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 4.1.22 to 4.1.23
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 4.1.23 to 4.1.24
- Priority changed from 48 to 47
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 4.1.24 to 588
- Priority changed from 47 to 46
Updated by Nicolas CHARLES almost 5 years ago
- Target version changed from 588 to 5.0.13
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 46 to 45
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.14 to 5.0.15
- Priority changed from 45 to 44
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.15 to 5.0.16
- Priority changed from 44 to 43
Updated by Alexis Mousset about 4 years ago
- Target version changed from 5.0.16 to 5.0.17
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 5.0.18 to 5.0.19
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0.19 to 5.0.20
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0.20 to 797
Updated by Benoît PECCATTE almost 3 years ago
- Target version changed from 797 to 6.1.14
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.18 to 6.1.19
- Priority changed from 43 to 44
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.1.19 to 6.1.20
- Priority changed from 44 to 45
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.1.20 to 6.1.21
- Priority changed from 45 to 46
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
Updated by François ARMAND 6 months ago
- Status changed from New to Resolved
- Priority changed from 46 to 0
- Regression set to No
This does not seems to be the case anymore, and we now often have a mixe of ipv4/ipv6 IP with the gateway.
Actions