Skip to content

Flatcar fails to boot on AWS m4.* instance types #665

@jepio

Description

@jepio

Description

Flatcar stable 3033.2.0 works, 3033.2.1 doesn't. The symptoms are no DHCP address being acquired on the network interface, so fetching instance metadata fails. Boot log shows more or less this:

[   70.884544] ignition[535]: GET http://169.254.169.254/2009-04-04/user-data: attempt #18
[   70.888100] ignition[535]: GET error: Get "http://169.254.169.254/2009-04-04/user-data": dial tcp 169.254.169.254:80: connect: network is unreachable

Impact

[ 1 sentence detailing the impact this bug is creating for you ]

Environment and steps to reproduce

  1. Set-up: [ describe the environment Flatcar/Lokomotive/Nebraska etc was running in when encountering the bug; Platform etc. ]
  2. Task: [ describe the task performing when encountering the bug ]
  3. Action(s): [ sequence of actions that triggered the bug, see example below ]
    a. [ requested the start of a new pod or container ]
    b. [ container image downloaded ]
  4. Error: [describe the error that was triggered]

Expected behavior

[ describe what you expected to happen at 4. above but instead got an error ]

Additional information

Please add any information here that does not fit the above format.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions