Project

General

Profile

Actions

Bug #6459

closed

AWS EC2 Instance should skip interface config in setup wizard

Added by Danny Schuh over 5 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Category:
Interfaces
Target version:
Start date:
06/06/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

AWS EC2 instances should default to DHCP. EC2 instances are assigned IP addresses via DHCP. If you want to give the instance a static address, you will still need to configure the ENI in EC2. No need to configure this twice unless you are running the DHCPd services.

Actions #1

Updated by Chris Buechler over 5 years ago

  • Subject changed from AWS EC2 Instance interfaces should default to DHCP to AWS EC2 Instance should skip interface config in setup wizard
  • Status changed from New to Confirmed
  • Target version changed from 2.3.1-p2 to 2.3.2
  • Affected Version changed from 2.3.1 to All

I presume updated subject is what you're referring to, as it does default to DHCP. It ought to not prompt users in the setup wizard to avoid confusing them.

Actions #2

Updated by Danny Schuh over 5 years ago

Actually, I had skipped the initial setup wizard. I'm looking to eventually deploy this AMI w/o user interaction.

Actions #3

Updated by Chris Buechler over 5 years ago

Danny Schuh wrote:

Actually, I had skipped the initial setup wizard.

Then your WAN would be DHCP, that's the only possible config out of the box.

Actions #4

Updated by Danny Schuh over 5 years ago

I believe that that was the case. I think that when I manually created the LAN interface, the addressing method was set to none for both v4 and v6, which is why I created this ticket. This is no doubt a side-effect of me not running the setup wizard. Perhaps a userdata-supplied array mentioned in feature request #6457 will help AWS users by not having to manually configure them post-launch.

I would normally close this bug at this point, but it seems that it can be better served to improve the setup wizard as you have pointed out.

Actions #5

Updated by Chris Buechler over 5 years ago

oh, for LAN. Every additional interface defaults to "none", which is most appropriate. Yeah #6457 will address the remaining concern for AWS.

Actions #6

Updated by Chris Buechler over 5 years ago

  • Target version changed from 2.3.2 to 2.4.0
Actions #7

Updated by Jim Thompson over 4 years ago

  • Assignee set to Matthew Smith
  • Target version changed from 2.4.0 to 2.4.1
Actions #8

Updated by Jim Pingle about 4 years ago

  • Target version changed from 2.4.1 to 2.4.2
Actions #9

Updated by Jim Thompson about 4 years ago

  • Assignee changed from Matthew Smith to Renato Botelho
Actions #10

Updated by Renato Botelho almost 4 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100
Actions #11

Updated by Chris Macmahon almost 4 years ago

Tested ok today.

Actions #12

Updated by Jim Pingle almost 4 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF