Fuel 9 does not allow multiple NICs to be enabled for public and private networks

Bug #1602415 reported by Anton
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Sustaining
Mitaka
Confirmed
Medium
Fuel Sustaining

Bug Description

Detailed bug description:
 When installing MOS 9 (Fuel), I use two physical network cards and separate networks, one for the public network and one for the private network to keep the traffic separate. The networks are setup correctly. The public network has DHCP disabled and uses NAT, the private network is an isolated network with DHCP disabled. When enabling eth1 on the Fuel TUI, I input the correct network settings and check them. I then go to the Bootstrap Image tab and when I check these settings, I always get a error stating the the repositories are not available.

Steps to reproduce:
 Install MOS 9 (Fuel 9) on a virtual machine, configure two networks (Private, Public) Private having no DHCP and isolated, Public having no DHCP and NAT. Create a Fuel VM and connect Private first and Public to it second. connect the Mirantis 9 Fuel iso to it and boot. When the TUI appears, configure eth1 to have the settings:
Enabled
Static
172.16.1.2
255.255.255.0
172.16.1.1

Press Check and press Apply

From the menu, choose Bootstrap Image
Press Check

The error will come up at this step.

Expected results:
 I was expecting to be able to use the second NIC (eth0) as the public network interface and use it to download the Bootstrap Image
Actual result:
 I am unable to continue the install of Fuel 9.
Reproducibility:
 Always
Workaround:
 NA
Impact:
 Fuel 9 cannot be setup with multiple NICs
Description of the environment:
 Operation system: CentOS 7
 Versions of components: MOS 9 GA
 Reference architecture: x86_64
 Network model: 3 networks: Public (NAT, no DHCP) , private (internal only, no DHCP)
 Related projects installed: NA
Additional information:
 Anton Moczygemba

Tags: area-python
Revision history for this message
Andrey Grebennikov (agrebennikov) wrote :

Please mark as invalid - network settings were wrong. Once they are right - everything is working.

Changed in fuel:
status: New → Invalid
Revision history for this message
Anton (antonwoods) wrote :

I reinstalled MOS 9. I then set the correct IP address, sugnet address, and gateway address for the public network. I then switched screens, logged in as root, and pinged 8.8.8.8 successfully and pinged google.com successfully. I sent back to the Fuel Text User Interface and checked the Bootstrap Image again and it faied. I am re-opening this ticket because I verified that I can ping 8.8.8.8 and google.com, and validated the NPT servers, however the Bootstrap check does not work.

Changed in fuel:
status: Invalid → New
Revision history for this message
Anton (antonwoods) wrote :

Also, I after ignoring the Bootstrap error, I successfully continued the installation and completed the installation.

Revision history for this message
Dmitry Klenov (dklenov) wrote :

@Andrey, can you please tell, what exactly was configured incorrectly?

tags: added: area-python
Dmitry Klenov (dklenov)
Changed in fuel:
milestone: none → 9.1
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
importance: Undecided → High
status: New → Confirmed
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 9.1 → 10.0
assignee: Fuel Sustaining (fuel-sustaining-team) → l23network (l23network)
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: Registry Administrators (registry) → Fuel Sustaining (fuel-sustaining-team)
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
importance: High → Medium
Revision history for this message
rezroo (r3za) wrote :

In fuelmenu check "skip build of bootstrap image" to avoid this bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.