Bug #30706
Creating compute resources on IPV6 network does not fail gracefully
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1858855
Description of problem:
I know that one of the requirements is that IPv6 doesn't support compute resources, but when you try to create one, it doesn't fail gracefully.
Version-Release number of selected component (if applicable):
6.8.0_snap 9
How reproducible:
100%
Steps to Reproduce:
1. Have all ipv6 connection setup.
2. Create proxy on firefox to access UI
3. Login on UI, Infrastructure -> Compute Resources
4. Select EC2 from dropdown menu and fill in all necessary info
5. Click submit.
Actual results:
Oops, we're sorry but something went wrong Network is unreachable - connect(2) for <ip> (Errno::ENETUNREACH)
Expected results:
At least stay on satellite with a better error message.
Additional info:
Any compute resources provider fails the same way. Is there a way we make this error handle better on the UI?
Associated revisions
History
#1
Updated by Lukas Zapletal 8 months ago
What else is Foreman supposed to print out? Foreman can't reach the destination. We throw the very same message at about 50+ other places.
#2
Updated by The Foreman Bot 8 months ago
- Assignee set to Tomer Brisker
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7952 added
#3
Updated by The Foreman Bot 8 months ago
- Fixed in Releases 2.3.0 added
#4
Updated by Tomer Brisker 8 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|c6361ee8aeb287cd2ab2694885b57684d7dc2846.
#5
Updated by The Foreman Bot 8 months ago
- Pull request https://github.com/theforeman/foreman/pull/7940 added
#6
Updated by The Foreman Bot 7 months ago
- Pull request https://github.com/theforeman/foreman/pull/7975 added
Fixes #30706 - Gracefully recover from CR connection error
If the connection fails to the compute resource due to networking
issues we should capture it nicely rather than causing a 500 page.