[ppc64el] curtin block-discover fails to generate storage-config for partitions on raids
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Committed
|
Medium
|
Unassigned | ||
subiquity |
Invalid
|
Undecided
|
Unassigned |
Bug Description
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,
the install fails printing the following errors in the console where subiquity is running:
ERROR: hook /usr/share/
Traceback (most recent call last):
File "/snap/
symb['add_
File "/usr/share/
is_kernel = report[
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-
608K subiquity-
56K subiquity-
20K subiquity-
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/
fcntl.
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-
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
Related branches
- Paride Legovini: Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 1013 lines (+975/-3)3 files modifiedcurtin/storage_config.py (+3/-3)
tests/data/probert_storage_raid1_partitions.json (+951/-0)
tests/unittests/test_storage_config.py (+21/-0)
Changed in curtin: | |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in subiquity: | |
status: | New → Invalid |
Reading package lists... us.archive. ubuntu. com/ubuntu/ dists/focal/ main/binary- ppc64el/ Packages
E: Failed to fetch
http://
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: cache=unsafe, size=6 --disk bus=virtio, cache=unsafe, size=6 bus=virtio, cache=unsafe, size=6 --disk img,bus= virtio, readonly= on --cdrom /path/to/ focal-live- apport/ general- hooks/powerpc. py crashed: subiquity/ 1335/usr/ lib/python3/ dist-packages/ apport/ report. py", line info']( report, ui) apport/ general- hooks/powerpc. py", line 42, in add_info 'ProblemType' ].startswith( 'Kernel' ) or 'linux' in get('Package' ) debug.log. * debug.log. 2167 debug.log. 2180 debug.log. 4033 subiquity/ 1335/lib/ python3. 6/site- packages/ subiquity/ cmd/tui. py", opts.answers, fcntl.LOCK_EX | fcntl.LOCK_NB) debug.log. 2167 log file shows very similar tracebacks. paste.ubuntu. com/p/xvKtK5bY5 P/
>
> 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,
> --disk disk3.qcow2,
> vol=answers.
> server-ppc64el.iso
>
> the install fails printing the following errors in the console where
> subiquity is running:
>
>
> ERROR: hook /usr/share/
> Traceback (most recent call last):
> File
> "/snap/
> 198, in _run_hook
> symb['add_
> File "/usr/share/
> is_kernel = report[
> report.
> 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-
> 608K subiquity-
> 56K subiquity-
> 20K subiquity-
>
> 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/
> line 136, in main
> fcntl.flock(
> 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-
>
> 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://
>
> ** A...