Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hostname could have more than 64 characters #10650

Closed
2 of 13 tasks
kezhuw opened this issue Sep 19, 2024 · 2 comments
Closed
2 of 13 tasks

hostname could have more than 64 characters #10650

kezhuw opened this issue Sep 19, 2024 · 2 comments

Comments

@kezhuw
Copy link

kezhuw commented Sep 19, 2024

Description

hostname gives fv-az1272-448.grsihaubamwerhiryzjrxtypna.phxx.internal.cloudapp.net which is longer than 64 characters. Some tools, say OpenSSL, refuses these hostnames.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

https://github.com/kezhuw/zookeeper/actions/runs/10831378697/job/30053388552

The first job step runs hostname -f.

Is it regression?

Not sure.

Expected behavior

Hostnames must be less than 63 characters in length per Section 2.3.4 of the Domain Names Specification RFC.

https://docs.github.com/en/enterprise-server@3.10/admin/configuring-settings/configuring-network-settings/configuring-the-hostname-for-your-instance

Actual behavior

hostname gives fv-az1272-448.grsihaubamwerhiryzjrxtypna.phxx.internal.cloudapp.net which is longer than 64 characters.

Repro steps

Adds a job step to output hostname.

@kishorekumar-anchala
Copy link
Contributor

Hi @kezhuw ,

Thank you for bringing this issue to us. We are looking into this issue and will update you on this issue after investigating.

@vidyasagarnimmagaddi
Copy link
Contributor

Hi @kezhuw , We have anlayzed the issue by forking your repo. The build appears to be successful. hence closing the issue. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants