[BGPCEP-162] BGP fails when hostname cannot be resolved to IPv4 address. Created: 06/Nov/14  Updated: 03/Mar/19  Resolved: 24/Apr/15

Status: Resolved
Project: bgpcep
Component/s: BGP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 2336

 Description   

This is a minor issue, so no logs until requested.

Every sane Linux installation should have a hostname resolvable to at least 127.0.0.1,
but it is possible that BGP does not really need that, and fails just because of an oversight.

If there a good reason to fail, it should be stated (for example) in User Manual. Wiki page may not be enough, as this issue is likely to happen just when the host loses DNS connectivity.

 Comments   
Comment by Robert Varga [ 26/Feb/15 ]

I think this actually is a Java requirement, so not a BGP bug. Can you provide whatever errors are reported so we can be sure and/or have a plan of action?

Comment by Vratko Polak [ 24/Apr/15 ]

Tested on recent Helium and Lithium builds, and this bug is not present; at least when hostname is changed only after Linux booted up with resolvable one .
Not sure whether it was incorrect first report, or some third-party dependency version upgrade has fixed the issue in meantime.
Either way, closing as WORKSFORME.

Generated at Wed Feb 07 19:12:13 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.