Project

General

Profile

Bug #9410

Finish script should try connect to hostname when IP address is empty

Added by Lukas Zapletal about 4 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
Low
Category:
Orchestration
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

In non-DHCP deployments finish script ssh connection only tries to connect to provisioning IP, but when empty, it could also try to connect to a hostname, if set for the provisioning interface.


Related issues

Related to Foreman - Feature #18765: Use hostname instead IP address for finish scriptClosed2017-03-02

History

#1 Updated by The Foreman Bot about 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2171 added
  • Pull request deleted ()

#2 Updated by Marek Hulán about 4 years ago

What is the use case for this? If we don't know the IP before the host is provisioned and there's no DHCP, then the IP must be hardcoded in the image right? So we know the IP... If there's some valid use case to use DNS for obtaining the IP, then I think it should set the IP of host when the domain is selected (similar to what we do for subnet) rather than trying to auto-guess during connecting. That would be more safe, user could review what IP he or she is trying to run finish script on.

#3 Updated by Lukas Zapletal about 4 years ago

  • Status changed from Ready For Testing to Rejected
  • Priority changed from Normal to Low

There was a request on the list for support of manually assigned DNS hostnames. The use case is IMHO incorrect configuration/deployment. I agree this is not clean. Closing.

#4 Updated by Dominic Cleal about 2 years ago

  • Related to Feature #18765: Use hostname instead IP address for finish script added

Also available in: Atom PDF