UEC Installer Only Configures One Network Interface

Bug #448036 reported by Joseph Salisbury
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Eucalyptus
Invalid
Undecided
Unassigned
netcfg (Debian)
New
Unknown
netcfg (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

I installed a Cluster Controller and Node Controller using the 09-Oct-2009 daily build of Karmic. This bug is to request a future enhancement request to be put on the wish list. During the installation of UEC, one of the questions is the IP Address for eth0 if the network is configured manually versus DHCP. However, the installer only allows one physical Interface to be configured - regardless of the number of physical interfaces on the machine. For example: my machine has four network interfaces, but I could only configure one during the install. Not a major issues since the other interfaces can be configured after the installation is complete, which is why this is a wish list bug.

Revision history for this message
In , Thomas Hood (jdthood-yahoo) wrote : retitle 257883 to netcfg: Please offer to configure all network interfaces

retitle 257883 netcfg: Please offer to configure all network interfaces

Revision history for this message
In , Joey Hess (joeyh) wrote : configuring all interfaces

I agree that configuring all interfaces would be nice. I have some
hardware on which I want to have dhcp done on all interfaces, and I'd
just as soon not even pick which to use, just use the first that DHCP'd.
Or maybe even use multiple interfaces with load balancing.

--
see shy jo

Revision history for this message
In , Michael Ablassmeier (abi) wrote : merging

merge 264984 257883
thanks

sorry, overlooked that one, hope merging is okey.

bye,
    - michael

Revision history for this message
In , Thomas Hood (jdthood-aglu) wrote : housekeeping

retitle 295888 Lists multiple NICs of same type the same way
severity 295888 wishlist
tags 248061 d-i
tags 295888 d-i
merge 295888 248061
tags 292862 d-i
merge 292862 257883
thanks
--
Thomas Hood <email address hidden>

Revision history for this message
In , Joey Hess (joeyh) wrote : d-i tag removal
Download full text (5.8 KiB)

# I decided to remove the d-i tag from all packages maintained by the
# d-i team, so the list of d-i tagged bugs reduces to bugs that affect
# d-i but are not in d-i itself
tag 328992 - d-i
tag 329391 - d-i
tag 224641 - d-i
tag 213482 - d-i
tag 220282 - d-i
tag 222718 - d-i
tag 243373 - d-i
tag 274307 - d-i
tag 276726 - d-i
tag 283712 - d-i
tag 284736 - d-i
tag 292570 - d-i
tag 317062 - d-i
tag 258834 - d-i
tag 201396 - d-i
tag 220269 - d-i
tag 252121 - d-i
tag 291723 - d-i
tag 218598 - d-i
tag 218598 - d-i
tag 157888 - d-i
tag 183366 - d-i
tag 196033 - d-i
tag 200467 - d-i
tag 201252 - d-i
tag 205519 - d-i
tag 211147 - d-i
tag 212442 - d-i
tag 213834 - d-i
tag 215471 - d-i
tag 215473 - d-i
tag 216711 - d-i
tag 217503 - d-i
tag 218485 - d-i
tag 218610 - d-i
tag 218765 - d-i
tag 220483 - d-i
tag 220825 - d-i
tag 220949 - d-i
tag 221598 - d-i
tag 222308 - d-i
tag 222506 - d-i
tag 223743 - d-i
tag 224642 - d-i
tag 224904 - d-i
tag 228839 - d-i
tag 230511 - d-i
tag 230552 - d-i
tag 231137 - d-i
tag 231222 - d-i
tag 231624 - d-i
tag 231643 - d-i
tag 231766 - d-i
tag 231782 - d-i
tag 233312 - d-i
tag 233540 - d-i
tag 233957 - d-i
tag 234199 - d-i
tag 235376 - d-i
tag 235980 - d-i
tag 237397 - d-i
tag 237401 - d-i
tag 238292 - d-i
tag 238911 - d-i
tag 241434 - d-i
tag 242182 - d-i
tag 243082 - d-i
tag 243085 - d-i
tag 243565 - d-i
tag 243857 - d-i
tag 244959 - d-i
tag 244975 - d-i
tag 245136 - d-i
tag 245164 - d-i
tag 245268 - d-i
tag 247260 - d-i
tag 247593 - d-i
tag 247725 - d-i
tag 247960 - d-i
tag 248067 - d-i
tag 248163 - d-i
tag 248261 - d-i
tag 248454 - d-i
tag 248638 - d-i
tag 249305 - d-i
tag 250047 - d-i
tag 250413 - d-i
tag 250471 - d-i
tag 250823 - d-i
tag 251007 - d-i
tag 254727 - d-i
tag 257201 - d-i
tag 257211 - d-i
tag 257213 - d-i
tag 257285 - d-i
tag 258010 - d-i
tag 258085 - d-i
tag 258216 - d-i
tag 258316 - d-i
tag 258496 - d-i
tag 258545 - d-i
tag 258623 - d-i
tag 258908 - d-i
tag 259007 - d-i
tag 259264 - d-i
tag 259297 - d-i
tag 259374 - d-i
tag 259825 - d-i
tag 259869 - d-i
tag 259871 - d-i
tag 259899 - d-i
tag 261100 - d-i
tag 261200 - d-i
tag 261416 - d-i
tag 262043 - d-i
tag 262140 - d-i
tag 263075 - d-i
tag 265290 - d-i
tag 265517 - d-i
tag 266133 - d-i
tag 267441 - d-i
tag 267650 - d-i
tag 268495 - d-i
tag 268817 - d-i
tag 268950 - d-i
tag 269077 - d-i
tag 269653 - d-i
tag 269821 - d-i
tag 269972 - d-i
tag 270136 - d-i
tag 270239 - d-i
tag 270728 - d-i
tag 271065 - d-i
tag 271354 - d-i
tag 271706 - d-i
tag 272176 - d-i
tag 272411 - d-i
tag 272901 - d-i
tag 273074 - d-i
tag 273193 - d-i
tag 273982 - d-i
tag 275262 - d-i
tag 275552 - d-i
tag 276100 - d-i
tag 277901 - d-i
tag 280122 - d-i
tag 282308 - d-i
tag 287408 - d-i
tag 287409 - d-i
tag 287412 - d-i
tag 287413 - d-i
tag 290382 - d-i
tag 294814 - d-i
tag 294881 - d-i
tag 296097 - d-i
tag 299610 - d-i
tag 304565 - d-i
tag 310455 - d-i
tag 310652 - d-i
tag 313049 - d-i
tag 317043 - d-i
tag 317165 - d-i
tag 321109 - d-i
tag 322376 - d-i
tag 322460 - d-i
tag 322464 - d-i
tag 322479 - d-i
tag 323804 - d-i
tag 324506 - d-i
tag 327393 - d-i
tag 329733 - d-i
tag 226758 - d-i
tag 234887 - d-i
tag 243961 - d-i
tag 246327 - d-i
tag 246764 - d-i
tag 247093 - d-i
tag 247733 - d-i
t...

Read more...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I installed a Cluster Controller and Node Controller using the 09-Oct-2009 daily build of Karmic. This bug is to request a future enhancement request to be put on the wish list. During the installation of UEC, one of the questions is the IP Address for eth0 if the network is configured manually versus DHCP. However, the installer only allows one physical Interface to be configured - regardless of the number of physical interfaces on the machine. For example: my machine has four network interfaces, but I could only configure one during the install. Not a major issues since the other interfaces can be configured after the installation is complete, which is why this is a wish list bug.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

I haven't personally confirmed this, but I strongly suspect that this is the case.

I believe the inadequate logic is in eucalyptus-udeb.finish-install, though I haven't tried to fix it yet myself.

:-Dustin

Changed in eucalyptus (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
status: Confirmed → Triaged
Changed in eucalyptus:
status: New → Invalid
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Moving this bug over to debian-installer.

Colin, is there anything we can realistically do here in the installer to help with multi-NIC systems? This will necessarily be the case for multi-cluster CC machines where one NIC is on the CLC's subnet and the other NIC is on the NC's subnet.

affects: eucalyptus (Ubuntu) → debian-installer (Ubuntu)
Changed in debian-installer (Ubuntu):
importance: Low → Medium
status: Triaged → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

This has been on the netcfg wishlist for some years now. I wouldn't hold your breath too much, and I doubt there's anything we can do as a quick hack, but it may happen some day.

affects: debian-installer (Ubuntu) → netcfg (Ubuntu)
Changed in netcfg (Ubuntu):
importance: Medium → Wishlist
status: Confirmed → Triaged
Changed in netcfg (Debian):
status: Unknown → New
Revision history for this message
Amos Hayes (ahayes-polkaroo) wrote :

I have run into a situation where this is more troublesome. In my case, I'm trying to deploy Ubuntu server on a diskless system using iSCSI. The storage network is isolated and only accessible on one network interface and the other interface is used for traditional network traffic and internet connectivity.

This means I have to install without internet connectivity which prevents me, for example, from specifying alternative packages to what is on the CD. And right now, that means I can't install a version of open-iscsi from proposed, and so my install will fail.

I realize this is an edge case, but as ubuntu server makes its way into more complex environments, the ability to configure multiple interfaces during install could save quite a few headaches. Particularly in catch-22 situations like mine.

As a side note, ifconfig doesn't seem present when I drop to a shell, at least not at the install stage where I need it (before choosing the install target) so I can't figure out how to bring up the second interface manually. This is the server CD, not the live CD.

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.