Skip to content

Fix missing metadata routes for Vultr#1125

Merged
TheRealFalcon merged 1 commit into
canonical:mainfrom
eb3095:vultr-nightly
Dec 1, 2021
Merged

Fix missing metadata routes for Vultr#1125
TheRealFalcon merged 1 commit into
canonical:mainfrom
eb3095:vultr-nightly

Conversation

@eb3095
Copy link
Copy Markdown
Contributor

@eb3095 eb3095 commented Nov 30, 2021

Proposed Commit Message

Fix missing metadata routes for Vultr

Vultr uses 169.254.169.254 for the metadata server. Some distros are having trouble with this on IPv6 only servers because the route is not being assigned to the link-local interface by default as it is in other distros. This change sets that route before attempting to fetch the metadata avoiding the current issue.

Test Steps

Deploy Arch as IPv6 Only on Vultr.

Checklist:

  • [ X ] My code follows the process laid out in the documentation
  • [ X ] I have updated or added any unit tests accordingly
  • [ X ] I have updated or added any documentation accordingly

@eb3095 eb3095 force-pushed the vultr-nightly branch 2 times, most recently from 4ef714e to 1ecbe93 Compare December 1, 2021 03:02
Copy link
Copy Markdown
Contributor

@TheRealFalcon TheRealFalcon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@TheRealFalcon TheRealFalcon merged commit a1cf55e into canonical:main Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants