Bug 12073 - selftest: setUpClass failed failing on ubuntu 17.04 (oeqa.selftest.signing.Signing)
Summary: selftest: setUpClass failed failing on ubuntu 17.04 (oeqa.selftest.signing.Si...
Status: RESOLVED DUPLICATE of bug 12022
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.5 M1
Assignee: oscar lopez arandas
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-09-12 14:19 UTC by oscar lopez arandas
Modified: 2017-11-29 20:54 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
FULL.LOG (25.97 KB, text/x-log)
2017-09-12 14:19 UTC, oscar lopez arandas
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description oscar lopez arandas 2017-09-12 14:19:40 UTC
Created attachment 4002 [details]
FULL.LOG

STATUS: FAILED
BUILD: 2.2.2: rc2-60402978fe3648bf560b3386c6e9dd661cdf2083
ENVIRONMENT: Ubuntu 17.04 x86-64

There are 2 ways of manual and automatic reproduction.

STEPS TO REPRODUCE MANUAL: 
Steps:
1. Generate a gpg key
gpg --gen-keyAnd provide this info when requested:

key: RSAkey-size: 2048key-valid: 0realname: testuseremail: testuser@email.comcomment: nocommentpassphrase: test123
2. Create a secret.txt with 'test123' in it.3. Export the secret and the public key:
gpg --export --armor "testuser (nocomment) <testuser@testemail.com>" > key.pubgpg --export-secret-keys --armor "testuser (nocomment) <testuser@testemail.com>" > key.secret
4. Add to local.conf:
INHERIT += "sign_rpm"RPM_GPG_PASSPHRASE_FILE = "/home/daniel/poky/meta-selftest/files/secret.txt"RPM_GPG_NAME = "testuser"RPM_GPG_PUBKEY = "/home/daniel/poky/meta-selftest/files/key.pub"GPG_PATH = "/home/daniel/poky/meta-selftest/files/"
5. bitbake -c cleansstate ed6. bitbake -c clean ed7. bitbake ed8. tmp/sysroots/x86_64-linux/usr/bin/rpm --import /home/daniel/poky/meta-selftest/files/key.pub9. tmp/sysroots/x86_64-linux/usr/bin/rpm --checksig tmp/deploy/rpm/i586/ed-1.9-r0.i586.rpm

STEPS TO REPRODUCE AUTOMATED:

oe-selftest –r signing


EXPECTED OUTCOME: 

it should show that the package was signed correctly: 

eg :tmp/deploy/rpm/i586/ed-1.9-r0.i586.rpm: rsa sha1 md5 OK 

ACTUAL OUTCOME:
======================================================================
ERROR [0.000s]: setUpClass (oeqa.selftest.signing.Signing)
----------------------------------------------------------------------
AssertionError: Command 'gpg --homedir /tmp/oeqa-signing-hc7m5doc --import /home/ab/autobuilder/yocto-worker/nightly-oe-selftest-ubuntu1704/build/meta-selftest/files/signing/key.pub /home/ab/autobuilder/yocto-worker/nightly-oe-selftest-ubuntu1704/build/meta-selftest/files/signing/key.secret' returned non-zero exit status 2:
gpg: keybox '/tmp/oeqa-signing-hc7m5doc/pubring.kbx' created
gpg: /tmp/oeqa-signing-hc7m5doc/trustdb.gpg: trustdb created
gpg: key 7B31316B5D64AD52: public key "testuser (nocomment) <testuser@testemail.com>" imported
gpg: key 7B31316B5D64AD52: "testuser (nocomment) <testuser@testemail.com>" not changed
gpg: key 7B31316B5D64AD52/7B31316B5D64AD52: error sending to agent: Inappropriate ioctl for device
gpg: error building skey array: Inappropriate ioctl for device
gpg: Total number processed: 2
gpg:               imported: 1
gpg:              unchanged: 1
gpg:       secret keys read: 1

----------------------------------------------------------------------
NOTE: log in attchment
Comment 1 Leonardo Sandoval Gonzalez 2017-09-20 15:06:41 UTC
Although this bug is pretty similar to bug 12022, this is failing in the gpg launch and bug 12022 on the rpmsign, so partially related. The common denominator is that both bugs (this one and 12022) are happening on the same distro. Moving to next release due to freeze.
Comment 2 Leonardo Sandoval Gonzalez 2017-09-25 21:18:58 UTC
recent log reported by RP:

https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/540/steps/Running%20oe-selftest/logs/stdio
Comment 3 Richard Purdie 2017-09-25 21:27:05 UTC
As well as pyro above, it was seen on morty:

https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/540/steps/Running%20oe-selftest/logs/stdio

(debian9.yocto.io worker)
Comment 4 Leonardo Sandoval Gonzalez 2017-09-26 16:16:25 UTC
(In reply to comment #0)
> Created attachment 4002 [details]
> FULL.LOG
> 
> STATUS: FAILED
> BUILD: 2.2.2: rc2-60402978fe3648bf560b3386c6e9dd661cdf2083
> ENVIRONMENT: Ubuntu 17.04 x86-64
> 
> There are 2 ways of manual and automatic reproduction.
> 
> STEPS TO REPRODUCE MANUAL: 
> Steps:
> 1. Generate a gpg key
> gpg --gen-keyAnd provide this info when requested:
> 
> key: RSAkey-size: 2048key-valid: 0realname: testuseremail:
> testuser@email.comcomment: nocommentpassphrase: test123
> 2. Create a secret.txt with 'test123' in it.3. Export the secret and the
> public key:
> gpg --export --armor "testuser (nocomment) <testuser@testemail.com>" >
> key.pubgpg --export-secret-keys --armor "testuser (nocomment)
> <testuser@testemail.com>" > key.secret
> 4. Add to local.conf:
> INHERIT += "sign_rpm"RPM_GPG_PASSPHRASE_FILE =
> "/home/daniel/poky/meta-selftest/files/secret.txt"RPM_GPG_NAME =
> "testuser"RPM_GPG_PUBKEY =
> "/home/daniel/poky/meta-selftest/files/key.pub"GPG_PATH =
> "/home/daniel/poky/meta-selftest/files/"
> 5. bitbake -c cleansstate ed6. bitbake -c clean ed7. bitbake ed8.
> tmp/sysroots/x86_64-linux/usr/bin/rpm --import
> /home/daniel/poky/meta-selftest/files/key.pub9.
> tmp/sysroots/x86_64-linux/usr/bin/rpm --checksig
> tmp/deploy/rpm/i586/ed-1.9-r0.i586.rpm
> 

> STEPS TO REPRODUCE AUTOMATED:
> 
> oe-selftest –r signing
> 
> 
> EXPECTED OUTCOME: 
> 
> it should show that the package was signed correctly: 
> 
> eg :tmp/deploy/rpm/i586/ed-1.9-r0.i586.rpm: rsa sha1 md5 OK 
> 
> ACTUAL OUTCOME:
> ======================================================================
> ERROR [0.000s]: setUpClass (oeqa.selftest.signing.Signing)
> ----------------------------------------------------------------------
> AssertionError: Command 'gpg --homedir /tmp/oeqa-signing-hc7m5doc --import
> /home/ab/autobuilder/yocto-worker/nightly-oe-selftest-ubuntu1704/build/meta-
> selftest/files/signing/key.pub
> /home/ab/autobuilder/yocto-worker/nightly-oe-selftest-ubuntu1704/build/meta-
> selftest/files/signing/key.secret' returned non-zero exit status 2:
> gpg: keybox '/tmp/oeqa-signing-hc7m5doc/pubring.kbx' created
> gpg: /tmp/oeqa-signing-hc7m5doc/trustdb.gpg: trustdb created
> gpg: key 7B31316B5D64AD52: public key "testuser (nocomment)
> <testuser@testemail.com>" imported
> gpg: key 7B31316B5D64AD52: "testuser (nocomment) <testuser@testemail.com>"
> not changed
> gpg: key 7B31316B5D64AD52/7B31316B5D64AD52: error sending to agent:
> Inappropriate ioctl for device
> gpg: error building skey array: Inappropriate ioctl for device
> gpg: Total number processed: 2
> gpg:               imported: 1
> gpg:              unchanged: 1
> gpg:       secret keys read: 1
> 
> ----------------------------------------------------------------------
> NOTE: log in attchment


Oscar, lets use the keys defined on meta-selftest. Can you please run the same manual test with this command:

$ mkdir /tmp/oeqa-signing-oscar $ or some folder which is unique on /tmp
$ gpg --batch --homedir /tmp/oeqa-signing-oscar --import <path to poky morty>/meta-selftest/files/signing/key.pub /<path to poky morty>/meta-selftest/files/signing/key.secret

I have tested the above command on a ubuntu 1704 box and I have no issues. This the gnupg version I used:

lsandov1@ubuntu1704:~$ gpg --version
gpg (GnuPG) 2.1.15
libgcrypt 1.7.6-beta
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/lsandov1/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
Comment 5 oscar lopez arandas 2017-09-26 17:37:00 UTC
> Oscar, lets use the keys defined on meta-selftest. Can you please run the
> same manual test with this command:
> 
> $ mkdir /tmp/oeqa-signing-oscar $ or some folder which is unique on /tmp
> $ gpg --batch --homedir /tmp/oeqa-signing-oscar --import <path to poky
> morty>/meta-selftest/files/signing/key.pub /<path to poky
> morty>/meta-selftest/files/signing/key.secret
> 
> I have tested the above command on a ubuntu 1704 box and I have no issues.
> This the gnupg version I used:
> 
> lsandov1@ubuntu1704:~$ gpg --version
> gpg (GnuPG) 2.1.15
> libgcrypt 1.7.6-beta
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <https://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> Home: /home/lsandov1/.gnupg
> Supported algorithms:
> Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
> Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
>         CAMELLIA128, CAMELLIA192, CAMELLIA256
> Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
> Compression: Uncompressed, ZIP, ZLIB, BZIP2

Leo,
I have tested the above command on a ubuntu 1604 box and I have no issues. This the gnupg version I used:

oscar@oscar:~$  gpg --version
gpg (GnuPG) 1.4.20
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
Comment 6 oscar lopez arandas 2017-11-29 20:54:12 UTC


is marked as duplicate the error already exists documented
bug 12022

*** This bug has been marked as a duplicate of bug 12022 ***