Rebuild command: x86_64 rpmbuild --rebuild   --define "dist .el8"  --define '_topdir /usr/src/redhat' --target=x86_64 --rcfile /tmp/tps_rpmrc_kKvtd0:/usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc /mnt/redhat/brewroot/vol/rhel-8/packages/openresty/1.19.3/22.el8/data/signed/fd431d51/src/openresty-1.19.3-22.el8.src.rpm
doRpmCommand: x86_64 rpmbuild --rebuild   --define "dist .el8"  --define '_topdir /usr/src/redhat' --target=x86_64 --rcfile /tmp/tps_rpmrc_kKvtd0:/usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc /mnt/redhat/brewroot/vol/rhel-8/packages/openresty/1.19.3/22.el8/data/signed/fd431d51/src/openresty-1.19.3-22.el8.src.rpm &> openresty-1.19.3-22.el8.src.rpm-x86_64-rebuild.log
doRpmCommand-result (0): 
REBUILD: success, please see openresty-1.19.3-22.el8.src.rpm-x86_64-rebuild.log.gz for details.
List of Built Packages:
/usr/src/redhat/RPMS/x86_64/openresty-1.19.3-22.el8.x86_64.rpm
/usr/src/redhat/RPMS/noarch/openresty-resty-1.19.3-22.el8.noarch.rpm
/usr/src/redhat/RPMS/noarch/openresty-opm-1.19.3-22.el8.noarch.rpm
/usr/src/redhat/RPMS/x86_64/openresty-opentracing-1.19.3-22.el8.x86_64.rpm
/usr/src/redhat/RPMS/x86_64/openresty-opentelemetry-1.19.3-22.el8.x86_64.rpm
/usr/src/redhat/RPMS/x86_64/openresty-debugsource-1.19.3-22.el8.x86_64.rpm
/usr/src/redhat/RPMS/x86_64/openresty-debuginfo-1.19.3-22.el8.x86_64.rpm
/usr/src/redhat/RPMS/x86_64/openresty-opentracing-debuginfo-1.19.3-22.el8.x86_64.rpm
/usr/src/redhat/RPMS/x86_64/openresty-opentelemetry-debuginfo-1.19.3-22.el8.x86_64.rpm
TPSERROR: openresty-opentelemetry-1.19.3-22.el8.x86_64.rpm was built by openresty-1.19.3-22.el8.src.rpm but not included in the file list
Please check previously released packages to ensure the file list
is sane.  It is possible that the new-files list is incomplete,
perhaps due to some problem with Release Engineering's ComposeDB, or perhaps due to a new subpackage.  In
that case, please file a ticket with Release Engineering.  See http://tps-server.lab.bos.redhat.com/wiki/Tickets
for contact information.  After RelEng makes the update, reload the filelist for the affected brew build.
In some cases, the subpackages built from a source RPM are split and
shipped in multiple repos/products. Check active errata for the package in question. If you find the missing
subpackage in the file list of another active erratum, you can waive this failure. You may also want to
test the two errata together, potentially using the Depends On feature. It won't help prevent the rebuild
test failure, but may help the RPM tests succeed.
It is also possible that the .spec file is consuming time and
resources by building something we do not intend to ship; in this
case, file a bug against the package to correct that behavior.
/mnt/redhat/released, tps-check-channels, RHN, and previous
advisories are all sources of information about previously released
packages.