<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>12609</bug_id>
          
          <creation_ts>2018-03-16 17:19:29 +0000</creation_ts>
          <short_desc>dnf failures during testing on Fedora 27</short_desc>
          <delta_ts>2018-03-20 02:31:17 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>2.5</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WORKSFORME</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Undecided</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="California Sullivan">california.l.sullivan</reporter>
          <assigned_to name="Alexander Kanavin">alex.kanavin</assigned_to>
          <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>79843</commentid>
    <comment_count>0</comment_count>
    <who name="California Sullivan">california.l.sullivan</who>
    <bug_when>2018-03-16 17:19:29 +0000</bug_when>
    <thetext>A couple different builds had failing tests all involving dnf on the new Fedora 27 builder:

Pyro-next: https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/871/steps/Running%20Sanity%20Tests_7/logs/stdio

---
Command: dnf --repofrompath=oe-testimage-repo-noarch,http://192.168.7.1:46709/noarch --repofrompath=oe-testimage-repo-qemux86_64,http://192.168.7.1:46709/qemux86_64 --repofrompath=oe-testimage-repo-core2_64,http://192.168.7.1:46709/core2_64 --nogpgcheck install -y http://192.168.7.1:46709/noarch/run-postinsts-dev-1.0-r9.noarch.rpm
...
Failed:
  run-postinsts.noarch 1.0-r9          run-postinsts-dev.noarch 1.0-r9         

Error: Transaction failed
---


Rocko-next: https://autobuilder.yocto.io/builders/nightly-musl-x86-64/builds/336/steps/Running%20Sanity%20Tests/logs/stdio

---
NOTE: core-image-sato-sdk-1.0-r0 do_testimage: test_dnf_install_dependency (dnf.DnfRepoTest)
NOTE: core-image-sato-sdk-1.0-r0 do_testimage:  ... FAIL
---
NOTE: core-image-sato-sdk-1.0-r0 do_testimage: test_dnf_reinstall (dnf.DnfRepoTest)
NOTE: core-image-sato-sdk-1.0-r0 do_testimage:  ... FAIL
---
| DEBUG: [Running]$ ssh -l root -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=ERROR 192.168.7.6 export PATH=/usr/sbin:/sbin:/usr/bin:/bin; dnf --repofrompath=oe-testimage-repo-noarch,http://192.168.7.5:41915/noarch --repofrompath=oe-testimage-repo-qemux86_64,http://192.168.7.5:41915/qemux86_64 --repofrompath=oe-testimage-repo-core2_64,http://192.168.7.5:41915/core2_64 --nogpgcheck install -y run-postinsts-dev
...
| No package run-postinsts-dev available.
| Error: Unable to find a match
| 
| NOTE:  ... FAIL</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79844</commentid>
    <comment_count>1</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2018-03-17 02:05:45 +0000</bug_when>
    <thetext>Could it be running the host dnf somehow?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79849</commentid>
    <comment_count>2</comment_count>
    <who name="Alexander Kanavin">alex.kanavin</who>
    <bug_when>2018-03-19 04:36:36 +0000</bug_when>
    <thetext>The tests are running dnf on the target image against a repository served by a host, so I don&apos;t think host dnf is involved. The rocko-next failing test seems to have network connectivity issues:

Added oe-testimage-repo-core2_64 repo from http://192.168.7.5:41915/core2_64
| Added oe-testimage-repo-qemux86_64 repo from http://192.168.7.5:41915/qemux86_64
| Added oe-testimage-repo-noarch repo from http://192.168.7.5:41915/noarch
| Failed to synchronize cache for repo &apos;oe-testimage-repo-core2_64&apos;, disabling.
| Failed to synchronize cache for repo &apos;oe-testimage-repo-qemux86_64&apos;, disabling.
| Failed to synchronize cache for repo &apos;oe-testimage-repo-noarch&apos;, disabling.


The pyro-next is installing and deinstalling a couple of packages in various ways, until it mysteriously fails:

Running transaction
  Installing  : run-postinsts-1.0-r9.noarch                                 1/2Created symlink /etc/systemd/system/sysinit.target.wants/run-postinsts.service \u2192 /lib/systemd/system/run-postinsts.service.
 
  Installing  : run-postinsts-dev-1.0-r9.noarch                             2/2run-postinsts-dev-1.0-r9.noarch was supposed to be installed but is not!
 
  Verifying   : run-postinsts-dev-1.0-r9.noarch                             1/2run-postinsts-1.0-r9.noarch was supposed to be installed but is not!
 
  Verifying   : run-postinsts-1.0-r9.noarch                                 2/2 

Failed:
  run-postinsts.noarch 1.0-r9          run-postinsts-dev.noarch 1.0-r9         

Error: Transaction failed


We need to narrow this down a bit, but I&apos;m not sure how yet.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79850</commentid>
    <comment_count>3</comment_count>
    <who name="Alexander Kanavin">alex.kanavin</who>
    <bug_when>2018-03-19 04:45:23 +0000</bug_when>
    <thetext>Especially puzzling is that pyro-next ran the same test several times, and only the last run (involving systemd) is failing:
https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/871/

In either case, I doubt it&apos;s F27&apos;s fault.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79853</commentid>
    <comment_count>4</comment_count>
    <who name="Alexander Kanavin">alex.kanavin</who>
    <bug_when>2018-03-19 09:21:34 +0000</bug_when>
    <thetext>In any case, if you see this again, do let me know, as I&apos;d appreciate narrowing this down. Trying to reproduce locally now, on a debian testing host.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79854</commentid>
    <comment_count>5</comment_count>
    <who name="Alexander Kanavin">alex.kanavin</who>
    <bug_when>2018-03-19 10:00:41 +0000</bug_when>
    <thetext>rocko-next worked flawlessly (musl, running testimage for three images in parallel). Will try pyro-next next.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79864</commentid>
    <comment_count>6</comment_count>
    <who name="Alexander Kanavin">alex.kanavin</who>
    <bug_when>2018-03-20 02:31:17 +0000</bug_when>
    <thetext>pyro-next works fine as well (with systemd enabled etc.)

So I&apos;m out of ideas at this point, and don&apos;t know what else to try. It&apos;s possible we&apos;re hitting some weird resource limit in F27 (especially if the issue occurs in random places), but without a way to reproduce there&apos;s nothing to be done. If you see this again, please do re-open.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>