Actions
Bug #11154
closedrudder-init not handling IPv6 subnets
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
-
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
49
Name check:
Fix check:
Regression:
Description
When running rudder-init, it does not accept IPv6 subnets.
Rudder GUI does, and handles is also well (for cf-servd and apache2 subnets).
Please either make rudder-init accept IPv6 subnets or remove the unnecessary step with rudder-init and just do the DB-Initialization with the installation, and keep the subnets open for the GUI / the REST API to be set up.
Updated by Benoît PECCATTE over 6 years ago
- Category set to Packaging
In which version did you test.
We added such support in 4.1
Updated by Benoît PECCATTE over 6 years ago
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Priority changed from 0 to 50
Updated by Janos Mattyasovszky over 6 years ago
Yes, this is quite disturbing for me right now... I have re-tested it, and apparently it accepts my ipv6 subnet now.
Either I have found some edge-case back last week, or I was really testing on an older version.
I would say let's close this issue, and I'll open a new one if I found a bug. :-/
Updated by Alexis Mousset over 6 years ago
- Status changed from New to Rejected
- Priority changed from 50 to 49
Closing as requested.
Actions