Bug 249237 - EC2 AMIs do not have dual-dhclient anymore?
Summary: EC2 AMIs do not have dual-dhclient anymore?
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-10 15:00 UTC by Val Packett
Modified: 2020-09-13 19:14 UTC (History)
2 users (show)

See Also:

Attachments
console screenshot from aws (84.13 KB, image/jpeg)
2020-09-10 15:00 UTC, Val Packett 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Val Packett 2020-09-10 15:00:47 UTC 
Created attachment 217872 [details]
console screenshot from aws

I've tried launching the two latest snapshots:

main (20200903 c122cf32f2a) - eu-west-1 region: ami-052c5e4b4db76c3fb
head (20200806 r363935) - eu-west-1 region: ami-05346685445cd7c63

on c5a instances and they're not reachable over the network.
A console screenshot suggests that dual-dhclient did not launch. :( See bugzilla attachments
Comment 1 Val Packett 2020-09-10 15:05:15 UTC 
This works:

head (20200806 r363935) - eu-west-1 region: ami-05346685445cd7c63

haven't checked the two in between
Comment 2 Colin Percival freebsd_committer freebsd_triage 2020-09-12 00:56:46 UTC 
Yeah, something broke.  I'm looking into it.
Comment 3 Colin Percival freebsd_committer freebsd_triage 2020-09-13 19:14:28 UTC 
Looks like the latest builds from HEAD are running out of disk space, due to an increase in the size of debug symbols.  I've bumped the AMIs up to 5GB which looks like it fixes the problem.