[jira] [Issue Comment Deleted] (TC-416) traffic_router: tomcat shutdown problems

[Jason Tucker (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TC-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Tucker updated TC-416:

Comment: was deleted

(was: PR: https://github.com/apache/incubator-trafficcontrol/pull/724)

> traffic_router: tomcat shutdown problems
> 
>
> Key: TC-416
> URL: https://issues.apache.org/jira/browse/TC-416
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Reporter: Jason Tucker
>  Labels: tomcat
>
> The tomcat init script has a few problems:
> 1. "Clean" shutdowns frequently timeout, and the scripts give up, leaving 
> tomcat running
> 2. Normal tomcat shutdown actually involves spinning up a second jvm 
> instance. Right now, we start this second instance with the same 
> CATALINA_OPTS as traffic_router, which can be problematic on 
> memory-constrained hosts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #724: [TC-416] tomcat init script fixe...

[guzzijason]

GitHub user guzzijason opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/724

[TC-416] tomcat init script fixes for traffic_router

Improving the reliabitiy of STOPPING tomcat service.

1. Add following variables to init script:
SHUTDOWN_TIMEOUT (default 10 seconds)
SHUTDOWN_FORCE (default "true" - kill if the shutdown times out)

2. Only export $CATALINA_OPTS when needed (to start the server)
Tomcat control scripts do this fun thing where to stop the current
jvm, catalina *starts* a second jvm, which then tells the first
to stop. This is all well and good, except we really don't want
to start this second jvm with our custom $CATALINA_OPTS, especially
on servers under memory pressure!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/guzzijason/incubator-trafficcontrol 
tomcat-init

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/724.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #724


commit 77d92d9ff0b60f0d372186f7c607de806e73ca19
Author: Jason Tucker 
Date:   2017-07-11T20:59:32Z

tomcat init script fixes for traffic_router

Improving the reliabitiy of STOPPING tomcat service.

1. Add following variables to init script:
SHUTDOWN_TIMEOUT (default 10 seconds)
SHUTDOWN_FORCE (default "true" - kill if the shutdown times out)

2. Only export $CATALINA_OPTS when needed (to start the server)
Tomcat control scripts do this fun thing where to stop the current
jvm, catalina *starts* a second jvm, which then tells the first
to stop. This is all well and good, except we really don't want
to start this second jvm with our custom $CATALINA_OPTS, especially
on servers under memory pressure!




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (TC-416) traffic_router: tomcat shutdown problems

[Jason Tucker (JIRA)]

Jason Tucker created TC-416:
---

 Summary: traffic_router: tomcat shutdown problems
 Key: TC-416
 URL: https://issues.apache.org/jira/browse/TC-416
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Router
Reporter: Jason Tucker


The tomcat init script has a few problems:

1. "Clean" shutdowns frequently timeout, and the scripts give up, leaving 
tomcat running

2. Normal tomcat shutdown actually involves spinning up a second jvm instance. 
Right now, we start this second instance with the same CATALINA_OPTS as 
traffic_router, which can be problematic on memory-constrained hosts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-416) traffic_router: tomcat shutdown problems

[Jason Tucker (JIRA)]

[ 
https://issues.apache.org/jira/browse/TC-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083031#comment-16083031
 ] 

Jason Tucker commented on TC-416:
-

PR: https://github.com/apache/incubator-trafficcontrol/pull/724

> traffic_router: tomcat shutdown problems
> 
>
> Key: TC-416
> URL: https://issues.apache.org/jira/browse/TC-416
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Reporter: Jason Tucker
>  Labels: tomcat
>
> The tomcat init script has a few problems:
> 1. "Clean" shutdowns frequently timeout, and the scripts give up, leaving 
> tomcat running
> 2. Normal tomcat shutdown actually involves spinning up a second jvm 
> instance. Right now, we start this second instance with the same 
> CATALINA_OPTS as traffic_router, which can be problematic on 
> memory-constrained hosts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-416) traffic_router: tomcat shutdown problems

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TC-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083029#comment-16083029
 ] 

ASF GitHub Bot commented on TC-416:
---

GitHub user guzzijason opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/724

[TC-416] tomcat init script fixes for traffic_router

Improving the reliabitiy of STOPPING tomcat service.

1. Add following variables to init script:
SHUTDOWN_TIMEOUT (default 10 seconds)
SHUTDOWN_FORCE (default "true" - kill if the shutdown times out)

2. Only export $CATALINA_OPTS when needed (to start the server)
Tomcat control scripts do this fun thing where to stop the current
jvm, catalina *starts* a second jvm, which then tells the first
to stop. This is all well and good, except we really don't want
to start this second jvm with our custom $CATALINA_OPTS, especially
on servers under memory pressure!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/guzzijason/incubator-trafficcontrol 
tomcat-init

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/724.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #724


commit 77d92d9ff0b60f0d372186f7c607de806e73ca19
Author: Jason Tucker 
Date:   2017-07-11T20:59:32Z

tomcat init script fixes for traffic_router

Improving the reliabitiy of STOPPING tomcat service.

1. Add following variables to init script:
SHUTDOWN_TIMEOUT (default 10 seconds)
SHUTDOWN_FORCE (default "true" - kill if the shutdown times out)

2. Only export $CATALINA_OPTS when needed (to start the server)
Tomcat control scripts do this fun thing where to stop the current
jvm, catalina *starts* a second jvm, which then tells the first
to stop. This is all well and good, except we really don't want
to start this second jvm with our custom $CATALINA_OPTS, especially
on servers under memory pressure!




> traffic_router: tomcat shutdown problems
> 
>
> Key: TC-416
> URL: https://issues.apache.org/jira/browse/TC-416
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Reporter: Jason Tucker
>  Labels: tomcat
>
> The tomcat init script has a few problems:
> 1. "Clean" shutdowns frequently timeout, and the scripts give up, leaving 
> tomcat running
> 2. Normal tomcat shutdown actually involves spinning up a second jvm 
> instance. Right now, we start this second instance with the same 
> CATALINA_OPTS as traffic_router, which can be problematic on 
> memory-constrained hosts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-64) Experimental SPA application

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TC-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082946#comment-16082946
 ] 

ASF GitHub Bot commented on TC-64:
--

GitHub user mitchell852 opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/723

[TC-64] - fixes steering targetname in TP



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
fixes-target-tp-ui

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/723.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #723


commit 37a85296c5690dbe76b53ef935419be08b0e216a
Author: Jeremy Mitchell 
Date:   2017-07-11T20:42:52Z

fixes targetname




> Experimental SPA application
> 
>
> Key: TC-64
> URL: https://issues.apache.org/jira/browse/TC-64
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: spa
>
> At the 2016 Traffic Control summit, a prototype of a SPA application 
> developed by [~mitchell...@apache.org] using AngularJS was demo'd that works 
> entirely on top of the TO API.
> This issue is a placeholder for any work done to this prototype / 
> experimental UI. The goal is to replicate the functionality of the current 
> MVC TO UI. nothing more, nothing less.
> This will require some additions to the TO API. look for issues regarding 
> each API addition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Jenkins build is back to normal : incubator-trafficcontrol-traffic_ops-test #7

[Apache Jenkins Server]

See 

[jira] [Commented] (TC-64) Experimental SPA application

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TC-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082923#comment-16082923
 ] 

ASF GitHub Bot commented on TC-64:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/722


> Experimental SPA application
> 
>
> Key: TC-64
> URL: https://issues.apache.org/jira/browse/TC-64
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: spa
>
> At the 2016 Traffic Control summit, a prototype of a SPA application 
> developed by [~mitchell...@apache.org] using AngularJS was demo'd that works 
> entirely on top of the TO API.
> This issue is a placeholder for any work done to this prototype / 
> experimental UI. The goal is to replicate the functionality of the current 
> MVC TO UI. nothing more, nothing less.
> This will require some additions to the TO API. look for issues regarding 
> each API addition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #722: [TC-64] - fixes tp release info ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/722


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #705: [TC-402] - ds xml_id is not editable

[dangogh]

Github user dangogh commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/705
  
isn't this to make xml_id read-only?  title confused me..

and there are conflicts now..



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-402) xml_id should not be changed after initial Delivery Service Creation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TC-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082898#comment-16082898
 ] 

ASF GitHub Bot commented on TC-402:
---

Github user dangogh commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/705
  
isn't this to make xml_id read-only?  title confused me..

and there are conflicts now..



> xml_id should not be changed after initial Delivery Service Creation
> 
>
> Key: TC-402
> URL: https://issues.apache.org/jira/browse/TC-402
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Dewayne Richardson
>Assignee: Jeremy Mitchell
>
> Traffic Ops cannot handle changing the xml_id because the parameters for the 
> ATS config files use the xml_id by naming convention.
> Easy fix, just disable the 'xml_id' field for "Edit/Updates"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #721: fix use of hash as reference err...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/721


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (TC-414) TO unit tests run in docker

[Dan Kirkwood (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TC-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Kirkwood resolved TC-414.
-
Resolution: Fixed

merged to master,   testing in Apache Jenkins environment:

https://builds.apache.org/view/S-Z/view/TrafficControl/job/incubator-trafficcontrol-traffic_ops-test/

> TO unit tests run in docker
> ---
>
> Key: TC-414
> URL: https://issues.apache.org/jira/browse/TC-414
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 2.1.0
>
>
> To enable running traffic ops unit tests in a CI environment (i.e. Jenkins),  
> prepare a docker container environment that can be stood up automatically 
> with a clean database and prepare a report with pass/fail information



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-64) Experimental SPA application

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TC-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082660#comment-16082660
 ] 

ASF GitHub Bot commented on TC-64:
--

GitHub user mitchell852 opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/722

[TC-64] - fixes tp release info dialog



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-64-fixes-release-info

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/722.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #722


commit 19994680af58d12d92e061f55ef740bb5c0ae47f
Author: Jeremy Mitchell 
Date:   2017-07-11T18:01:07Z

fixes tp release info dialog




> Experimental SPA application
> 
>
> Key: TC-64
> URL: https://issues.apache.org/jira/browse/TC-64
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: spa
>
> At the 2016 Traffic Control summit, a prototype of a SPA application 
> developed by [~mitchell...@apache.org] using AngularJS was demo'd that works 
> entirely on top of the TO API.
> This issue is a placeholder for any work done to this prototype / 
> experimental UI. The goal is to replicate the functionality of the current 
> MVC TO UI. nothing more, nothing less.
> This will require some additions to the TO API. look for issues regarding 
> each API addition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #722: [TC-64] - fixes tp release info ...

[mitchell852]

GitHub user mitchell852 opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/722

[TC-64] - fixes tp release info dialog



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-64-fixes-release-info

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/722.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #722


commit 19994680af58d12d92e061f55ef740bb5c0ae47f
Author: Jeremy Mitchell 
Date:   2017-07-11T18:01:07Z

fixes tp release info dialog




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #721: fix use of hash as reference err...

[DylanVolz]

GitHub user DylanVolz opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/721

fix use of hash as reference error in email blacklist lookup



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/DylanVolz/incubator-trafficcontrol 
fix-validation-bug

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/721.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #721






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #720: fix steering target foreign cons...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/720


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #675: custom or no headers for take an...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/675


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #684: [WIP] Adds cachekey plugin suppo...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/684


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (TC-415) traffic_ops unit test fails: api/1.1/deliveryservice/ssl_keys.t

[Dan Kirkwood (JIRA)]

Dan Kirkwood created TC-415:
---

 Summary: traffic_ops unit test fails: 
api/1.1/deliveryservice/ssl_keys.t
 Key: TC-415
 URL: https://issues.apache.org/jira/browse/TC-415
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops
Affects Versions: 2.1.0
Reporter: Dan Kirkwood
 Fix For: 2.1.0


This test script is showing 2 failures:  api/1.1/deliveryservice/ssl_keys.t

It's unknown when this started,  since unit tests haven't been watched for a 
while.   Console log from Apache Jenkins (current build log is 
https://builds.apache.org/view/S-Z/view/TrafficControl/job/incubator-trafficcontrol-traffic_ops-test/3/consoleFull)
 shows the error: 

{quote}
unit_1  | writing RSA key
unit_1  | Signature ok
unit_1  | 
subject=/C=US/ST=Colorado/L=Denver/O=KableTown/OU=CDN_Eng/CN=foober.com
unit_1  | Getting Private key
unit_1  | DBIx::Class::Storage::DBI::select_single(): Query returned more than 
one row.  SQL that returns multiple rows is DEPRECATED for ->find and ->single 
at /opt/traffic_ops/app/lib/API/DeliveryService/SslKeys.pm line 159
unit_1  | Use of uninitialized value $host_regex in concatenation (.) or string 
at /opt/traffic_ops/app/lib/API/DeliveryService/SslKeys.pm line 151.
unit_1  | Use of uninitialized value $cdn_id in string at 
/opt/traffic_ops/app/lib/API/DeliveryService/SslKeys.pm line 159.
db_1| ERROR:  invalid input syntax for integer: ""
db_1| STATEMENT:  SELECT me.id, me.xml_id, me.active, me.dscp, me.signed, 
me.qstring_ignore, me.geo_limit, me.http_bypass_fqdn, me.dns_bypass_ip, 
me.dns_bypass_ip6, me.dns_bypass_ttl, me.org_server_fqdn, me.type, me.profile, 
me.cdn_id, me.ccr_dns_ttl, me.global_max_mbps, me.global_max_tps, me.long_desc, 
me.long_desc_1, me.long_desc_2, me.max_dns_answers, me.info_url, me.miss_lat, 
me.miss_long, me.check_path, me.last_updated, me.protocol, me.ssl_key_version, 
me.ipv6_routing_enabled, me.range_request_handling, me.edge_header_rewrite, 
me.origin_shield, me.mid_header_rewrite, me.regex_remap, me.cacheurl, 
me.remap_text, me.multi_site_origin, me.display_name, me.tr_response_headers, 
me.initial_dispersion, me.dns_bypass_cname, me.tr_request_headers, 
me.regional_geo_blocking, me.geo_provider, me.geo_limit_countries, 
me.logs_enabled, me.multi_site_origin_algorithm, me.geolimit_redirect_url, 
me.tenant_id FROM deliveryservice me LEFT JOIN deliveryservice_regex 
deliveryservice_regexes ON deliveryservice_regexes.deliveryservice = me.id LEFT 
JOIN regex regex ON regex.id = deliveryservice_regexes.regex WHERE ( ( cdn_id = 
$1 AND regex.pattern = $2 ) )
unit_1  | Warning: Log message argument #1 undefined at 
/opt/traffic_ops/app/local/lib/perl5/Mojolicious.pm line 199.
unit_1  | Use of uninitialized value in join or string at 
/opt/traffic_ops/app/local/lib/perl5/Log/Log4perl/Appender.pm line 182.
unit_1  | 
unit_1  | #   Failed test '400 Bad Request'
unit_1  | #   at /opt/traffic_ops/app/t/api/1.1/deliveryservice/ssl_keys.t line 
208.
unit_1  | #  got: '500'
unit_1  | # expected: '400'
unit_1  | Use of uninitialized value $cdn_id in string at 
/opt/traffic_ops/app/lib/API/DeliveryService/SslKeys.pm line 159.
db_1| ERROR:  invalid input syntax for integer: ""
db_1| STATEMENT:  SELECT me.id, me.xml_id, me.active, me.dscp, me.signed, 
me.qstring_ignore, me.geo_limit, me.http_bypass_fqdn, me.dns_bypass_ip, 
me.dns_bypass_ip6, me.dns_bypass_ttl, me.org_server_fqdn, me.type, me.profile, 
me.cdn_id, me.ccr_dns_ttl, me.global_max_mbps, me.global_max_tps, me.long_desc, 
me.long_desc_1, me.long_desc_2, me.max_dns_answers, me.info_url, me.miss_lat, 
me.miss_long, me.check_path, me.last_updated, me.protocol, me.ssl_key_version, 
me.ipv6_routing_enabled, me.range_request_handling, me.edge_header_rewrite, 
me.origin_shield, me.mid_header_rewrite, me.regex_remap, me.cacheurl, 
me.remap_text, me.multi_site_origin, me.display_name, me.tr_response_headers, 
me.initial_dispersion, me.dns_bypass_cname, me.tr_request_headers, 
me.regional_geo_blocking, me.geo_provider, me.geo_limit_countries, 
me.logs_enabled, me.multi_site_origin_algorithm, me.geolimit_redirect_url, 
me.tenant_id FROM deliveryservice me LEFT JOIN deliveryservice_regex 
deliveryservice_regexes ON deliveryservice_regexes.deliveryservice = me.id LEFT 
JOIN regex regex ON regex.id = deliveryservice_regexes.regex WHERE ( ( cdn_id = 
$1 AND regex.pattern = $2 ) )
unit_1  | Warning: Log message argument #1 undefined at 
/opt/traffic_ops/app/local/lib/perl5/Mojolicious.pm line 199.
unit_1  | Use of uninitialized value in join or string at 
/opt/traffic_ops/app/local/lib/perl5/Log/Log4perl/Appender.pm line 182.
unit_1  | 
unit_1  | #   Failed test '400 Bad Request'
unit_1  | #   at /opt/traffic_ops/app/t/api/1.1/deliveryservice/ssl_keys.t line 
212.
unit_1  | #  got: '500'
unit_1  | # expected: '400'
unit_1  | Generating a 2048 bit RSA private 

[GitHub] incubator-trafficcontrol pull request #720: fix steering target foreign cons...

[dg4prez]

GitHub user dg4prez opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/720

fix steering target foreign constraints

Fixes incorrect constraints in steering_target.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dg4prez/incubator-trafficcontrol schema_fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/720.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #720


commit 4a744af304d0da3a21d121a0052dee78e357b977
Author: Derek Gelinas 
Date:   2017-07-11T16:00:30Z

fix steering fc

commit 0757c99ed662b0d83e145c034610c60f031f76e5
Author: Derek Gelinas 
Date:   2017-07-11T16:11:19Z

add migration




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Build failed in Jenkins: incubator-trafficcontrol-traffic_ops-test #1

[Apache Jenkins Server]

See 


--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-6 (ubuntu trusty) in workspace 

Cloning the remote Git repository
Cloning repository git://git.apache.org/incubator-trafficcontrol.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from git://git.apache.org/incubator-trafficcontrol.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > git://git.apache.org/incubator-trafficcontrol.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > git://git.apache.org/incubator-trafficcontrol.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > git://git.apache.org/incubator-trafficcontrol.git # timeout=10
Fetching upstream changes from git://git.apache.org/incubator-trafficcontrol.git
 > git fetch --tags --progress 
 > git://git.apache.org/incubator-trafficcontrol.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 13b701af9aa9aefc43f126f3119f9789d42e9f6c 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 13b701af9aa9aefc43f126f3119f9789d42e9f6c
First time build. Skipping changelog.
[incubator-trafficcontrol-traffic_ops-test] $ /bin/bash 
/tmp/hudson6835242131215884563.sh
+ proj=jenkins-incubator-trafficcontrol-traffic_ops-test-1
++ pwd
+ 
compose=
+ [[ ! -x 

 ]]
+ mkdir bin
++ uname -s
++ uname -m
+ curl -L 
https://github.com/docker/compose/releases/download/1.13.0/docker-compose-Linux-x86_64
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0100 
  6170   6170 0   4206  0 --:--:-- --:--:-- --:--:--  4197
  5 8079k5  458k0 0   412k  0  0:00:19  0:00:01  0:00:18  412k 
53 8079k   53 4299k0 0  2064k  0  0:00:03  0:00:02  0:00:01 
3947k100 8079k  100 8079k0 0  3312k  0  0:00:02  0:00:02 --:--:-- 
5738k
+ chmod +x 

+ docker version
Client:
 Version:  1.12.6
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   78d1802
 Built:Tue Jan 10 20:26:30 2017
 OS/Arch:  linux/amd64

Server:
 Version:  1.12.6
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   78d1802
 Built:Tue Jan 10 20:26:30 2017
 OS/Arch:  linux/amd64
+ 

 -p jenkins-incubator-trafficcontrol-traffic_ops-test-1 -f '' down -v
.IOError: [Errno 21] Is a directory: u'./'
+ 

 -p jenkins-incubator-trafficcontrol-traffic_ops-test-1 -f '' up --build
.IOError: [Errno 21] Is a directory: u'./'
+ docker ps -a
+ grep traffic
+ docker images
+ grep traffic
+ 

 -p jenkins-incubator-trafficcontrol-traffic_ops-test-1 -f '' down -v
.IOError: [Errno 21] Is a directory: u'./'
Build step 'Execute shell' marked build as failure
Archiving artifacts

Build failed in Jenkins: incubator-trafficcontrol-traffic_ops-test #2

[Apache Jenkins Server]

See 


--
Started by user dangogh
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-6 (ubuntu trusty) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > git://git.apache.org/incubator-trafficcontrol.git # timeout=10
Fetching upstream changes from git://git.apache.org/incubator-trafficcontrol.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > git://git.apache.org/incubator-trafficcontrol.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 13b701af9aa9aefc43f126f3119f9789d42e9f6c 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 13b701af9aa9aefc43f126f3119f9789d42e9f6c
 > git rev-list 13b701af9aa9aefc43f126f3119f9789d42e9f6c # timeout=10
[incubator-trafficcontrol-traffic_ops-test] $ /bin/bash 
/tmp/hudson3555914288129006532.sh
+ proj=jenkins-incubator-trafficcontrol-traffic_ops-test-2
++ pwd
+ 
compose=
+ [[ ! -x 

 ]]
+ docker version
Client:
 Version:  1.12.6
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   78d1802
 Built:Tue Jan 10 20:26:30 2017
 OS/Arch:  linux/amd64

Server:
 Version:  1.12.6
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   78d1802
 Built:Tue Jan 10 20:26:30 2017
 OS/Arch:  linux/amd64
+ 

 -p jenkins-incubator-trafficcontrol-traffic_ops-test-2 -f '' down -v
.IOError: [Errno 21] Is a directory: u'./'
+ 

 -p jenkins-incubator-trafficcontrol-traffic_ops-test-2 -f '' up --build
.IOError: [Errno 21] Is a directory: u'./'
+ docker ps -a
+ grep traffic
+ docker images
+ grep traffic
+ 

 -p jenkins-incubator-trafficcontrol-traffic_ops-test-2 -f '' down -v
.IOError: [Errno 21] Is a directory: u'./'
Build step 'Execute shell' marked build as failure

[GitHub] incubator-trafficcontrol pull request #719: [TC-64] - hooks steering targets...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/719


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-64) Experimental SPA application

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TC-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082363#comment-16082363
 ] 

ASF GitHub Bot commented on TC-64:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/719


> Experimental SPA application
> 
>
> Key: TC-64
> URL: https://issues.apache.org/jira/browse/TC-64
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: spa
>
> At the 2016 Traffic Control summit, a prototype of a SPA application 
> developed by [~mitchell...@apache.org] using AngularJS was demo'd that works 
> entirely on top of the TO API.
> This issue is a placeholder for any work done to this prototype / 
> experimental UI. The goal is to replicate the functionality of the current 
> MVC TO UI. nothing more, nothing less.
> This will require some additions to the TO API. look for issues regarding 
> each API addition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)