Project

General

Profile

Actions

Bug #25421

closed

Unattended flow does not allow mapped IPv4 addresses

Added by Arend Lapere over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Unattended installations
Target version:
-
Difficulty:
trivial
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Because our end-system does not allow the use of tokens (because it can't process the "?" in the URL) we had to disable token based unattended installs altogether.
However, in our system we run in a dual stack environment. What appears to be happening, is that the REMOTE_ADDR is an IPv6 mapped to an IPv4 address; however, foremand does not seem to take into account these types of addresses and thys no host is found.

The fix will only parse these mapped or translated IPv6 addresses back to IPv4 addresses.

Actions #1

Updated by Arend Lapere over 5 years ago

  • Category set to Unattended installations
  • Assignee set to Arend Lapere
Actions #2

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6222 added
Actions #3

Updated by Arend Lapere over 5 years ago

  • Subject changed from Unattended flow without token does not accept mapped or translated IPv4 addresses to IPv6 to Unattended flow does not allow mapped IPv4 addresses
Actions #4

Updated by Lukas Zapletal over 5 years ago

  • Fixed in Releases 1.21.0 added
Actions #5

Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF