Actions
Bug #33929
closed
Provide a meaningful report when a subnet has an invalid address
Difficulty:
trivial
Triaged:
Yes
Description
We recently added a better subnet address validation, but there was no migration to ensure all addresses are correct and it would need to be interactive perhaps which is a no go. This at least improves the exception a bit.
Updated by The Foreman Bot about 3 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8925 added
Updated by Lukas Zapletal about 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|29cc1a76f50b365ba6068e5797a1af758dda99f1.
Updated by The Foreman Bot almost 3 years ago
- Pull request https://github.com/theforeman/foreman/pull/8977 added
Updated by Evgeni Golov almost 3 years ago
- Fixed in Releases 3.1.0 added
- Fixed in Releases deleted (
3.1.1, 3.2.0)
Updated by Amit Upadhye almost 3 years ago
- Subject changed from Report nicely when subnet has invalid address to Provide a meaningful report when a subnet has invalid address
Updated by Ewoud Kohl van Wijngaarden almost 3 years ago
- Subject changed from Provide a meaningful report when a subnet has invalid address to Provide a meaningful report when a subnet has and invalid address
Updated by Ewoud Kohl van Wijngaarden almost 3 years ago
- Subject changed from Provide a meaningful report when a subnet has and invalid address to Provide a meaningful report when a subnet has an invalid address
Updated by Ondřej Ezr almost 3 years ago
- Fixed in Releases 3.1.1, 3.2.0 added
- Fixed in Releases deleted (
3.1.0)
Updated by Ondřej Ezr almost 3 years ago
- Fixed in Releases 3.1.0 added
- Fixed in Releases deleted (
3.1.1, 3.2.0)
Actions