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

BottleRocket configures setttings.network.hostname incorrectly when using resource based names #3011

Closed
tzneal opened this issue Apr 13, 2023 · 1 comment
Labels
status/needs-triage Pending triage or re-evaluation type/bug Something isn't working

Comments

@tzneal
Copy link
Contributor

tzneal commented Apr 13, 2023

Platform I'm building on:

A VPC with subnets configured for resource based names.

What I expected to happen:

[root@admin]# apiclient  get settings.network.hostname
{
  "settings": {
    "network": {
      "hostname": "i-1234567890abcdef0.compute.internal"
    }
  }
}

What actually happened:

[root@admin]# apiclient  get settings.network.hostname
{
  "settings": {
    "network": {
      "hostname": "ip-192-168-131-0.us-west-2.compute.internal"
    }
  }
}

How to reproduce the problem:

  1. Configure a subnet with resource based naming
  2. Launch a BottleRocket instance into this subnet
@stmcginnis
Copy link
Contributor

Resolved by #3021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/needs-triage Pending triage or re-evaluation type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants