Bug 37938 – Appliance configuration with multiple network cards can be confusing

Bug 37938 - Appliance configuration with multiple network cards can be confusing


Summary:	Appliance configuration with multiple network cards can be confusing

Status:	RESOLVED DUPLICATE of bug 38330

Product:	UCS
Classification:	Unclassified
Component:	UMC - Setup wizard
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-03-04 19:52 CET by Alexander Kläser
Modified:	2015-07-08 13:31 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Screenshot of network page in setup wizard (44.19 KB, image/png) 2015-03-04 19:56 CET, Alexander Kläser	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 Alexander Kläser

2015-03-04 19:52:36 CET

I started a UCS 4.0-1 appliance with Virtual Box and 2 network devices (NAT + Host-Only). Only the 1st devices is configured via UCR. The setup wizard, shows on the network page only an IP address for the first device, the second one is empty. I re-queried DHCP addresses which consequently filled out the second interfaces, as well. However, when proceeding to the next page, these properties do not seem to be applied, as the global DHCP checkbox did not change.

Comment 1 Alexander Kläser

2015-03-04 19:56:46 CET

Created attachment 6746 [details]
Screenshot of network page in setup wizard

Comment 2 Alexander Kläser

2015-07-08 13:31:04 CEST

Has been fixed with the adjustments from Bug 38330.

*** This bug has been marked as a duplicate of bug 38330 ***