Devuan bug report logs - #459
autopkgtest-build-qemu does not set up /dev/ttyS[01]

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

Package: autopkgtest
Version: 5.13.1
Severity: minor
Tags: beowulf ceres
Control: found -1 5.10

Dear Maintainer,

"man autopkgtest-virt-qemu" says:
REQUIREMENTS
       autopkgtest-virt-qemu  assumes  that you have already prepared a suitable Debian based QEMU image (see BUILDING IMAGES below for how to create them).
       But you can use any VM which has python3 or python installed and either

       *   opens a root shell on ttyS1, or

       *   has a serial console on ttyS0 where you can log in (getty or similar) with specified user and password. This will then be used to  start  a  root
           shell on ttyS1, to reduce this to the first case and to not assume that ttyS0 stays operational throughout the whole test.

But autopkgtest-build-qemu does not adjust /etc/inittab inside the qemu image,
and autopkgtest-virt-qemu always fails.
Workaround is easy, just modify /etc/inittab in the qemu image.

This issue is found in package versions 5.13.1 and 5.10.

Best regards, Ryutaroh Matsumoto


-- System Information:
Distributor ID:	Debian
Description:	Devuan GNU/Linux 3 (beowulf)
Release:	3
Codename:	beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages autopkgtest depends on:
ii  apt-utils       1.8.2.1
ii  libdpkg-perl    1.19.7
ii  procps          2:3.3.15-2+devuan1
ii  python3         3.7.3-1
ii  python3-debian  0.1.35

Versions of packages autopkgtest recommends:
ii  autodep8  0.18

Versions of packages autopkgtest suggests:
pn  lxc               <none>
pn  lxd               <none>
ii  ovmf              0~20181115.85588389-3+deb10u1
pn  qemu-efi-aarch64  <none>
pn  qemu-efi-arm      <none>
pn  qemu-system       <none>
ii  qemu-utils        1:3.1+dfsg-8+deb10u5
pn  schroot           <none>
ii  vmdb2             0.13.2+git20190215-1

-- no debconf information

Message #10 received at 459@bugs.devuan.org (full text, mbox, reply):

Control: tags -1 debian

Ryutaroh,

Thanks for this

On Sat, May 16, 2020 at 05:03:18PM +0900, Ryutaroh Matsumoto wrote:
> Package: autopkgtest
> Version: 5.13.1
> Severity: minor
> Tags: beowulf ceres
> Control: found -1 5.10
> 
> Dear Maintainer,
> 
> "man autopkgtest-virt-qemu" says:
> REQUIREMENTS
>        autopkgtest-virt-qemu  assumes  that you have already prepared a suitable Debian based QEMU image (see BUILDING IMAGES below for how to create them).
>        But you can use any VM which has python3 or python installed and either
> 
>        *   opens a root shell on ttyS1, or
> 
>        *   has a serial console on ttyS0 where you can log in (getty or similar) with specified user and password. This will then be used to  start  a  root
>            shell on ttyS1, to reduce this to the first case and to not assume that ttyS0 stays operational throughout the whole test.
> 
> But autopkgtest-build-qemu does not adjust /etc/inittab inside the qemu image,
> and autopkgtest-virt-qemu always fails.
> Workaround is easy, just modify /etc/inittab in the qemu image.
> 
> This issue is found in package versions 5.13.1 and 5.10.

autopkgtest is not a forked package and Devuan uses Debian's packages directly.

Can you report this to Debian BTS, please?

Thanks

Mark

Message #17 received at 459@bugs.devuan.org (full text, mbox, reply):

Dear Mark, Thank you for your attention and response. But,

> autopkgtest is not a forked package and Devuan uses Debian's packages directly.
> Can you report this to Debian BTS, please?

I don't think this is a Debian issue.
Debian PID 1 is systemd,
and with systemd ttyS[01] are available
in autopkgtest-built qemu images.

I believe "tag debian" should be removed.

Best regards, Ryutaroh

From: Mark Hindley <mark@hindley.org.uk>
Subject: Re: bug#459: autopkgtest-build-qemu does not set up /dev/ttyS[01]
Date: Sat, 16 May 2020 10:29:48 +0100

> Control: tags -1 debian
> 
> Ryutaroh,
> 
> Thanks for this
> 
> On Sat, May 16, 2020 at 05:03:18PM +0900, Ryutaroh Matsumoto wrote:
>> Package: autopkgtest
>> Version: 5.13.1
>> Severity: minor
>> Tags: beowulf ceres
>> Control: found -1 5.10
>> 
>> Dear Maintainer,
>> 
>> "man autopkgtest-virt-qemu" says:
>> REQUIREMENTS
>>        autopkgtest-virt-qemu  assumes  that you have already prepared a suitable Debian based QEMU image (see BUILDING IMAGES below for how to create them).
>>        But you can use any VM which has python3 or python installed and either
>> 
>>        *   opens a root shell on ttyS1, or
>> 
>>        *   has a serial console on ttyS0 where you can log in (getty or similar) with specified user and password. This will then be used to  start  a  root
>>            shell on ttyS1, to reduce this to the first case and to not assume that ttyS0 stays operational throughout the whole test.
>> 
>> But autopkgtest-build-qemu does not adjust /etc/inittab inside the qemu image,
>> and autopkgtest-virt-qemu always fails.
>> Workaround is easy, just modify /etc/inittab in the qemu image.
>> 
>> This issue is found in package versions 5.13.1 and 5.10.
> 
> autopkgtest is not a forked package and Devuan uses Debian's packages directly.
> 
> Can you report this to Debian BTS, please?
> 
> Thanks
> 
> Mark

Message #22 received at 459@bugs.devuan.org (full text, mbox, reply):

On Sat, May 16, 2020 at 06:33:26PM +0900, Ryutaroh Matsumoto wrote:
> Dear Mark, Thank you for your attention and response. But,
> 
> > autopkgtest is not a forked package and Devuan uses Debian's packages directly.
> > Can you report this to Debian BTS, please?
> 
> I don't think this is a Debian issue.
> Debian PID 1 is systemd,

No. Both sysvinit and runit-init are available in Debian. So this issue would be
present on a Debian system not running systemd as PID1.

Best wishes

Mark

Message #27 received at 459@bugs.devuan.org (full text, mbox, reply):

>> I don't think this is a Debian issue.
>> Debian PID 1 is systemd,
> 
> No. Both sysvinit and runit-init are available in Debian. So this issue would be
> present on a Debian system not running systemd as PID1.

Umm, but is there any option to instruct autopkgtest to
make a Debian qemu image with PID 1 not being systemd?
I do not know such an option.

How can anybody reproduce this issue on Debian??
Do you have any idea?

Best regards, Ryutaroh


From: Mark Hindley <mark@hindley.org.uk>
Subject: Re: bug#459: autopkgtest-build-qemu does not set up /dev/ttyS[01]
Date: Sat, 16 May 2020 10:41:41 +0100

> On Sat, May 16, 2020 at 06:33:26PM +0900, Ryutaroh Matsumoto wrote:
>> Dear Mark, Thank you for your attention and response. But,
>> 
>> > autopkgtest is not a forked package and Devuan uses Debian's packages directly.
>> > Can you report this to Debian BTS, please?
>> 
>> I don't think this is a Debian issue.
>> Debian PID 1 is systemd,
> 
> No. Both sysvinit and runit-init are available in Debian. So this issue would be
> present on a Debian system not running systemd as PID1.
> 
> Best wishes
> 
> Mark

Message #30 received at 459@bugs.devuan.org (full text, mbox, reply):

Control: tags -1 moreinfo

Ryutaroh,

On Sat, May 16, 2020 at 07:09:31PM +0900, Ryutaroh Matsumoto wrote:
> I have no idea on how to work around #461, and without a workaround or a right
> fix to #461, fixes to #459 or #460 do not have much value, as autopkgtest
> remains completely unusable with qemu testbed, besides #459 and #460 have easy
> workarounds.
> 
> I will put my effort on #460 after #461 finds a workaround or a fix.

Now #461 is fixed, did you get resolutions for #460 and #459?

Thanks

Mark

Send a report that this bug log contains spam.