Bug 849395

Created attachment 605456 [details]
File: program.log

This seems to be related to ipv6 support?

Here's the traceback, which it doesn't seem to have attached: 

The following was filed automatically by anaconda:
anaconda 18.6 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 639, in <genexpr>
    ipv6_addr = socket.inet_ntop(socket.AF_INET6, "".join(str(byte) for byte in addr))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 639, in _refresh_device_cfg
    ipv6_addr = socket.inet_ntop(socket.AF_INET6, "".join(str(byte) for byte in addr))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 587, in refresh_ui
    self._refresh_device_cfg((device, num_of_tries))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 362, in on_device_selection_changed
    self.refresh_ui(device)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb8 in position 0: invalid start byte

What steps did you take to get this traceback?  Did you enable ipv6 on the command line?

This is a kvm guest with bridged networking. The network is dual stack, and has radvd running to assign ipv6 addresses. The only thing passed on the command line was the 'xdriver=vesa' to get a working graphical install in virt-viewer. 

The instance did have a valid/active ipv6 address... as well as a ipv4 one. I just couldn't continue the install due to this error/issue.

Patch sent for review.

You can check the fix with updates image by adding
updates=http://rvykydal.fedorapeople.org/updates.ipv6.img

 
> You can check the fix with updates image by adding
> updates=http://rvykydal.fedorapeople.org/updates.ipv6.img

to boot options

I can confirm that this fixes the issue I was seeing. ;) 

Thanks!

Proposing as Alpha blocker; since F17 we've considered IPv6 to be 'supported functionality' so far as networking goes. So this would violate any criterion requiring networking - e.g. "The installer must be able to use at least one of the HTTP or FTP remote package source options" - in the case of IPv6.

This is a bit different from previous bugs, admittedly, in that we're now talking IPv6 connectivity *within anaconda* - for F17, we focused on bugs which prevented you from easily obtaining IPv6 connectivity in an *installed system*.

Discussed at 2012-08-22 blocker review meeting. Accepted as a blocker per criterion "The installer must be able to use at least one of the HTTP or FTP remote package source options", in the case of IPv6 addressing - it seems anaconda crashes as soon as it tries to bring up networking, for an IPv6/radvd connection.

anaconda-18.6.1-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.6.1-1.fc18

Package anaconda-18.6.1-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.6.1-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-12550/anaconda-18.6.1-1.fc18
then log in and leave karma (feedback).

I can consistently trigger this problem on a bare-metal machine with no cmdline tinkering. We have IPv6 connectivity in our office.

The updates.img from comment #5 fixes the issue.

I can confirm no traceback occurs with F18 Alpha TC5 (using the same machine).

18.6.5-1 was pushed stable, so closing.