<?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>16504</bug_id>
          
          <creation_ts>2026-11-14 17:45:03 +0000</creation_ts>
          <short_desc>RRS: upgrade history hangs parsing OE-Core 3c00ad5d3b (OEEquivHash without BB_HASHSERVE)</short_desc>
          <delta_ts>2026-11-15 00:46:36 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Recipe Reporting System (RRS)</product>
          <component>Recipe Reporting System (RRS)</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>IN PROGRESS REVIEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>6.2 M2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Tim Orling">tim.orling</reporter>
          <assigned_to name="Tim Orling">tim.orling</assigned_to>
          
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>107449</commentid>
    <comment_count>0</comment_count>
    <who name="Tim Orling">tim.orling</who>
    <bug_when>2026-11-14 17:45:03 +0000</bug_when>
    <thetext>rrs_upgrade_history.py stalls indefinitely when it reaches OE-Core
commit 3c00ad5d3b (&quot;build-appliance-image: Update to master head
revisions&quot;, 2026-02-27).

OE-Core 5596ea156d (&quot;bitbake.conf: Switch BB_SIGNATURE_HANDLER to
OEEquivHash by default&quot;) changed the default signature handler, and
BB_HASHSERVE ??= &quot;auto&quot; was only added in the following commit,
4a388406ac (&quot;bitbake.conf: Set BB_HASHSERVE alongside
BB_SIGNATURE_HANDLER&quot;). 3c00ad5d3b is the only commit in between that
touches a recipe, so RRS parses it. Parsing it fails in
meta/lib/oe/sstatesig.py with:

  ERROR: OEEquivHash requires BB_HASHSERVE to be set

The error is raised in the BitBake server during tinfoil setup, and
the BitBake of that period (bc8be83aef) doesn&apos;t return it to the
client, so upgrade_history_internal.py never exits. run_internal()
ignores non-zero exits and would move on, but it has no timeout, so
the whole run stalls until it is killed. On layers.moto-timo.net it
sat idle for ~7.5 hours.

The layer index parse configuration (conf/local.conf) doesn&apos;t need
hash equivalence at all. Since 4a388406ac, OE-Core master also starts
a local hashserv for every layer index / RRS parse.

Proposed fix: set BB_SIGNATURE_HANDLER = &quot;OEBasicHash&quot; in
layerindex-web&apos;s conf/local.conf. This fixes the bad revision and
avoids the per-parse hashserv on current master.

Possible follow-up: add a per-commit timeout to run_internal() so any
future hang becomes a logged failure instead of stalling the run.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>107463</commentid>
    <comment_count>1</comment_count>
    <who name="Tim Orling">tim.orling</who>
    <bug_when>2026-11-15 00:46:36 +0000</bug_when>
    <thetext>Patch 5/6 of the series sent to yocto-patches, under review:
https://lore.kernel.org/all/20261115003506.53654-1-tim.orling@konsulko.com/</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>