zrhoffman opened a new issue, #7006:
URL: https://github.com/apache/trafficcontrol/issues/7006

   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! 
Instead, contact
   the Apache Traffic Control Security Team at 
[email protected] and follow the
   guidelines at https://apache.org/security regarding vulnerability disclosure.
   
   - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack 
(https://s.apache.org/tc-slack-request)
   or the Traffic Control Users mailing list (send an email to 
[email protected] to subscribe).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
       * https://github.com/apache/trafficcontrol/issues
       * https://github.com/apache/trafficcontrol/pulls
   -->
   
   <!-- Do not submit security vulnerabilities or support requests here - see 
above -->
   ## This Bug Report affects these Traffic Control components:
   <!-- delete all those that don't apply -->
   - Traffic Control Cache Config (`t3c`, formerly ORT) - Traffic Server RPM 
used by integration tests
   
   ## Current behavior:
   <!-- Describe how the bug happens -->
   Building ATS 9.1.x using the ATS build configuration in 
`cache-config/testing/docker/trafficserver` fails:
   ```shell
   [...]
   *** WARNING: ./opt/trafficserver/libexec/trafficserver/fq_pacing.la is 
executable but has no shebang, removing executable bit
   *** WARNING: ./opt/trafficserver/libexec/trafficserver/cache_promote.la is 
executable but has no shebang, removing executable bit
   mangling shebang in /opt/trafficserver/bin/tspush from /usr/bin/env perl to 
#!/usr/bin/perl
   mangling shebang in /opt/trafficserver/bin/tsxs from /usr/bin/env bash to 
#!/usr/bin/bash
   Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.kOSn32
   Skipping Trafficserver Unit tests
   + umask 022
   + cd /root/rpmbuild/BUILD
   + cd trafficserver-9.1.2
   + echo 'Skipping Trafficserver Unit tests'
   + exit 0
   Processing files: trafficserver-9.1.2-26.281416ad9.el8.x86_64
   error: File not found: 
/root/rpmbuild/BUILDROOT/trafficserver-9.1.2-26.281416ad9.el8.x86_64/opt/trafficserver/etc/trafficserver/ip_allow.config
   error: File not found: 
/root/rpmbuild/BUILDROOT/trafficserver-9.1.2-26.281416ad9.el8.x86_64/opt/trafficserver/etc/trafficserver/ssl_server_name.yaml
   Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.wmYnVO
   + umask 022
   + cd /root/rpmbuild/BUILD
   + cd trafficserver-9.1.2
   + 
LICENSEDIR=/root/rpmbuild/BUILDROOT/trafficserver-9.1.2-26.281416ad9.el8.x86_64/usr/share/licenses/trafficserver
   + export LC_ALL=C
   + LC_ALL=C
   + export LICENSEDIR
   + /usr/bin/mkdir -p 
/root/rpmbuild/BUILDROOT/trafficserver-9.1.2-26.281416ad9.el8.x86_64/usr/share/licenses/trafficserver
   + cp -pr LICENSE 
/root/rpmbuild/BUILDROOT/trafficserver-9.1.2-26.281416ad9.el8.x86_64/usr/share/licenses/trafficserver
   + exit 0
       File not found: 
/root/rpmbuild/BUILDROOT/trafficserver-9.1.2-26.281416ad9.el8.x86_64/opt/trafficserver/etc/trafficserver/ip_allow.config
       File not found: 
/root/rpmbuild/BUILDROOT/trafficserver-9.1.2-26.281416ad9.el8.x86_64/opt/trafficserver/etc/trafficserver/ssl_server_name.yaml
   
   
   RPM build errors:
   Failed to build the ATS RPM.
   docker-trafficserver_build-1 exited with code 1
   ```
   ([full 
log](https://github.com/apache/trafficcontrol/files/9262595/ats-9.log))
   
   ## Expected behavior:
   <!-- Describe what the behavior would be without the bug -->
   Building an ATS 9.1.x RPM should succeed
   
   ## Steps to reproduce:
   <!-- If the current behavior is a bug, please provide the *STEPS TO 
REPRODUCE* and
   include the applicable TC version.
   
   -->
   ```shell
   cd cache-config/testing/docker
   sed -Ei 's/^(ATS_VERSION=).*/\19.1.x/' variables.env
   docker-compose -f docker-compose-ats-build.yml up
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to