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


   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! 
Instead, contact
   the Apache Software Foundation Security Team at 
[email protected] and follow the
   guidelines at https://www.apache.org/security/ regarding vulnerability 
disclosure.
   -->
   
   <!--
   - For *SUPPORT QUESTIONS*, use the
   [Traffic Control slack channels](https://traffic-control-cdn.slack.com) or 
[Traffic Control mailing 
lists](http://trafficcontrol.apache.org/mailing_lists/).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR. -->
   
   ## I'm submitting a ...
   <!-- (check all that apply with "[x]") -->
   <!--- security vulnerability (STOP!! - see above)-->
   - [x] bug report
   - [ ] new feature / enhancement request
   - [ ] improvement request (usability, performance, tech debt, etc.)
   - [ ] other <!--(Please do not submit support requests here - see above)-->
   
   ## Traffic Control components affected ...
   <!-- (check all that apply with "[x]") -->
   - [ ] CDN in a Box
   - [ ] Documentation
   - [ ] Grove
   - [ ] Traffic Control Client
   - [ ] Traffic Monitor
   - [x] Traffic Ops
   - [ ] Traffic Ops ORT
   - [ ] Traffic Portal
   - [ ] Traffic Router
   - [ ] Traffic Stats
   - [ ] Traffic Vault
   - [ ] unknown
   
   ## Current behavior:
   <!-- Describe how the bug manifests / how the current features are 
insufficient. -->
   Cachegroup parameters API tests fail at fd838becca
   
   ## Expected / new behavior:
   <!-- Describe what the behavior would be without the bug / how the feature 
would improve Traffic Control -->
   Cachegroup parameters API tests should succeed
   
   ## Minimal reproduction of the problem with instructions:
   <!--
   If the current behavior is a bug or you can illustrate your feature request 
better with an example,
   please provide the *STEPS TO REPRODUCE* and include the applicable TC 
version.
   -->
   1. Start CDN-in-a-Box with exposed ports and wait Traffic Ops Perl to finish 
seeding the database
       ```shell script
       docker-compose -f docker-compose.yml -f docker-compose.expose-ports.yml 
up -d
       docker-compose -f docker-compose.yml -f docker-compose.expose-ports.yml 
logs -f trafficops-perl
       ```
   
   1. Configure `traffic_ops/testing/api/conf/traffic-ops-test.conf` for 
CDN-in-a-Box
       ```json
       {
           "default": {
               "logLocations": {
                   "debug": "stdout",
                   "error": "stdout",
                   "event": "stdout",
                   "info": "stdout",
                   "warning": "stdout"
               },
               "session": {
                   "timeoutInSecs": 60
               },
               "includeSystemTests": false
           },
           "use_ims": true,
           "trafficOps": {
               "URL": "https://localhost:6443";,
               "password": "twelve",
               "users": {
                   "disallowed": "disallowed",
                   "operations": "operations",
                   "admin": "admin",
                   "federation": "federation",
                   "portal": "portal",
                   "readOnly": "readOnly",
                   "extension": "extension"
               }
           },
           "trafficOpsDB": {
               "dbname": "traffic_ops",
               "description": "Test database traffic_ops",
               "hostname": "localhost",
               "password": "twelve",
               "port": "5432",
               "type": "Pg",
               "user": "traffic_ops"
           }
       }
       ```
   
   1. Run the cachegroup parameters API tests
       ```shell script
       go test ./v3 -test.v -cfg=../conf/traffic-ops-test.conf 
-fixtures=tc-fixtures.json -test.run 'TestMain|TestCacheGroupParameters'
       ```
   
   ## Anything else:
   <!-- e.g. stacktraces, related issues, suggestions how to fix -->
   Cachegroup API tests log:
   ```
   INFO: traffic_ops_test.go:71: 2020-06-30T14:10:46.528087208-06:00: Using 
Config values:
                           TO Config File:       ../conf/traffic-ops-test.conf
                           TO Fixtures:          tc-fixtures.json
                           TO URL:               https://localhost:6443
                           TO Session Timeout In Secs:  60
                           DB Server:            localhost
                           DB User:              traffic_ops
                           DB Name:              traffic_ops
                           DB Ssl:               false
                  UseIMS:               true
   === RUN   TestCacheGroupParameters
       TestCacheGroupParameters: types_test.go:87: ---- CreateTestTypes ----
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: parameters_test.go:75: Response:  {[{param was 
created. success}]}
       TestCacheGroupParameters: cachegroups_parameters_test.go:94: Expected 
304 status code, got 200
       TestCacheGroupParameters: types_test.go:187: ---- DeleteTestTypes ----
   --- FAIL: TestCacheGroupParameters (2.01s)
   FAIL
   FAIL github.com/apache/trafficcontrol/traffic_ops/testing/api/v3     2.560s
   FAIL
   ```
   
   <!--
   Licensed to the Apache Software Foundation (ASF) under one
   or more contributor license agreements.  See the NOTICE file
   distributed with this work for additional information
   regarding copyright ownership.  The ASF licenses this file
   to you under the Apache License, Version 2.0 (the
   "License"); you may not use this file except in compliance
   with the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing,
   software distributed under the License is distributed on an
   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
   under the License.
   -->


----------------------------------------------------------------
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.

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


Reply via email to