[GitHub] incubator-trafficcontrol pull request #786: Fix TO ORT for missing Content-L...

[rob05c]

Github user rob05c commented on a diff in the pull request:


https://github.com/apache/incubator-trafficcontrol/pull/786#discussion_r132784235
  
--- Diff: traffic_ops/bin/traffic_ops_ort.pl ---
@@ -1623,9 +1623,7 @@ sub check_lwp_response_content_length {
my $url   = $lwp_response->request->uri;
 
if ( !defined($lwp_response->header('Content-Length')) ) {
-   ( $log_level >> $panic_level ) && print $log_level_str . " $url 
did not return a Content-Length header!\n";
-   exit;
-   return 1;
+   return 0; # Content-Length MAY be omitted per HTTP/1.1 RFC 
7230, and in fact MUST NOT be included with a 'Transfer-Encoding: Chunked' 
header, which MUST be accepted by clients.
--- End diff --

Agreed, something like CityHash would be better. But I don't want to deal 
with finding a Perl CityHash library. I'd vote Sha512 for now, and maybe switch 
to CityHash/Murmur/etc when TO is completely in Go.

On the other hand, for clients, it _is_ more convenient to have a more 
common hash like Sha or MD5, easier to find libraries.


---
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-230) Cache Health Monitor - Add IPv6 Checks

[ASF GitHub Bot (JIRA)]

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

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

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/695
  
This should also be linked to this issue: 
https://issues.apache.org/jira/browse/TC-230



> Cache Health Monitor - Add IPv6 Checks
> --
>
> Key: TC-230
> URL: https://issues.apache.org/jira/browse/TC-230
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Monitor, Traffic Monitor (golang)
>Reporter: Ryan Durfey
>  Labels: health_monitoring, ipv6
>
> We had access to several caches go down over IPv6 but not IPv4 due to a 
> routing issue.  Since the current health check only uses IPv4, these caches 
> were kept in rotation when they should have either been admin downed or at 
> least stopped advertising IPv6.
> We are looking for a health monitor check that detects issues on both IPv4 
> and IPv6.



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

[GitHub] incubator-trafficcontrol issue #695: TrafficMonitor IPV6 improvements

[dneuman64]

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/695
  
This should also be linked to this issue: 
https://issues.apache.org/jira/browse/TC-230



---
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 #695: TrafficMonitor IPV6 improvements

[dneuman64]

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/695
  
+1 to @alficles comments.  @serDrem can you please make this two PRs?  One 
for astats and one for TM?  


---
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 #786: Fix TO ORT for missing Content-L...

[alficles]

Github user alficles commented on a diff in the pull request:


https://github.com/apache/incubator-trafficcontrol/pull/786#discussion_r132782691
  
--- Diff: traffic_ops/bin/traffic_ops_ort.pl ---
@@ -1623,9 +1623,7 @@ sub check_lwp_response_content_length {
my $url   = $lwp_response->request->uri;
 
if ( !defined($lwp_response->header('Content-Length')) ) {
-   ( $log_level >> $panic_level ) && print $log_level_str . " $url 
did not return a Content-Length header!\n";
-   exit;
-   return 1;
+   return 0; # Content-Length MAY be omitted per HTTP/1.1 RFC 
7230, and in fact MUST NOT be included with a 'Transfer-Encoding: Chunked' 
header, which MUST be accepted by clients.
--- End diff --

Yup. That's great. Or any other fast hash. Security isn't a major issue 
here, so any reliable hash with low collisions will work.


---
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-511) migrations: Remove the reference to public table

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/47/



> migrations: Remove the reference to public table
> 
>
> Key: TC-511
> URL: https://issues.apache.org/jira/browse/TC-511
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
> Environment: Centos 7.3, Postgres 0.9.6
>Reporter: Steve Malenfant
>Assignee: Steve Malenfant
>Priority: Minor
>  Labels: easyfix
> Fix For: 2.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The `20170205101432_cdn_table_domain_name.go` migration contains reference to 
> some public tables and needs the description changed from "Starting migration 
> 20130106222315".



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

[jira] [Created] (TC-512) Default cdn.conf should have a traffic_ops_golang_port defined

[Steve Malenfant (JIRA)]

Steve Malenfant created TC-512:
--

 Summary: Default cdn.conf should have a traffic_ops_golang_port 
defined
 Key: TC-512
 URL: https://issues.apache.org/jira/browse/TC-512
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops
Affects Versions: 2.1.0
Reporter: Steve Malenfant
Priority: Trivial


Postinstall handles adding traffic_ops_golang_port to the cdn.conf, but there 
is no example in the default cdn.conf.

Almost documentation bug, but having some working defaults in cdn.conf is a 
good idea.



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

[GitHub] incubator-trafficcontrol issue #797: [BACKPORT][TC-511] Remove reference to ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/47/



---
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-511) migrations: Remove the reference to public table

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/46/



> migrations: Remove the reference to public table
> 
>
> Key: TC-511
> URL: https://issues.apache.org/jira/browse/TC-511
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
> Environment: Centos 7.3, Postgres 0.9.6
>Reporter: Steve Malenfant
>Assignee: Steve Malenfant
>Priority: Minor
>  Labels: easyfix
> Fix For: 2.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The `20170205101432_cdn_table_domain_name.go` migration contains reference to 
> some public tables and needs the description changed from "Starting migration 
> 20130106222315".



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

[GitHub] incubator-trafficcontrol pull request #797: [BACKPORT][TC-511] Remove refere...

[smalenfant]

GitHub user smalenfant opened a pull request:

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

[BACKPORT][TC-511] Remove reference to public database



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

$ git pull https://github.com/smalenfant/incubator-trafficcontrol 
backport-2.1-tc-511

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

https://github.com/apache/incubator-trafficcontrol/pull/797.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 #797


commit 3271631f15efd035989a1abfaff76a462e60a797
Author: Steve Malenfant 
Date:   2017-08-11T18:52:32Z

Remove reference to table "public" and match description

commit c141e47a68096e55018bc7b65376e68a218a52aa
Author: Steve Malenfant 
Date:   2017-08-11T19:13:13Z

Removed ".go" typo




---
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-511) migrations: Remove the reference to public table

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/45/



> migrations: Remove the reference to public table
> 
>
> Key: TC-511
> URL: https://issues.apache.org/jira/browse/TC-511
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
> Environment: Centos 7.3, Postgres 0.9.6
>Reporter: Steve Malenfant
>Assignee: Steve Malenfant
>Priority: Minor
>  Labels: easyfix
> Fix For: 2.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The `20170205101432_cdn_table_domain_name.go` migration contains reference to 
> some public tables and needs the description changed from "Starting migration 
> 20130106222315".



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

[GitHub] incubator-trafficcontrol issue #796: [TC-511] Remove reference to public dat...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/45/



---
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 #796: [TC-511] Remove reference to pub...

[smalenfant]

GitHub user smalenfant opened a pull request:

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

[TC-511] Remove reference to public database



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

$ git pull https://github.com/smalenfant/incubator-trafficcontrol 
sm-migration-tc-511

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

https://github.com/apache/incubator-trafficcontrol/pull/796.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 #796


commit 7aef1c98820f297bc1f2b65b9fd288357bfd5b53
Author: Steve Malenfant 
Date:   2017-08-11T17:58:53Z

Merge pull request #1 from apache/master

Merging master

commit 199f207c67b38d778d0a6caa88b2229ae84885d5
Author: Steve Malenfant 
Date:   2017-08-11T18:52:32Z

Remove reference to table "public" and match description




---
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-511) migrations: Remove the reference to public table

[Steve Malenfant (JIRA)]

Steve Malenfant created TC-511:
--

 Summary: migrations: Remove the reference to public table
 Key: TC-511
 URL: https://issues.apache.org/jira/browse/TC-511
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops
Affects Versions: 2.1.0
 Environment: Centos 7.3, Postgres 0.9.6
Reporter: Steve Malenfant
Assignee: Steve Malenfant
Priority: Minor
 Fix For: 2.1.0


The `20170205101432_cdn_table_domain_name.go` migration contains reference to 
some public tables and needs the description changed from "Starting migration 
20130106222315".



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

[GitHub] incubator-trafficcontrol pull request #786: Fix TO ORT for missing Content-L...

[rob05c]

Github user rob05c commented on a diff in the pull request:


https://github.com/apache/incubator-trafficcontrol/pull/786#discussion_r132727173
  
--- Diff: traffic_ops/bin/traffic_ops_ort.pl ---
@@ -1623,9 +1623,7 @@ sub check_lwp_response_content_length {
my $url   = $lwp_response->request->uri;
 
if ( !defined($lwp_response->header('Content-Length')) ) {
-   ( $log_level >> $panic_level ) && print $log_level_str . " $url 
did not return a Content-Length header!\n";
-   exit;
-   return 1;
+   return 0; # Content-Length MAY be omitted per HTTP/1.1 RFC 
7230, and in fact MUST NOT be included with a 'Transfer-Encoding: Chunked' 
header, which MUST be accepted by clients.
--- End diff --

X prefixes are deprecated https://tools.ietf.org/html/rfc6648

Further, X-prefixed or not, it doesn't solve the problem the deprecation 
addressed, of allowing inconsistent adoption. 
https://trac.ietf.org/trac/httpbis/ticket/178

How about `Whole-Content-SHA512`?


---
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 #786: Fix TO ORT for missing Content-L...

[alficles]

Github user alficles commented on a diff in the pull request:


https://github.com/apache/incubator-trafficcontrol/pull/786#discussion_r132722069
  
--- Diff: traffic_ops/bin/traffic_ops_ort.pl ---
@@ -1623,9 +1623,7 @@ sub check_lwp_response_content_length {
my $url   = $lwp_response->request->uri;
 
if ( !defined($lwp_response->header('Content-Length')) ) {
-   ( $log_level >> $panic_level ) && print $log_level_str . " $url 
did not return a Content-Length header!\n";
-   exit;
-   return 1;
+   return 0; # Content-Length MAY be omitted per HTTP/1.1 RFC 
7230, and in fact MUST NOT be included with a 'Transfer-Encoding: Chunked' 
header, which MUST be accepted by clients.
--- End diff --

Current recommendations are to implement your own `X-` header and use a 
nice modern hash. Reusing the `Content-MD5` header is not recommended because 
many clients implemented it (varyingly, leading to trouble) before it was 
pulled from the spec. I'd either use an `X-Content-SHA256` field or, 
alternately, a totally separate request that just fetches the hash. (Race 
conditions about on that approach, though.)


---
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-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> TPv2 - add the ability to generate ISO
> --
>
> Key: TC-437
> URL: https://issues.apache.org/jira/browse/TC-437
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Priority: Minor
>
> add the ability to generate ISO



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

[GitHub] incubator-trafficcontrol pull request #783: [TC-437] - adds the ability to g...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #360: [TC-187] fix HTTPs bugs

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-187) Update delivery service makes SSL keys invalid

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Update delivery service makes SSL keys invalid
> --
>
> Key: TC-187
> URL: https://issues.apache.org/jira/browse/TC-187
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Zhilin Huang
>Assignee: Zhilin Huang
>  Labels: ssl, xml-id
>
> Modify xml-id or subdomain in a https delivery service will make existing SSL 
> keys invalid.
> And there is problem to generate keys if using "http and https" together with 
> 1 host_regex, and 1 path_regex.
> BTW, the certificate returned by RESTful API is not consistent with that GUI.



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

[jira] [Updated] (TC-510) cannot apply ipv6 on delivery services

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-510:
---
Affects Version/s: 2.1.0
  Component/s: (was: Traffic Portal)

> cannot apply ipv6 on delivery services
> --
>
> Key: TC-510
> URL: https://issues.apache.org/jira/browse/TC-510
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Sean Aoyagi
>
> attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
> delivery service.
> on trafficops, 2.1.0-6566.3980b417.el7 Also receive following error: 
> {code}Traffic Ops fatal error occurred while processing your request. 
> Error at line 50 (%= field('ds.cdn_id')->select( \@{$cdns} );) 
> Global symbol "$cdns" requires explicit package name at template 
> delivery_service/_form.html.ep line 50. Global symbol "$profiles" requires 
> explicit package name at template delivery_service/_form.html.ep line 
> 375.{code}



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

[jira] [Updated] (TC-510) cannot apply ipv6 on delivery services

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-510:
---
Attachment: (was: Pasted image at 2017_08_11 09_09 AM.png)

> cannot apply ipv6 on delivery services
> --
>
> Key: TC-510
> URL: https://issues.apache.org/jira/browse/TC-510
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Portal
>Reporter: Sean Aoyagi
>
> attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
> delivery service.
> on trafficops, 2.1.0-6566.3980b417.el7 Also receive following error: 
> {code}Traffic Ops fatal error occurred while processing your request. 
> Error at line 50 (%= field('ds.cdn_id')->select( \@{$cdns} );) 
> Global symbol "$cdns" requires explicit package name at template 
> delivery_service/_form.html.ep line 50. Global symbol "$profiles" requires 
> explicit package name at template delivery_service/_form.html.ep line 
> 375.{code}



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

[jira] [Updated] (TC-510) cannot apply ipv6 on delivery services

[Sean Aoyagi (JIRA)]

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

Sean Aoyagi updated TC-510:
---
Description: 
attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
delivery service.

on trafficops, 2.1.0-6566.3980b417.el7 Also receive following error: 
{code}Traffic Ops fatal error occurred while processing your request. 
Error at line 50 (%= field('ds.cdn_id')->select( \@{$cdns} );) 
Global symbol "$cdns" requires explicit package name at template 
delivery_service/_form.html.ep line 50. Global symbol "$profiles" requires 
explicit package name at template delivery_service/_form.html.ep line 375.{code}

  was:
attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
delivery service.

on trafficops, 2.1.0-6566.3980b417.el7 Also recieve error 


> cannot apply ipv6 on delivery services
> --
>
> Key: TC-510
> URL: https://issues.apache.org/jira/browse/TC-510
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Portal
>Reporter: Sean Aoyagi
> Attachments: Pasted image at 2017_08_11 09_09 AM.png, Pasted image at 
> 2017_08_11 09_10 AM.png
>
>
> attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
> delivery service.
> on trafficops, 2.1.0-6566.3980b417.el7 Also receive following error: 
> {code}Traffic Ops fatal error occurred while processing your request. 
> Error at line 50 (%= field('ds.cdn_id')->select( \@{$cdns} );) 
> Global symbol "$cdns" requires explicit package name at template 
> delivery_service/_form.html.ep line 50. Global symbol "$profiles" requires 
> explicit package name at template delivery_service/_form.html.ep line 
> 375.{code}



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

[jira] [Updated] (TC-510) cannot apply ipv6 on delivery services

[Sean Aoyagi (JIRA)]

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

Sean Aoyagi updated TC-510:
---
Component/s: Traffic Ops

> cannot apply ipv6 on delivery services
> --
>
> Key: TC-510
> URL: https://issues.apache.org/jira/browse/TC-510
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Portal
>Reporter: Sean Aoyagi
> Attachments: Pasted image at 2017_08_11 09_09 AM.png, Pasted image at 
> 2017_08_11 09_10 AM.png
>
>
> attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
> delivery service.
> on trafficops, 2.1.0-6566.3980b417.el7 Also recieve error 



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

[jira] [Updated] (TC-510) cannot apply ipv6 on delivery services

[Sean Aoyagi (JIRA)]

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

Sean Aoyagi updated TC-510:
---
Description: 
attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
delivery service.

on trafficops, 2.1.0-6566.3980b417.el7 Also recieve error 

  was:attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to 
update delivery service.


> cannot apply ipv6 on delivery services
> --
>
> Key: TC-510
> URL: https://issues.apache.org/jira/browse/TC-510
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Portal
>Reporter: Sean Aoyagi
> Attachments: Pasted image at 2017_08_11 09_09 AM.png, Pasted image at 
> 2017_08_11 09_10 AM.png
>
>
> attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
> delivery service.
> on trafficops, 2.1.0-6566.3980b417.el7 Also recieve error 



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

[jira] [Created] (TC-510) cannot apply ipv6 on delivery services

[Sean Aoyagi (JIRA)]

Sean Aoyagi created TC-510:
--

 Summary: cannot apply ipv6 on delivery services
 Key: TC-510
 URL: https://issues.apache.org/jira/browse/TC-510
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Portal
Reporter: Sean Aoyagi
 Attachments: Pasted image at 2017_08_11 09_09 AM.png, Pasted image at 
2017_08_11 09_10 AM.png

attempt to change ipv6 flag from ipv4 to ipv6 results in a / unable to update 
delivery service.



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

[jira] [Commented] (TC-375) yum upgrade traffic_ops... can't find goose

[Steve Malenfant (JIRA)]

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

Steve Malenfant commented on TC-375:


[~dewrich] I just tried upgrading from 2.0 to 
traffic_ops-2.1.0-6795.e2e89e12.el7.x86_64.rpm and the same thing happened.

goose was in the path. Does the fix introduced take care of the 2.0 -> 2.1 RPM 
upgrade?

{code:java}
Preparing...  # [100%]
trafops:x:995:ansible
trafops:x:997:995::/opt/traffic_ops:/sbin/nologin

Backing up config files.

Stopping traffic_ops (via systemctl):  [  OK  ]
Updating / installing...
   1:traffic_ops-2.1.0-6795.e2e89e12.ewarning: 
/opt/traffic_ops/app/conf/cdn.conf created as 
/opt/traffic_ops/app/conf/cdn.conf.rpmnew
# [ 50%]

Restoring config files.

Migrating database...
Can't exec "goose": No such file or directory at db/admin.pl line 183.
Can't run goose
Database migration failed.

Upgrade complete.
{code}


> yum upgrade traffic_ops... can't find goose
> ---
>
> Key: TC-375
> URL: https://issues.apache.org/jira/browse/TC-375
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dewayne Richardson
>  Labels: goose, postinstall, yum
> Fix For: 2.1.0
>
>
> Traffic Ops postinstall puts goose in /opt/traffic_ops/go/bin.   The rpm 
> upgrade path executes `db/admin.pl upgrade` which tries to run goose,   but 
> can't find it because it's not in the root PATH.



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

[jira] [Updated] (TC-161) ort does not restart ATS when it should

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-161:
---
Fix Version/s: 2.1.0

> ort does not restart ATS when it should
> ---
>
> Key: TC-161
> URL: https://issues.apache.org/jira/browse/TC-161
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops ORT
>Affects Versions: 2.1.0
>Reporter: John Shen
>Assignee: John Shen
> Fix For: 2.1.0
>
>
> ort does not restart ATS when ATS is already running



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

[jira] [Commented] (TC-151) Delivery Service XML IDs should be limited to lower-case letters

[Steve Malenfant (JIRA)]

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

Steve Malenfant commented on TC-151:


[~shemesh] Are we talking about the XML ID or the HOST_REGEXP?

Maybe I'm wrong, but the XML ID is not part of the FQDN.

> Delivery Service XML IDs should be limited to lower-case letters
> 
>
> Key: TC-151
> URL: https://issues.apache.org/jira/browse/TC-151
> Project: Traffic Control
>  Issue Type: New Feature
>  Components: Traffic Ops
>Affects Versions: 1.7.0
>Reporter: Oren Shemesh
>Priority: Minor
>  Labels: delivery_service, xml-id
>
> The DNS system is case-insensitive. Since a delivery service XML ID is used 
> as part of the FQDN of the cache being redirected to, two different DSs 
> cannot differ only by case.
> This leads to the conclusion that it is best if we limit the XML IDs of 
> delivery services to be lower-case only.
> This would achieve the following:
> 1. Make domain names used by TC 'conventional' (i.e. lower-case only)
> 2. Remove the possibility of a case-conflict between DSs
> 3. Currently, Traffic Router does not behave correctly when a DS XML ID 
> contains upper case letters. Limiting to lower-case would prevent the need to 
> fix this :-)
> Current problems with TR behaviour, when an XML ID contains opper-case letter 
> are:
> 1. The TR sends a redirect to a host FQDN which contains a lower-case version 
> of the DS XML ID
> 2. The TR does not resolve the lower-case version of the host FQDN.
> Here is an example to demo current bug in TR. DS XML ID is opencachehub-DT, 
> TR redirects to opencachehub-dt, and then refused to resolve the cache name 
> using this DS (a lot of irrelevant data was removed fro this text):
> $ curl -L -s -D - 
> http://tr.opencachehub-DT.stage-cdn.tc-stage.cqloud.com/video01.mp4 -v
> * Connected to tr.opencachehub-DT.stage-cdn.tc-stage.cqloud.com 
> (54.244.152.242) port 80 (#0)
> > GET /video01.mp4 HTTP/1.1
> > Host: tr.opencachehub-DT.stage-cdn.tc-stage.cqloud.com
> > Accept: */*
> > 
> < HTTP/1.1 302 Moved Temporarily
> < Location: 
> http://p39-edge-lab.opencachehub-dt.stage-cdn.tc-stage.cqloud.com/video01.mp4
> < Content-Length: 0
> < 
> * Connection #0 to host tr.opencachehub-DT.stage-cdn.tc-stage.cqloud.com left 
> intact
> * Issue another request to this URL: 
> 'http://p39-edge-lab.opencachehub-dt.stage-cdn.tc-stage.cqloud.com/video01.mp4'
> * getaddrinfo(3) failed for 
> p39-edge-lab.opencachehub-dt.stage-cdn.tc-stage.cqloud.com:80
> * Couldn't resolve host 
> 'p39-edge-lab.opencachehub-dt.stage-cdn.tc-stage.cqloud.com'



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

[jira] [Commented] (TC-161) ort does not restart ATS when it should

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/44/



> ort does not restart ATS when it should
> ---
>
> Key: TC-161
> URL: https://issues.apache.org/jira/browse/TC-161
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops ORT
>Affects Versions: 2.1.0
>Reporter: John Shen
>Assignee: John Shen
>
> ort does not restart ATS when ATS is already running



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

[GitHub] incubator-trafficcontrol issue #298: [TC-161] ort does not restart ATS when ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/44/



---
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-161) ort does not restart ATS when it should

[John Shen (JIRA)]

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

John Shen commented on TC-161:
--

[~hbeatty] Did a merge with latest master. Please check if it is ok now, thanks.

> ort does not restart ATS when it should
> ---
>
> Key: TC-161
> URL: https://issues.apache.org/jira/browse/TC-161
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops ORT
>Affects Versions: 2.1.0
>Reporter: John Shen
>Assignee: John Shen
>
> ort does not restart ATS when ATS is already running



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

[jira] [Commented] (TC-115) ATS sometimes does not reload the config while receiving a "traffic_line -x"

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/43/



> ATS sometimes does not reload the config while receiving a "traffic_line -x"
> 
>
> Key: TC-115
> URL: https://issues.apache.org/jira/browse/TC-115
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Ops ORT
>Reporter: John Shen
>Assignee: John Shen
>Priority: Minor
>  Labels: traffic_line-x
>
> If the owner of a config file (e.g. ssl_multicert.config) is not ats.ats, ATS 
> does not reload the config while receiving a "traffic_line -x".



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

[GitHub] incubator-trafficcontrol issue #211: [TC-115] make sure ats config files are...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/43/



---
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] [Updated] (TC-501) TPv2 installation - better defaults are required

[Nir Sopher (JIRA)]

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

Nir Sopher updated TC-501:
--
Issue Type: Improvement  (was: Bug)

> TPv2 installation - better defaults are required
> 
>
> Key: TC-501
> URL: https://issues.apache.org/jira/browse/TC-501
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>
> After basic install of traffic-portal based on the documentation, traffic 
> portal failed to launch. this is due to relative pathes to the logs and 
> static files appear in the default configuration.
> Note that the working directory of the server is "/"
> First, the log path (./server/log) does not exists. A possible fix is to 
> change the dir to /opt/traffic_portal/server/log and create the log dir if 
> needed. 
> Second. the files static path should be set to "opt/traffic_portal/public"



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