[JIRA] [ec2-plugin] (JENKINS-34533) Do not call getPublicDnsName

2 views
Skip to first unread message

shields@kkvesper.jp (JIRA)

unread,
May 2, 2016, 10:37:03 AM5/2/16
to jenkinsc...@googlegroups.com
Johnny Shields created an issue
 
Jenkins / Bug JENKINS-34533
Do not call getPublicDnsName
Issue Type: Bug Bug
Assignee: Francis Upton
Components: ec2-plugin
Created: 2016/May/02 2:36 PM
Priority: Minor Minor
Reporter: Johnny Shields

in ec2-plugin/src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java

on line 372 in function `getEC2HostAddress()`

there is a line:

```
String host = inst.getPublicDnsName();
```

This assumes that DNS Hostnames are enabled for the VPC which the slave instance is in, however, by default DNS is not enabled. This causes an error when attempting to relaunch slave instances in VPC, but *NOT* when launching new instances.

The best fix would be to remove ALL usage of Public DNS and instead only use public IP or private DNS, both which are guaranteed to exist (I think).

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

ian.bamforth@tracsis.com (JIRA)

unread,
Aug 19, 2016, 5:09:01 AM8/19/16
to jenkinsc...@googlegroups.com
Ian Bamforth commented on Bug JENKINS-34533
 
Re: Do not call getPublicDnsName

This problem has bitten me too. The setting for this is clearly labelled "Connect using Public IP", but that is not what the code does - it tries to use the public dns. In a vpc, the public dns resolves to a private ip address.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

fabrizio.manfredi@gmail.com (JIRA)

unread,
Aug 11, 2019, 7:11:02 AM8/11/19
to jenkinsc...@googlegroups.com
FABRIZIO MANFREDI closed an issue as Fixed
Change By: FABRIZIO MANFREDI
Status: Open Closed
Resolution: Fixed
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages