You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Reserved consistentHashQueryParameters cause internal server error #6385
This Bug Report affects these Traffic Control components:
Traffic Ops
Current behavior:
Trying to update or create a Delivery Service to use a reserved query string parameter name like "trred" or "format" causes a 500 Internal Server Error response.
Expected behavior:
I'm almost certain the old behavior was more proper; the API should return a client-level error and accompanying Alert that tells the user they can't do what they're trying to do.
ok, I tried to build it with docker-compose 1.25.4 but the compose version 3.8 in YAML files only supported from version 1.25.5 https://github.com/docker/compose/releases/tag/1.25.5. adding it here on the hope it helps someone.
Also i am getting this error,
Step 10/35 : FROM common-traffic-server-dependencies AS common-cache-config-layers
---> f76f2258a217
Step 11/35 : COPY infrastructure/cdn-in-a-box/cache/trafficserver.rpm /trafficserver.rpm
COPY failed: file not found in build context or excluded by .dockerignore: stat infrastructure/cdn-in-a-box/cache/trafficserver.rpm: file does not exist
ERROR: Service 'edge' failed to build : Build failed
The RPM file is not found in given path infrastructure/cdn-in-a-box/cache/trafficserver.rpm.
Should it be built separately?
ok, I tried to build it with docker-compose 1.25.4 but the compose version 3.8 in YAML files only supported from version 1.25.5 https://github.com/docker/compose/releases/tag/1.25.5. adding it here on the hope it helps someone.
The Python version of docker-compose (versions < v2.0.0) is no longer supported. They rewrote docker-compose in Go.
Also i am getting this error, Step 10/35 : FROM common-traffic-server-dependencies AS common-cache-config-layers ---> f76f2258a217 Step 11/35 : COPY infrastructure/cdn-in-a-box/cache/trafficserver.rpm /trafficserver.rpm COPY failed: file not found in build context or excluded by .dockerignore: stat infrastructure/cdn-in-a-box/cache/trafficserver.rpm: file does not exist ERROR: Service 'edge' failed to build : Build failed
The RPM file is not found in given path infrastructure/cdn-in-a-box/cache/trafficserver.rpm. Should it be built separately?
All of the RPMs necessary to run CDN in a Box will be built and placed in the correct locations if you just run make from the infrastructure/cdn-in-a-box directory. From the documentation:
These can all be supplied manually via the steps in :ref:`dev-building` (for Traffic Control component RPMs) or via some external source. Alternatively, the :file:`infrastructure/cdn-in-a-box/Makefile` file contains recipes to build all of these - simply run :manpage:`make(1)` from the :file:`infrastructure/cdn-in-a-box/` directory. Once all RPM dependencies have been satisfied, run ``docker-compose build --parallel`` from the :file:`infrastructure/cdn-in-a-box/` directory to construct the images needed to run CDN in a Box.
make builds sequentially. I think about 80% of its time is spent on building the builder image for the ATS RPM (citation needed). make -j is marginally faster. When building on systems that use rpm to manage packages (which is LSB-compliant, to be fair) can build quite a bit faster with make native. The absolute fastest is make -j native, where supported. But at any rate, building once will expedite future builds.
make builds sequentially. I think about 80% of its time is spent on building the builder image for the ATS RPM (citation needed). make -j is marginally faster. When building on systems that use rpm to manage packages (which is LSB-compliant, to be fair) can build quite a bit faster with make native. The absolute fastest is make -j native, where supported. But at any rate, building once will expedite future builds.
make builds sequentially. I think about 80% of its time is spent on building the builder image for the ATS RPM (citation needed). make -j is marginally faster. When building on systems that use rpm to manage packages (which is LSB-compliant, to be fair) can build quite a bit faster with make native. The absolute fastest is make -j native, where supported. But at any rate, building once will expedite future builds.
Activity
asheikm commentedon Dec 14, 2021
Hi
Can this bug reproduced using cdn-in-box ?
ocket8888 commentedon Dec 14, 2021
yes, it's not dependent on environment
asheikm commentedon Dec 14, 2021
ok, I tried to build it with docker-compose 1.25.4 but the compose version 3.8 in YAML files only supported from version 1.25.5 https://github.com/docker/compose/releases/tag/1.25.5. adding it here on the hope it helps someone.
Also i am getting this error,
Step 10/35 : FROM common-traffic-server-dependencies AS common-cache-config-layers
---> f76f2258a217
Step 11/35 : COPY infrastructure/cdn-in-a-box/cache/trafficserver.rpm /trafficserver.rpm
COPY failed: file not found in build context or excluded by .dockerignore: stat infrastructure/cdn-in-a-box/cache/trafficserver.rpm: file does not exist
ERROR: Service 'edge' failed to build : Build failed
The RPM file is not found in given path infrastructure/cdn-in-a-box/cache/trafficserver.rpm.
Should it be built separately?
zrhoffman commentedon Dec 14, 2021
The Python version of docker-compose (versions < v2.0.0) is no longer supported. They rewrote docker-compose in Go.
All of the RPMs necessary to run CDN in a Box will be built and placed in the correct locations if you just run
makefrom theinfrastructure/cdn-in-a-boxdirectory. From the documentation:trafficcontrol/docs/source/admin/quick_howto/ciab.rst
Line 41 in e67c967
asheikm commentedon Dec 15, 2021
Ok, Thanks , It is building now, stragely, make takes lot of time, I am on VM OL8, which is taken as CentOS 8, thats fine anyway. It is still building
ocket8888 commentedon Dec 15, 2021
makebuilds sequentially. I think about 80% of its time is spent on building the builder image for the ATS RPM (citation needed).make -jis marginally faster. When building on systems that userpmto manage packages (which is LSB-compliant, to be fair) can build quite a bit faster withmake native. The absolute fastest ismake -j native, where supported. But at any rate, building once will expedite future builds.asheikm commentedon Dec 15, 2021
ok, I got it, now the cdn-in-a-box is running fine.
zrhoffman commentedon Dec 15, 2021
make nativeis temporarily broken due to #6419asheikm commentedon Dec 15, 2021
Fix merged with master now #6420
asheikm commentedon Dec 16, 2021
can we directly issue this command on cli ? or with curl ?
Edit: I got doc link, let me try curl with post request for this, in the mean time, how to use
topostif it is tool ? or is it alias ?ocket8888 commentedon Dec 16, 2021
topostis a utility provided by the Python client for Traffic Ops. It has an unofficial hosting on PyPI: https://pypi.org/project/Apache-TrafficControl/