Comment 2 for bug 1853018

   Reading package lists...
        E: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/focal/main/binary-ppc64el/Packages
404 Not Found [IP: 91.189.91.23 80]
        E: Some index files failed to download. They have been ignored, or
old ones used instead.

Failure during apt-get update command,

+ /snap/subiquity/1335/usr/bin/python3 -m curtin in-target -- apt-get update

On Mon, Nov 18, 2019 at 10:10 AM Paride Legovini <
<email address hidden>> wrote:

> Public bug reported:
>
> Premise: I don't think this is really specific to ppc64el, but as I'm
> not sure of what the problem is I'll start with describing what I
> observe, then let's try to draw the right conclusions.
>
>
> When trying to perform an automated raid1 installation with the
> answers.yaml [1] by using virt-install like this:
>
> virt-install --name isotest-raid1 --os-variant ubuntu18.04
> --noautoconsole --wait -1 --memory 2048 --disk
> bus=virtio,cache=unsafe,size=6 --disk bus=virtio,cache=unsafe,size=6
> --disk disk3.qcow2,bus=virtio,cache=unsafe,size=6 --disk
> vol=answers.img,bus=virtio,readonly=on --cdrom /path/to/focal-live-
> server-ppc64el.iso
>
> the install fails printing the following errors in the console where
> subiquity is running:
>
>
> ERROR: hook /usr/share/apport/general-hooks/powerpc.py crashed:
> Traceback (most recent call last):
> File
> "/snap/subiquity/1335/usr/lib/python3/dist-packages/apport/report.py", line
> 198, in _run_hook
> symb['add_info'](report, ui)
> File "/usr/share/apport/general-hooks/powerpc.py", line 42, in add_info
> is_kernel = report['ProblemType'].startswith('Kernel') or 'linux' in
> report.get('Package')
> TypeError: argument of type 'NoneType' is not iterable
>
>
> which seems to be an error with the call to apport. This is probably by
> itself a bug. Looking in /var/log/install, there are 3 subiquity log files:
>
> $ du -h subiquity-debug.log.*
> 608K subiquity-debug.log.2167
> 56K subiquity-debug.log.2180
> 20K subiquity-debug.log.4033
>
> The bigger one is likely the one that actually did the installation.
> Looking at what's in it, the first thing I notice is:
>
>
> 2019-11-17 11:24:36,725 ERROR subiquity:139 Failed to lock auto answers
> file, proceding without it.
> Traceback (most recent call last):
> File
> "/snap/subiquity/1335/lib/python3.6/site-packages/subiquity/cmd/tui.py",
> line 136, in main
> fcntl.flock(opts.answers, fcntl.LOCK_EX | fcntl.LOCK_NB)
> BlockingIOError: [Errno 11] Resource temporarily unavailable
>
>
> so this subiquity seems to have lost the "race" lock the answers.yaml, but
> then did a lot of things. Strange. At the very end of the log there are two
> tracebacks, probably the true reason of the failure. The
> subiquity-debug.log.2167 log file shows very similar tracebacks.
>
> Interesting data points:
>
> - The very same installation succeeds on amd64;
> - An automated, non-raid installation done on ppc64el
> using virt-install in the same way suceeds;
> - A non-automated install with the same setup on
> ppc64el also succeeds (!).
>
> Attached: the full /var/log of the installer system.
>
> Paride
>
>
> [1] http://paste.ubuntu.com/p/xvKtK5bY5P/
>
> ** Affects: subiquity
> Importance: Undecided
> Status: New
>
> ** Attachment added: "full /var/log of the installer system"
>
> https://bugs.launchpad.net/bugs/1853018/+attachment/5306235/+files/_var_log.tar.gz
>
> --
> You received this bug notification because you are subscribed to
> subiquity.
> Matching subscriptions: subiquity-bugs
> https://bugs.launchpad.net/bugs/1853018
>
> Title:
> [autoinstall] raid1 install fails on ppc64el
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/subiquity/+bug/1853018/+subscriptions
>