Project

General

Profile

Actions

action #47303

closed

[aarch64] 'eject_cd' does not work

Added by ggardet_arm almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-02-08
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-zdup-Leap-15.0-gnome@aarch64 fails in
bootloader_uefi
because the call to eject_cd function has no effect.

Test suite description

Reproducible

Fails since (at least) Build 20190206

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

A call to eject_cd function should remove the ISO from CDROM, but it does not.
I am not sure if this function is called at all by another test ATM?

On a standalone QEMU, I tried eject cd0 (from monitor) and it worked properly.


Related issues 2 (0 open2 closed)

Related to openQA Project (public) - action #91971: crosscheck if testapi::eject_cd actually worksResolvedmkittler2021-04-292021-05-15

Actions
Blocks openQA Tests (public) - action #46868: [aarch64][functional][y][migration] enable migration tests on aarch64Resolvedggardet_arm2019-01-302019-03-12

Actions
Actions #1

Updated by ggardet_arm almost 6 years ago

  • Blocks action #46868: [aarch64][functional][y][migration] enable migration tests on aarch64 added
Actions #2

Updated by ggardet_arm almost 6 years ago

From qemu monitor info block returns:

pflash-code-overlay0 (#block555): /home/guillaume/openQA_tests/zdup-Leap-15.0-gnome/raid/pflash-code-overlay0 (qcow2, read-only)
  Attached to:      /machine/unattached/device[1]
  Cache mode:       writeback
  Backing file:     /usr/share/qemu/aavmf-aarch64-code.bin (chain depth: 1)
pflash-vars-overlay0 (#block919): /home/guillaume/openQA_tests/zdup-Leap-15.0-gnome/raid/pflash-vars-overlay0 (qcow2)
  Attached to:      /machine/unattached/device[2]
  Cache mode:       writeback
  Backing file:     /home/guillaume/openQA_tests/opensuse-15.0-aarch64-GM-gnome@aarch64-uefi-vars.qcow2 (chain depth: 1)
floppy0: [not inserted]
  Removable device: not locked, tray closed
  sd0: [not inserted]
  Removable device: not locked, tray closed
hd0-overlay0: /home/guillaume/openQA_tests/zdup-Leap-15.0-gnome/raid/hd0-overlay0 (qcow2)
  Attached to:      hd0-device
  Cache mode:       writeback, ignore flushes
  Backing file:     /home/guillaume/openQA_tests/opensuse-15.0-aarch64-GM-gnome@aarch64.qcow2 (chain depth: 1)
hd1: /home/guillaume/openQA_tests/zdup-Leap-15.0-gnome/raid/hd1 (qcow2)
  Attached to:      hd1-device
  Cache mode:       writeback, ignore flushes
cd0-overlay0: /home/guillaume/openQA_tests/zdup-Leap-15.0-gnome/raid/cd0-overlay0 (qcow2)
  Attached to:      cd0-device
  Removable device: not locked, tray closed
  Cache mode:       writeback, ignore flushes
  Backing file:     /home/guillaume/openQA_tests/openSUSE-Tumbleweed-DVD-aarch64-Snapshot20190125-Media.iso (chain depth: 1)

But eject cd0, cd0-overlay0, or cd0-device returns:

Device 'XXX' not found    

Only eject sd0 works, but this is not where our ISO is attached to.

Actions #3

Updated by ggardet_arm almost 6 years ago

I reported the problem upstream: https://bugs.launchpad.net/qemu/+bug/1815445

Actions #4

Updated by ggardet_arm almost 6 years ago

  • Assignee set to ggardet_arm

PR available to not use broken 'eject_cd' function: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6747

Actions #5

Updated by ggardet_arm almost 6 years ago

  • Priority changed from Normal to Low

Should we remove eject_cd function as it is broken and no test make use of it anymore?

Actions #6

Updated by riafarov almost 6 years ago

  • Status changed from New to Resolved

I believe we can resolve this one, as there is workaround already in place.

Actions #7

Updated by mkittler over 3 years ago

  • Related to action #91971: crosscheck if testapi::eject_cd actually works added
Actions

Also available in: Atom PDF