All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>,
	linux-integrity@vger.kernel.org,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Stefan Berger <stefanb@us.ibm.com>
Subject: Re: [PATCH 1/1] travis: Fix Fedora
Date: Fri, 30 Apr 2021 21:24:53 +0200	[thread overview]
Message-ID: <YIxZhRcN4fbZ6Xjy@pevik> (raw)
In-Reply-To: <YIxW/h41HTozljSo@pevik>

Hi Mimi,

> > [Cc'ing Stefan]

> > Hi Petr,

> > On Fri, 2021-04-30 at 15:24 +0200, Petr Vorel wrote:
> > > > On Thu, 2021-04-29 at 07:39 +0200, Petr Vorel wrote:
> > > > > Fedora recently got 2.33, which requires on Travis CI to use podman.

> > > > > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > > > > ---
> > > > > Hi Mimi,

> > > > > Tested [1].

> > > > > Previously Fedora fails on autoconf issue [2], which is caused by
> > > > > faccessat2 incompatibility on glibc 2.33:

> > > > > /usr/bin/autoconf: This script requires a shell more modern than all
> > > > > /usr/bin/autoconf: the shells that I found on your system.
> > > > > /usr/bin/autoconf: Please tell bug-autoconf@gnu.org about your system,
> > > > > /usr/bin/autoconf: including any error possibly output before this
> > > > > /usr/bin/autoconf: message. Then install a modern shell, or manually run
> > > > > /usr/bin/autoconf: the script under such a shell if you do have one.
> > > > > autoreconf: /usr/bin/autoconf failed with exit status: 1

> > > > > [1] https://travis-ci.org/github/pevik/ima-evm-utils/builds/768789641
> > > > > [2] https://travis-ci.org/github/pevik/ima-evm-utils/jobs/767259578

> > > > The "boot_aggregate" test should succeed, but for some reason is now
> > > > being skipped.

> > > > PASS: ima_hash.test
> > > > PASS: sign_verify.test
> > > > SKIP: boot_aggregate.test
> > > Not sure why, I'll try to have look. Maybe missing dependencies?
> > > I suppose this is not related to the patch at all.

> > The boot_aggregate test has a dependency on a software TPM.  From the
> > end of the log, there's problems communicating with the swtpm.

> > which: no tpm_server in (../src:/root/ima-evm-utils-install/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)
> > INFO: Starting software TPM: /usr/bin/swtpm
> > INFO: Sending software TPM startup
> > TSS_Socket_Open: Error on connect to localhost:2321
> > TSS_Socket_Open: client connect: error 111 Connection refused
> > startup: failed, rc 000b0008
> > TSS_RC_NO_CONNECTION - Failure connecting to lower layer
> > INFO: Retry sending software TPM startup
> > TSS_Socket_Open: Error on connect to localhost:2321
> > TSS_Socket_Open: client connect: error 111 Connection refused
> > startup: failed, rc 000b0008
> > TSS_RC_NO_CONNECTION - Failure connecting to lower layer
> > INFO: Software TPM startup failed
> Hm, testing if sudo is needed for podman to be able to the container run swtpm.
OK, sudo didn't help:
https://travis-ci.org/github/pevik/ima-evm-utils/jobs/769054065

I have no idea what's wrong.

Kind regards,
Petr

> > > > I tested with/without this patch on our internal travis.   I was seeing
> > > > the Tumbleweed problem, but am not seeing this problem with Fedora
> > > > latest yet.  Both with/without the patch, Fedora latest works properly
> > > "not yet" => if you check glibc package update for the version. I bet it's still
> > > 2.32. Thanks for testing it.

> > From the local raw log:
> >   glibc-devel-2.33-
> > 5.fc34.x86_64
> >   glibc-headers-x86-2.33-5.fc34.noarch

> OK, if your internal travis is working with 2.33 maybe the rest of the setup is
> different (different docker and/or runc), because this patch is really needed on
> public Travis.

> Kind regards,
> Petr

> > thanks,

> > Mimi

> > > > on our internal travis.


      reply	other threads:[~2021-04-30 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  5:39 [PATCH 1/1] travis: Fix Fedora Petr Vorel
2021-04-30 12:40 ` Mimi Zohar
2021-04-30 13:24   ` Petr Vorel
2021-04-30 13:44     ` Mimi Zohar
2021-04-30 19:14       ` Petr Vorel
2021-04-30 19:24         ` Petr Vorel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YIxZhRcN4fbZ6Xjy@pevik \
    --to=pvorel@suse.cz \
    --cc=linux-integrity@vger.kernel.org \
    --cc=stefanb@us.ibm.com \
    --cc=zohar@linux.ibm.com \
    --cc=zohar@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.