[jira] [Commented] (TC-44) TR fd leak observed when new HTTPS DS is added without certificate

[John Shen (JIRA)]

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

John Shen commented on TC-44:
-

lower to minor as discussed in slack-dev

> TR fd leak observed when new HTTPS DS is added without certificate
> --
>
> Key: TC-44
> URL: https://issues.apache.org/jira/browse/TC-44
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Affects Versions: 1.7.0
>Reporter: John Shen
>Assignee: John Shen
>Priority: Minor
> Fix For: 2.1.0, 2.2.0
>
>
> In TC 1.7, when a new HTTPS DS (HTTP 302 routing) is added without 
> certificate, there will be fd leak observed on TR. The connections to TM stay 
> in CLOSE-WAIT, which begins to show ~20mins after a new DS without cert/key 
> is added.
> And CrState appears to be blocked in ~20mins as well, i.e. no request from TR 
> to TM to fetch CrState.



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

[jira] [Updated] (TC-44) TR fd leak observed when new HTTPS DS is added without certificate

[John Shen (JIRA)]

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

John Shen updated TC-44:

Priority: Minor  (was: Major)

> TR fd leak observed when new HTTPS DS is added without certificate
> --
>
> Key: TC-44
> URL: https://issues.apache.org/jira/browse/TC-44
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Affects Versions: 1.7.0
>Reporter: John Shen
>Assignee: John Shen
>Priority: Minor
> Fix For: 2.1.0, 2.2.0
>
>
> In TC 1.7, when a new HTTPS DS (HTTP 302 routing) is added without 
> certificate, there will be fd leak observed on TR. The connections to TM stay 
> in CLOSE-WAIT, which begins to show ~20mins after a new DS without cert/key 
> is added.
> And CrState appears to be blocked in ~20mins as well, i.e. no request from TR 
> to TM to fetch CrState.



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

[GitHub] incubator-trafficcontrol issue #829: Fix TO Go monitoring numeric values

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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 #829: Fix TO Go monitoring numeric values

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/50/



---
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 #829: Fix TO Go monitoring numeric values

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/48/



---
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 #829: Fix TO Go monitoring numeric val...

[rob05c]

GitHub user rob05c opened a pull request:

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

Fix TO Go monitoring numeric values

Perl TO monitoring.json returns numeric types for parameters whose strings 
successfully convert to integers. This replicates that behavior.

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

$ git pull https://github.com/rob05c/incubator-trafficcontrol 
to-go-monitoringtypes

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

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


commit 0551be2cbe732de00be5cbb2da350b752b5ffdde
Author: Robert Butts 
Date:   2017-08-16T23:56:53Z

Fix TO Go monitoring numeric values




---
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 #828: MSO Documentation and fixes

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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 #828: MSO Documentation and fixes

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/49/



---
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 #828: MSO Documentation and fixes

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/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.
---

[GitHub] incubator-trafficcontrol pull request #828: MSO Documentation and fixes

[dg4prez]

GitHub user dg4prez opened a pull request:

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

MSO Documentation and fixes

Updated documentation for multi-site to include ATS 6 MSO instructions.  
Minor corrections to other files from errors in make.

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

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

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

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


commit cf1e6e1bad580ab716a9e55e92ce0947ca669d15
Author: Derek Gelinas 
Date:   2017-08-16T21:36:04Z

fix multisite instructions

commit eb071fb98ba961b4ddbf18fe40f9cccfb34db3d4
Author: Derek Gelinas 
Date:   2017-08-16T23:30:22Z

minor corrections




---
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 #826: Fix Traffic Monitor log EventfRaw for n...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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 #827: Fix Traffic Ops Go cookie to have path,...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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 #827: Fix Traffic Ops Go cookie to have path,...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/48/



---
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 #826: Fix Traffic Monitor log EventfRaw for n...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/46/



---
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-294) Missing location parameter leads to broken remap.config

[Mark Torluemke (JIRA)]

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

Mark Torluemke commented on TC-294:
---

'Improvement' is better than 'bug'. The parameter with name 'location' controls 
whether TO generates a config file for ATS, and also determines whether ORT 
audits this file. The actual 'location' parameter can be inferred, and only 
adds additional fragility to the config file distribution system.

> Missing location parameter leads to broken remap.config
> ---
>
> Key: TC-294
> URL: https://issues.apache.org/jira/browse/TC-294
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops ORT
>Affects Versions: 2.1.0, 2.0.0, 2.2.0
>Reporter: Mark Torluemke
>Priority: Minor
>  Labels: remap.config
> Fix For: 2.2.0
>
>
> From the original GH issue #195:
> For things like header_rewrite, cacheurl, etc, there isn't value in managing 
> the 'location' parameter outside the delivery service assignment to the 
> caches...is there?



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

[GitHub] incubator-trafficcontrol pull request #827: Fix Traffic Ops Go cookie to hav...

[rob05c]

GitHub user rob05c opened a pull request:

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

Fix Traffic Ops Go cookie to have path, httponly



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

$ git pull https://github.com/rob05c/incubator-trafficcontrol 
to-go-fixcookiepath

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

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


commit c022f7600ebc045aad372d536074c0a3e017a128
Author: Robert Butts 
Date:   2017-08-16T22:01:03Z

Fix TO Go cookie to have path, httponly




---
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-294) Missing location parameter leads to broken remap.config

[Mark Torluemke (JIRA)]

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

Mark Torluemke updated TC-294:
--
Issue Type: Improvement  (was: Bug)

> Missing location parameter leads to broken remap.config
> ---
>
> Key: TC-294
> URL: https://issues.apache.org/jira/browse/TC-294
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops ORT
>Affects Versions: 2.1.0, 2.0.0, 2.2.0
>Reporter: Mark Torluemke
>Priority: Minor
>  Labels: remap.config
> Fix For: 2.2.0
>
>
> From the original GH issue #195:
> For things like header_rewrite, cacheurl, etc, there isn't value in managing 
> the 'location' parameter outside the delivery service assignment to the 
> caches...is there?



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

[GitHub] incubator-trafficcontrol issue #826: Fix Traffic Monitor log EventfRaw for n...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-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.
---

[GitHub] incubator-trafficcontrol pull request #826: Fix Traffic Monitor log EventfRa...

[rob05c]

GitHub user rob05c opened a pull request:

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

Fix Traffic Monitor log EventfRaw for nil loggers



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

$ git pull https://github.com/rob05c/incubator-trafficcontrol 
tm-log-fixeventfraw

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

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


commit fab62e38ac2bcdf1babe3b3194f4673a00e5d4a4
Author: Robert Butts 
Date:   2017-08-16T21:59:44Z

Fix TM log EventfRaw for nil loggers




---
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-441) TPv2 - implement password reset functionality

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

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



> TPv2 - implement password reset functionality
> -
>
> Key: TC-441
> URL: https://issues.apache.org/jira/browse/TC-441
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>
> implement password reset functionality



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

[GitHub] incubator-trafficcontrol issue #825: [TC-441] - hooks up password reset to T...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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-441) TPv2 - implement password reset functionality

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/44/



> TPv2 - implement password reset functionality
> -
>
> Key: TC-441
> URL: https://issues.apache.org/jira/browse/TC-441
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>
> implement password reset functionality



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

[jira] [Commented] (TC-515) Traffic Portal - Show human readable protocol on DS page

[ASF GitHub Bot (JIRA)]

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

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

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


https://github.com/apache/incubator-trafficcontrol/pull/818#discussion_r133571450
  
--- Diff: traffic_portal/app/src/common/modules/header/header.tpl.html ---
@@ -61,11 +61,11 @@
 
 
 
-
-
-
-
-
+
--- End diff --

yea, i did


> Traffic Portal - Show human readable protocol on DS page
> 
>
> Key: TC-515
> URL: https://issues.apache.org/jira/browse/TC-515
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0, 2.2.0
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0, 2.2.0
>
>
> In the TO UI, the delivery service protocol is converted from an int (0,1,2) 
> to a human readable string (http, https, http and https, etc).  The new TO 
> portal just shows the int but it should show the human readable string.



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

[GitHub] incubator-trafficcontrol pull request #818: [TC-515] - TPv2 - adds human rea...

[mitchell852]

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


https://github.com/apache/incubator-trafficcontrol/pull/818#discussion_r133571450
  
--- Diff: traffic_portal/app/src/common/modules/header/header.tpl.html ---
@@ -61,11 +61,11 @@
 
 
 
-
-
-
-
-
+
--- End diff --

yea, i did


---
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 #825: [TC-441] - hooks up password reset to T...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/46/



---
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-441) TPv2 - implement password reset functionality

[ASF GitHub Bot (JIRA)]

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

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

GitHub user mitchell852 opened a pull request:

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

[TC-441] - hooks up password reset to TP



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-441-tp-password-reset

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

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


commit a1313fbf5825a5e485e6e60eb7712a56e040172a
Author: Jeremy Mitchell 
Date:   2017-08-16T21:22:13Z

hooks up password reset to TP




> TPv2 - implement password reset functionality
> -
>
> Key: TC-441
> URL: https://issues.apache.org/jira/browse/TC-441
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>
> implement password reset functionality



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

[GitHub] incubator-trafficcontrol pull request #825: [TC-441] - hooks up password res...

[mitchell852]

GitHub user mitchell852 opened a pull request:

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

[TC-441] - hooks up password reset to TP



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-441-tp-password-reset

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

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


commit a1313fbf5825a5e485e6e60eb7712a56e040172a
Author: Jeremy Mitchell 
Date:   2017-08-16T21:22:13Z

hooks up password reset to TP




---
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-441) TPv2 - implement password reset functionality

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-441:
---
Affects Version/s: 2.1.0
 Priority: Major  (was: Minor)
   Issue Type: Bug  (was: Improvement)

> TPv2 - implement password reset functionality
> -
>
> Key: TC-441
> URL: https://issues.apache.org/jira/browse/TC-441
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>
> implement password reset functionality



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

[jira] [Commented] (TC-491) Deleting Delivery Service with associated job in job table fails due to foreign key constraint violation

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

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



> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation
> 
>
> Key: TC-491
> URL: https://issues.apache.org/jira/browse/TC-491
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Assignee: Jeremy Mitchell
>Priority: Critical
> Fix For: 2.1.0, 2.2.0
>
>
> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation.
> E.g.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table "deliveryservice" violates foreign 
> key constraint "fk_job_deliveryservice1" on table "job"
> DETAIL:  Key (id)=(714) is still referenced from table "job". [for Statement 
> "DELETE FROM deliveryservice WHERE ( id = ? )" with ParamValues: 1='714'] at 
> /opt/traffic_ops/app/lib/API/Deliveryservice.pm line 642
> Workaround: No UI/API end-point to delete the associated job.  Delete 
> associated job from database.
> NOTE: Other Traffic Ops versions may also be affected.



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

[GitHub] incubator-trafficcontrol issue #824: [TC-491] [TC-492] - deletes applicable ...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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-491) Deleting Delivery Service with associated job in job table fails due to foreign key constraint violation

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/45/



> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation
> 
>
> Key: TC-491
> URL: https://issues.apache.org/jira/browse/TC-491
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Assignee: Jeremy Mitchell
>Priority: Critical
> Fix For: 2.1.0, 2.2.0
>
>
> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation.
> E.g.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table "deliveryservice" violates foreign 
> key constraint "fk_job_deliveryservice1" on table "job"
> DETAIL:  Key (id)=(714) is still referenced from table "job". [for Statement 
> "DELETE FROM deliveryservice WHERE ( id = ? )" with ParamValues: 1='714'] at 
> /opt/traffic_ops/app/lib/API/Deliveryservice.pm line 642
> Workaround: No UI/API end-point to delete the associated job.  Delete 
> associated job from database.
> NOTE: Other Traffic Ops versions may also be affected.



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

[GitHub] incubator-trafficcontrol issue #824: [TC-491] [TC-492] - deletes applicable ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-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.
---

[jira] [Commented] (TC-491) Deleting Delivery Service with associated job in job table fails due to foreign key constraint violation

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/43/



> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation
> 
>
> Key: TC-491
> URL: https://issues.apache.org/jira/browse/TC-491
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Assignee: Jeremy Mitchell
>Priority: Critical
> Fix For: 2.1.0, 2.2.0
>
>
> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation.
> E.g.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table "deliveryservice" violates foreign 
> key constraint "fk_job_deliveryservice1" on table "job"
> DETAIL:  Key (id)=(714) is still referenced from table "job". [for Statement 
> "DELETE FROM deliveryservice WHERE ( id = ? )" with ParamValues: 1='714'] at 
> /opt/traffic_ops/app/lib/API/Deliveryservice.pm line 642
> Workaround: No UI/API end-point to delete the associated job.  Delete 
> associated job from database.
> NOTE: Other Traffic Ops versions may also be affected.



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

[GitHub] incubator-trafficcontrol issue #824: [TC-491] [TC-492] - deletes applicable ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/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.
---

[GitHub] incubator-trafficcontrol pull request #824: [TC-491] [TC-492] - deletes appl...

[mitchell852]

GitHub user mitchell852 opened a pull request:

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

[TC-491] [TC-492] - deletes applicable staticdnsentries and jobs when a ds 
is deleted



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-492-staticdnsentry-cascade-delete

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

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


commit bf048b657ae745b993e4a76e50c491d3c5436327
Author: Jeremy Mitchell 
Date:   2017-08-16T20:32:14Z

deletes applicable staticdnsentries and jobs when a ds is deleted




---
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-491) Deleting Delivery Service with associated job in job table fails due to foreign key constraint violation

[ASF GitHub Bot (JIRA)]

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

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

GitHub user mitchell852 opened a pull request:

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

[TC-491] [TC-492] - deletes applicable staticdnsentries and jobs when a ds 
is deleted



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-492-staticdnsentry-cascade-delete

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

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


commit bf048b657ae745b993e4a76e50c491d3c5436327
Author: Jeremy Mitchell 
Date:   2017-08-16T20:32:14Z

deletes applicable staticdnsentries and jobs when a ds is deleted




> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation
> 
>
> Key: TC-491
> URL: https://issues.apache.org/jira/browse/TC-491
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Assignee: Jeremy Mitchell
>Priority: Critical
> Fix For: 2.1.0, 2.2.0
>
>
> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation.
> E.g.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table "deliveryservice" violates foreign 
> key constraint "fk_job_deliveryservice1" on table "job"
> DETAIL:  Key (id)=(714) is still referenced from table "job". [for Statement 
> "DELETE FROM deliveryservice WHERE ( id = ? )" with ParamValues: 1='714'] at 
> /opt/traffic_ops/app/lib/API/Deliveryservice.pm line 642
> Workaround: No UI/API end-point to delete the associated job.  Delete 
> associated job from database.
> NOTE: Other Traffic Ops versions may also be affected.



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

[jira] [Created] (TC-538) Traffic Stats should be able to poll over IPv6 if IPv4 is not available

[David Neuman (JIRA)]

David Neuman created TC-538:
---

 Summary: Traffic Stats should be able to poll over IPv6 if IPv4 is 
not available
 Key: TC-538
 URL: https://issues.apache.org/jira/browse/TC-538
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Stats
Reporter: David Neuman


Currently if you have TM that has A and  records, but only  is 
available, TS will fail because it tries to use the IPv4 address only.  TS 
should be smart enough to use the  record if it is available.



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

[jira] [Commented] (TC-515) Traffic Portal - Show human readable protocol on DS page

[ASF GitHub Bot (JIRA)]

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

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

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


https://github.com/apache/incubator-trafficcontrol/pull/818#discussion_r133551958
  
--- Diff: traffic_portal/app/src/common/modules/header/header.tpl.html ---
@@ -61,11 +61,11 @@
 
 
 
-
-
-
-
-
+
--- End diff --

did you mean to leave this commented out?


> Traffic Portal - Show human readable protocol on DS page
> 
>
> Key: TC-515
> URL: https://issues.apache.org/jira/browse/TC-515
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0, 2.2.0
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0, 2.2.0
>
>
> In the TO UI, the delivery service protocol is converted from an int (0,1,2) 
> to a human readable string (http, https, http and https, etc).  The new TO 
> portal just shows the int but it should show the human readable string.



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

[GitHub] incubator-trafficcontrol issue #818: [TC-515] - TPv2 - adds human readable d...

[dneuman64]

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/818
  
why does asfgit have to comment on this so much?  makes too much clutter



---
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 #818: [TC-515] - TPv2 - adds human rea...

[dneuman64]

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


https://github.com/apache/incubator-trafficcontrol/pull/818#discussion_r133551958
  
--- Diff: traffic_portal/app/src/common/modules/header/header.tpl.html ---
@@ -61,11 +61,11 @@
 
 
 
-
-
-
-
-
+
--- End diff --

did you mean to leave this commented out?


---
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-515) Traffic Portal - Show human readable protocol on DS page

[ASF GitHub Bot (JIRA)]

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

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

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/818
  
@mitchell852 I will get this merged today


> Traffic Portal - Show human readable protocol on DS page
> 
>
> Key: TC-515
> URL: https://issues.apache.org/jira/browse/TC-515
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0, 2.2.0
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0, 2.2.0
>
>
> In the TO UI, the delivery service protocol is converted from an int (0,1,2) 
> to a human readable string (http, https, http and https, etc).  The new TO 
> portal just shows the int but it should show the human readable string.



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

[GitHub] incubator-trafficcontrol issue #818: [TC-515] - TPv2 - adds human readable d...

[dneuman64]

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/818
  
@mitchell852 I will get this merged today


---
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-537) Update TO routing APIs to use Traffic Stats data (InfluxDB)

[David Neuman (JIRA)]

David Neuman created TC-537:
---

 Summary: Update TO routing APIs to use Traffic Stats data 
(InfluxDB)
 Key: TC-537
 URL: https://issues.apache.org/jira/browse/TC-537
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops, Traffic Stats
Reporter: David Neuman


Dependent on [TC-536|https://issues.apache.org/jira/browse/TC-536]

Currently the routing endpoint in Traffic Ops (apis/1.2/cdns/routing, 
api/1.2/deliveryservices/:id/routing.json) reach out to the crs/stats API on 
one Traffic Router to get the information.  Traffic Routers are stateless 
therefore the crs/stats API data from one traffic router is not a full picture. 
 Once TC-536 is complete the routing APIs in Traffic Ops should be updated to 
use the data that is stored by Traffic Stats in InfluxDB. 



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

[jira] [Comment Edited] (TC-384) Profiles exported from TC1.7 cannot be imported to TC 2.1

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood edited comment on TC-384 at 8/16/17 7:50 PM:
--

I was going to suggest adding this to release notes.  Overkill?

[~n...@qwilt.com] I agree..   Can you add a note and close it?


was (Author: dangogh):
I was going to suggest adding this to release notes.  Overkill?

> Profiles exported from TC1.7 cannot be imported to TC 2.1
> -
>
> Key: TC-384
> URL: https://issues.apache.org/jira/browse/TC-384
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>Assignee: Dan Kirkwood
>  Labels: profile_parameters
>
> Due to a missing "profile-type" in the 1.7 json, the profiles cannot be 
> imported.



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

[jira] [Created] (TC-536) Update Traffic Stats to collect and store /crs/stats data from Traffic Routers

[David Neuman (JIRA)]

David Neuman created TC-536:
---

 Summary: Update Traffic Stats to collect and store /crs/stats data 
from Traffic Routers
 Key: TC-536
 URL: https://issues.apache.org/jira/browse/TC-536
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Router, Traffic Stats
Reporter: David Neuman


Traffic Router has an API endpoint (:/crs/stats) that has lots of really 
good information.  Traffic Stats should poll this API endpoint and store the 
data in InfluxDB. 


TODO:  
- Update create_ts_database to create new traffic_router table
- Update create_ts_database to create retention policies on traffic_router table
- Update create_ts_database to add continuous queries for traffic_router data 
(downsample to 1 min is a good start)
- Add a poller to poll Traffic Router /crs/stats endpoint, collect stats, and 
write to BPS chan. 
- whatever else I forgot



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

[jira] [Commented] (TC-384) Profiles exported from TC1.7 cannot be imported to TC 2.1

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood commented on TC-384:
-

I was going to suggest adding this to release notes.  Overkill?

> Profiles exported from TC1.7 cannot be imported to TC 2.1
> -
>
> Key: TC-384
> URL: https://issues.apache.org/jira/browse/TC-384
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>Assignee: Dan Kirkwood
>  Labels: profile_parameters
>
> Due to a missing "profile-type" in the 1.7 json, the profiles cannot be 
> imported.



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

[GitHub] incubator-trafficcontrol issue #818: [TC-515] - TPv2 - adds human readable d...

[mitchell852]

Github user mitchell852 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/818
  
@dneuman64 will be looking at this one


---
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-535) DS URL sig key apis needs to have tenancy check in place

[Jeremy Mitchell (JIRA)]

Jeremy Mitchell created TC-535:
--

 Summary: DS URL sig key apis needs to have tenancy check in place
 Key: TC-535
 URL: https://issues.apache.org/jira/browse/TC-535
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops API
Affects Versions: 2.1.0
Reporter: Jeremy Mitchell
Assignee: Nir Sopher


Tenancy was introduced in 2.1, however, by default it is turned off via the 
use_tenancy parameter but when activated it is used to limit the scope of 
delivery services that a user can act on.

The following APIs needs to check tenancy to ensure users cannot act on ds's 
that they don't have access to.

post("/api/$version/deliveryservices/xmlId/:xmlId/urlkeys/generate
post("/api/$version/deliveryservices/xmlId/:xmlId/urlkeys/copyFromXmlId/:copyFromXmlId
get("/api/$version/deliveryservices/xmlId/:xmlId/urlkeys



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

[jira] [Commented] (TC-374) `systemctl stop traffic_ops` does not kill all processes

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

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



> `systemctl stop traffic_ops` does not kill all processes
> 
>
> Key: TC-374
> URL: https://issues.apache.org/jira/browse/TC-374
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
>  Labels: systemctl
> Fix For: 2.1.0, 2.2.0
>
>
> not sure why it gets in this state,  but traffic_ops processes sometimes get 
> in a state where the parent process is the root (1) for many of the 
> script/cdn workers.   The init.d script doesn't stop them because they don't 
> match the pid in `/var/run/traffic_ops.pid`.
> This needs to be more robust.
> Example:   on my test VM,  if I run this,  I see multiple parent processes:
> {quote}
>  ps -ef | grep script/cdn|grep -v root | awk '\{print $3\}'  | sort -u
>  1
>  22713
>  29306
> {quote}



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

[GitHub] incubator-trafficcontrol issue #823: [TC-374] handle orphan processes in TO ...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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-534) Traffic Router statistics are not aggregated

[Steve Malenfant (JIRA)]

Steve Malenfant created TC-534:
--

 Summary: Traffic Router statistics are not aggregated
 Key: TC-534
 URL: https://issues.apache.org/jira/browse/TC-534
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops API
Affects Versions: 2.1.0, 2.2.0
Reporter: Steve Malenfant


Looks like some of the stats APIs related to Traffic Router don't return proper 
data when there is more than 1 instance of Traffic Router (or will return data 
for OFFLINE TR).

This would affect statistics for Traffic Portal as an example. 

Looking at the code, it doesn't seem to cycle through all the request routers 
available to get statistics from a Delivery Service as an example.

Known affected APIs :
/api/1.2/deliveryservices/:id/routing.json

Few things to take in consideration
- Skip OFFLINE traffic routers
- Skip unreachable traffic routers
- Need to aggregate data? Numbers from 
`/api/1.2/deliveryservices/:id/routing.json` seems to be percentages. Does it 
matter to get an average from all request routers?

Note: I don't have full knowledge of what was intended by this API.



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

[jira] [Commented] (TC-374) `systemctl stop traffic_ops` does not kill all processes

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/42/



> `systemctl stop traffic_ops` does not kill all processes
> 
>
> Key: TC-374
> URL: https://issues.apache.org/jira/browse/TC-374
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
>  Labels: systemctl
> Fix For: 2.1.0, 2.2.0
>
>
> not sure why it gets in this state,  but traffic_ops processes sometimes get 
> in a state where the parent process is the root (1) for many of the 
> script/cdn workers.   The init.d script doesn't stop them because they don't 
> match the pid in `/var/run/traffic_ops.pid`.
> This needs to be more robust.
> Example:   on my test VM,  if I run this,  I see multiple parent processes:
> {quote}
>  ps -ef | grep script/cdn|grep -v root | awk '\{print $3\}'  | sort -u
>  1
>  22713
>  29306
> {quote}



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

[GitHub] incubator-trafficcontrol issue #823: [TC-374] handle orphan processes in TO ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-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.
---

[GitHub] incubator-trafficcontrol issue #823: [TC-374] handle orphan processes in TO ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/42/



---
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-533) GET /api/$version/deliveryservices/xmlId/#xmlid/sslkeys needs to have tenancy check in place

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-533:
---
Description: 
Tenancy was introduced in 2.1, however, by default it is turned off via the 
use_tenancy parameter but when activated it is used to limit the scope of 
delivery services that a user can act on.

The following APIs needs to check tenancy to ensure users cannot act on ds's 
that they don't have access to.

get("/api/$version/deliveryservices/xmlId/#xmlid/sslkeys
post("/api/$version/deliveryservices/sslkeys/generate
post("/api/$version/deliveryservices/sslkeys/add
get("/api/$version/deliveryservices/xmlId/:xmlid/sslkeys/delete

  was:
Tenancy was introduced in 2.1, however, by default it is turned off via the 
use_tenancy parameter but when activated it is used to limit the scope of 
delivery services that a user can act on.

GET /api/$version/deliveryservices/xmlId/#xmlid/sslkeys needs to check tenancy 
to ensure users cannot view ds info of ds's that they don't have access to.


> GET /api/$version/deliveryservices/xmlId/#xmlid/sslkeys needs to have tenancy 
> check in place
> 
>
> Key: TC-533
> URL: https://issues.apache.org/jira/browse/TC-533
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Nir Sopher
>
> Tenancy was introduced in 2.1, however, by default it is turned off via the 
> use_tenancy parameter but when activated it is used to limit the scope of 
> delivery services that a user can act on.
> The following APIs needs to check tenancy to ensure users cannot act on ds's 
> that they don't have access to.
> get("/api/$version/deliveryservices/xmlId/#xmlid/sslkeys
> post("/api/$version/deliveryservices/sslkeys/generate
> post("/api/$version/deliveryservices/sslkeys/add
> get("/api/$version/deliveryservices/xmlId/:xmlid/sslkeys/delete



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

[jira] [Updated] (TC-533) DS SSL key apis needs to have tenancy check in place

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-533:
---
Summary: DS SSL key apis needs to have tenancy check in place  (was: GET 
/api/$version/deliveryservices/xmlId/#xmlid/sslkeys needs to have tenancy check 
in place)

> DS SSL key apis needs to have tenancy check in place
> 
>
> Key: TC-533
> URL: https://issues.apache.org/jira/browse/TC-533
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Nir Sopher
>
> Tenancy was introduced in 2.1, however, by default it is turned off via the 
> use_tenancy parameter but when activated it is used to limit the scope of 
> delivery services that a user can act on.
> The following APIs needs to check tenancy to ensure users cannot act on ds's 
> that they don't have access to.
> get("/api/$version/deliveryservices/xmlId/#xmlid/sslkeys
> post("/api/$version/deliveryservices/sslkeys/generate
> post("/api/$version/deliveryservices/sslkeys/add
> get("/api/$version/deliveryservices/xmlId/:xmlid/sslkeys/delete



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

[jira] [Commented] (TC-374) `systemctl stop traffic_ops` does not kill all processes

[ASF GitHub Bot (JIRA)]

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

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

GitHub user dangogh opened a pull request:

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

[TC-374] handle orphan processes in TO init.d

allows stop and/or restart of TO in case of orphaned workers.

To test,  find a worker process (`ps -ef | grep 
/opt/traffic_ops/app/scripts/cdn`) and kill with a HUP signal:   `kill -HUP 
5432`

You should see a new process with a parent of 1:

```
$ ps -ef | awk '/^trafops/&&/\/script\/cdn/ { if ($3 == 1) {print} }'
trafops  29881 1  0 18:05 ?00:00:00 
/opt/traffic_ops/app/script/cdn```
```

Restart:
```sudo systemctl restart traffic_ops```

The only `/script/cdn` process with a parent of 1 should be owned by `root` 
and should be the one in the `/var/run/traffic_ops.pid` file.

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

$ git pull https://github.com/dangogh/incubator-trafficcontrol TC-374

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

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


commit c65c2e7d0125e14917341bd8ac05edcb559b5599
Author: Dan Kirkwood 
Date:   2017-08-16T18:31:28Z

handle orphan processes in TO




> `systemctl stop traffic_ops` does not kill all processes
> 
>
> Key: TC-374
> URL: https://issues.apache.org/jira/browse/TC-374
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
>  Labels: systemctl
> Fix For: 2.1.0, 2.2.0
>
>
> not sure why it gets in this state,  but traffic_ops processes sometimes get 
> in a state where the parent process is the root (1) for many of the 
> script/cdn workers.   The init.d script doesn't stop them because they don't 
> match the pid in `/var/run/traffic_ops.pid`.
> This needs to be more robust.
> Example:   on my test VM,  if I run this,  I see multiple parent processes:
> {quote}
>  ps -ef | grep script/cdn|grep -v root | awk '\{print $3\}'  | sort -u
>  1
>  22713
>  29306
> {quote}



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

[GitHub] incubator-trafficcontrol pull request #823: [TC-374] handle orphan processes...

[dangogh]

GitHub user dangogh opened a pull request:

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

[TC-374] handle orphan processes in TO init.d

allows stop and/or restart of TO in case of orphaned workers.

To test,  find a worker process (`ps -ef | grep 
/opt/traffic_ops/app/scripts/cdn`) and kill with a HUP signal:   `kill -HUP 
5432`

You should see a new process with a parent of 1:

```
$ ps -ef | awk '/^trafops/&&/\/script\/cdn/ { if ($3 == 1) {print} }'
trafops  29881 1  0 18:05 ?00:00:00 
/opt/traffic_ops/app/script/cdn```
```

Restart:
```sudo systemctl restart traffic_ops```

The only `/script/cdn` process with a parent of 1 should be owned by `root` 
and should be the one in the `/var/run/traffic_ops.pid` file.

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

$ git pull https://github.com/dangogh/incubator-trafficcontrol TC-374

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

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


commit c65c2e7d0125e14917341bd8ac05edcb559b5599
Author: Dan Kirkwood 
Date:   2017-08-16T18:31:28Z

handle orphan processes in TO




---
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-533) GET /api/$version/deliveryservices/xmlId/#xmlid/sslkeys needs to have tenancy check in place

[Jeremy Mitchell (JIRA)]

Jeremy Mitchell created TC-533:
--

 Summary: GET /api/$version/deliveryservices/xmlId/#xmlid/sslkeys 
needs to have tenancy check in place
 Key: TC-533
 URL: https://issues.apache.org/jira/browse/TC-533
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops API
Affects Versions: 2.1.0
Reporter: Jeremy Mitchell
Assignee: Nir Sopher


Tenancy was introduced in 2.1, however, by default it is turned off via the 
use_tenancy parameter but when activated it is used to limit the scope of 
delivery services that a user can act on.

GET /api/$version/deliveryservices/xmlId/#xmlid/sslkeys needs to check tenancy 
to ensure users cannot view ds info of ds's that they don't have access to.



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

[jira] [Created] (TC-532) PUT /api/$version/deliveryservices/:id/safe needs to have tenancy check in place

[Jeremy Mitchell (JIRA)]

Jeremy Mitchell created TC-532:
--

 Summary: PUT /api/$version/deliveryservices/:id/safe needs to have 
tenancy check in place
 Key: TC-532
 URL: https://issues.apache.org/jira/browse/TC-532
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops API
Affects Versions: 2.1.0
Reporter: Jeremy Mitchell
Assignee: Dylan Volz


Tenancy was introduced in 2.1, however, by default it is turned off via the 
use_tenancy parameter but when activated it is used to limit the scope of 
delivery services that a user can act on. 

PUT /api/$version/deliveryservices/:id/safe needs to check tenancy to ensure 
users do not attempt to update ds's that they don't have access to.





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

[GitHub] incubator-trafficcontrol pull request #822: [TC-82] - removes dead API route...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-82) Eliminate duplicate implementations of deliveryservice, cachegroup and server api endpoints

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-82:
--

Github user asfgit closed the pull request at:

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


> Eliminate duplicate implementations of deliveryservice, cachegroup and server 
> api endpoints
> ---
>
> Key: TC-82
> URL: https://issues.apache.org/jira/browse/TC-82
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: api_endpoints
>
> The following endpoints are duplicates and need to be reconciled:
> Delivery Services:
> GET /api/$version/deliveryservices
> GET /api/$version/deliveryservices/list <-- remove
> GET /api/$version/deliveryservices/:id
> GET /api/$version/deliveryservices/:id/get <-- remove
> POST /api/$version/deliveryservices
> POST /api/$version/deliveryservices/create <-- remove
> PUT /api/$version/deliveryservices/:id
> PUT /api/$version/deliveryservices/:id/update <-- remove
> Cache Groups:
> GET /api/$version/cachegroups
> GET /api/$version/cachegroups/list <-- remove
> POST /api/$version/cachegroups
> POST /api/$version/cachegroups/create <-- remove
> PUT /api/$version/cachegroups/:id
> PUT /api/$version/cachegroups/:id/update <-- remove
> DELETE /api/$version/cachegroups/:id
> DELETE /api/$version/cachegroups/:id/delete <-- remove
> Servers:
> POST /api/$version/servers
> POST /api/$version/servers/create <-- remove
> PUT /api/$version/servers/:id
> PUT /api/$version/servers/:id/update <-- remove



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

[jira] [Commented] (TC-82) Eliminate duplicate implementations of deliveryservice, cachegroup and server api endpoints

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-82:
--

Github user asfgit commented on the issue:

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

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



> Eliminate duplicate implementations of deliveryservice, cachegroup and server 
> api endpoints
> ---
>
> Key: TC-82
> URL: https://issues.apache.org/jira/browse/TC-82
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: api_endpoints
>
> The following endpoints are duplicates and need to be reconciled:
> Delivery Services:
> GET /api/$version/deliveryservices
> GET /api/$version/deliveryservices/list <-- remove
> GET /api/$version/deliveryservices/:id
> GET /api/$version/deliveryservices/:id/get <-- remove
> POST /api/$version/deliveryservices
> POST /api/$version/deliveryservices/create <-- remove
> PUT /api/$version/deliveryservices/:id
> PUT /api/$version/deliveryservices/:id/update <-- remove
> Cache Groups:
> GET /api/$version/cachegroups
> GET /api/$version/cachegroups/list <-- remove
> POST /api/$version/cachegroups
> POST /api/$version/cachegroups/create <-- remove
> PUT /api/$version/cachegroups/:id
> PUT /api/$version/cachegroups/:id/update <-- remove
> DELETE /api/$version/cachegroups/:id
> DELETE /api/$version/cachegroups/:id/delete <-- remove
> Servers:
> POST /api/$version/servers
> POST /api/$version/servers/create <-- remove
> PUT /api/$version/servers/:id
> PUT /api/$version/servers/:id/update <-- remove



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

[GitHub] incubator-trafficcontrol issue #822: [TC-82] - removes dead API routes that ...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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-82) Eliminate duplicate implementations of deliveryservice, cachegroup and server api endpoints

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-82:
--

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/43/



> Eliminate duplicate implementations of deliveryservice, cachegroup and server 
> api endpoints
> ---
>
> Key: TC-82
> URL: https://issues.apache.org/jira/browse/TC-82
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: api_endpoints
>
> The following endpoints are duplicates and need to be reconciled:
> Delivery Services:
> GET /api/$version/deliveryservices
> GET /api/$version/deliveryservices/list <-- remove
> GET /api/$version/deliveryservices/:id
> GET /api/$version/deliveryservices/:id/get <-- remove
> POST /api/$version/deliveryservices
> POST /api/$version/deliveryservices/create <-- remove
> PUT /api/$version/deliveryservices/:id
> PUT /api/$version/deliveryservices/:id/update <-- remove
> Cache Groups:
> GET /api/$version/cachegroups
> GET /api/$version/cachegroups/list <-- remove
> POST /api/$version/cachegroups
> POST /api/$version/cachegroups/create <-- remove
> PUT /api/$version/cachegroups/:id
> PUT /api/$version/cachegroups/:id/update <-- remove
> DELETE /api/$version/cachegroups/:id
> DELETE /api/$version/cachegroups/:id/delete <-- remove
> Servers:
> POST /api/$version/servers
> POST /api/$version/servers/create <-- remove
> PUT /api/$version/servers/:id
> PUT /api/$version/servers/:id/update <-- remove



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

[jira] [Commented] (TC-82) Eliminate duplicate implementations of deliveryservice, cachegroup and server api endpoints

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-82:
--

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/41/



> Eliminate duplicate implementations of deliveryservice, cachegroup and server 
> api endpoints
> ---
>
> Key: TC-82
> URL: https://issues.apache.org/jira/browse/TC-82
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: api_endpoints
>
> The following endpoints are duplicates and need to be reconciled:
> Delivery Services:
> GET /api/$version/deliveryservices
> GET /api/$version/deliveryservices/list <-- remove
> GET /api/$version/deliveryservices/:id
> GET /api/$version/deliveryservices/:id/get <-- remove
> POST /api/$version/deliveryservices
> POST /api/$version/deliveryservices/create <-- remove
> PUT /api/$version/deliveryservices/:id
> PUT /api/$version/deliveryservices/:id/update <-- remove
> Cache Groups:
> GET /api/$version/cachegroups
> GET /api/$version/cachegroups/list <-- remove
> POST /api/$version/cachegroups
> POST /api/$version/cachegroups/create <-- remove
> PUT /api/$version/cachegroups/:id
> PUT /api/$version/cachegroups/:id/update <-- remove
> DELETE /api/$version/cachegroups/:id
> DELETE /api/$version/cachegroups/:id/delete <-- remove
> Servers:
> POST /api/$version/servers
> POST /api/$version/servers/create <-- remove
> PUT /api/$version/servers/:id
> PUT /api/$version/servers/:id/update <-- remove



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

[GitHub] incubator-trafficcontrol issue #822: [TC-82] - removes dead API routes that ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-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.
---

[GitHub] incubator-trafficcontrol issue #822: [TC-82] - removes dead API routes that ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/41/



---
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-521) TPv2 - http-parser dependency cannot be resolved

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-521:
---
Fix Version/s: 2.2.0

> TPv2 - http-parser dependency cannot be resolved 
> -
>
> Key: TC-521
> URL: https://issues.apache.org/jira/browse/TC-521
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Blocker
> Fix For: 2.1.0, 2.2.0
>
>
> Therefore the Traffic Portal build fails.
> More details of the error: https://bugs.centos.org/view.php?id=13669=1



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

[jira] [Updated] (TC-521) TPv2 - http-parser dependency cannot be resolved

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-521:
---
Affects Version/s: 2.2.0

> TPv2 - http-parser dependency cannot be resolved 
> -
>
> Key: TC-521
> URL: https://issues.apache.org/jira/browse/TC-521
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Blocker
> Fix For: 2.1.0, 2.2.0
>
>
> Therefore the Traffic Portal build fails.
> More details of the error: https://bugs.centos.org/view.php?id=13669=1



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

[jira] [Updated] (TC-519) TP - tenants menu item mistakenly removed from TP

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-519:
---
Fix Version/s: 2.2.0

> TP - tenants menu item mistakenly removed from TP
> -
>
> Key: TC-519
> URL: https://issues.apache.org/jira/browse/TC-519
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
> Fix For: 2.1.0, 2.2.0
>
>
> Somehow the tenants menu was mistakenly removed from TP.



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

[jira] [Commented] (TC-82) Eliminate duplicate implementations of deliveryservice, cachegroup and server api endpoints

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-82:
--

GitHub user mitchell852 opened a pull request:

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

[TC-82] - removes dead API routes that must have resurfaced due to a bad 
conflict r…

…esolution

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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-82-removes-dead-routes

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

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


commit c4948a477b3d8de4e04265d23860df0310df8c3a
Author: Jeremy Mitchell 
Date:   2017-08-16T17:01:57Z

removes dead routes that must have resurfaced due to a bad conflict 
resolution




> Eliminate duplicate implementations of deliveryservice, cachegroup and server 
> api endpoints
> ---
>
> Key: TC-82
> URL: https://issues.apache.org/jira/browse/TC-82
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: api_endpoints
>
> The following endpoints are duplicates and need to be reconciled:
> Delivery Services:
> GET /api/$version/deliveryservices
> GET /api/$version/deliveryservices/list <-- remove
> GET /api/$version/deliveryservices/:id
> GET /api/$version/deliveryservices/:id/get <-- remove
> POST /api/$version/deliveryservices
> POST /api/$version/deliveryservices/create <-- remove
> PUT /api/$version/deliveryservices/:id
> PUT /api/$version/deliveryservices/:id/update <-- remove
> Cache Groups:
> GET /api/$version/cachegroups
> GET /api/$version/cachegroups/list <-- remove
> POST /api/$version/cachegroups
> POST /api/$version/cachegroups/create <-- remove
> PUT /api/$version/cachegroups/:id
> PUT /api/$version/cachegroups/:id/update <-- remove
> DELETE /api/$version/cachegroups/:id
> DELETE /api/$version/cachegroups/:id/delete <-- remove
> Servers:
> POST /api/$version/servers
> POST /api/$version/servers/create <-- remove
> PUT /api/$version/servers/:id
> PUT /api/$version/servers/:id/update <-- remove



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

[jira] [Commented] (TC-516) Deleting a DS thru the API should also delete all SSL keys (if applicable)

[Hank Beatty (JIRA)]

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

Hank Beatty commented on TC-516:


[~mitchell...@apache.org] Yeah, I'm going to do that. I just wanted to nail 
down those that we definitely wanted to fix for 2.1 and I think I'm almost 
there.

> Deleting a DS thru the API should also delete all SSL keys (if applicable)
> --
>
> Key: TC-516
> URL: https://issues.apache.org/jira/browse/TC-516
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jeremy Mitchell
> Fix For: 2.1.0, 2.2.0
>
>
> There are currently 4 protocols for a DS:
> 0 - HTTP
> 1 - HTTPS
> 2 - HTTP AND HTTPS
> 3 - HTTP TO HTTPS
> Currently, if you delete a DS thru the API, SSL keys are not deleted. This 
> should occur if ds.protocol > 0.



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

[jira] [Updated] (TC-519) TP - tenants menu item mistakenly removed from TP

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-519:
---
Affects Version/s: 2.2.0

> TP - tenants menu item mistakenly removed from TP
> -
>
> Key: TC-519
> URL: https://issues.apache.org/jira/browse/TC-519
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
> Fix For: 2.1.0, 2.2.0
>
>
> Somehow the tenants menu was mistakenly removed from TP.



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

[jira] [Updated] (TC-516) Deleting a DS thru the API should also delete all SSL keys (if applicable)

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-516:
---
Fix Version/s: 2.2.0
   2.1.0

> Deleting a DS thru the API should also delete all SSL keys (if applicable)
> --
>
> Key: TC-516
> URL: https://issues.apache.org/jira/browse/TC-516
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jeremy Mitchell
> Fix For: 2.1.0, 2.2.0
>
>
> There are currently 4 protocols for a DS:
> 0 - HTTP
> 1 - HTTPS
> 2 - HTTP AND HTTPS
> 3 - HTTP TO HTTPS
> Currently, if you delete a DS thru the API, SSL keys are not deleted. This 
> should occur if ds.protocol > 0.



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

[GitHub] incubator-trafficcontrol pull request #822: [TC-82] - removes dead API route...

[mitchell852]

GitHub user mitchell852 opened a pull request:

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

[TC-82] - removes dead API routes that must have resurfaced due to a bad 
conflict r…

…esolution

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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-82-removes-dead-routes

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

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


commit c4948a477b3d8de4e04265d23860df0310df8c3a
Author: Jeremy Mitchell 
Date:   2017-08-16T17:01:57Z

removes dead routes that must have resurfaced due to a bad conflict 
resolution




---
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-510) cannot apply ipv6 on delivery services

[Dylan Volz (JIRA)]

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

Dylan Volz commented on TC-510:
---

I believe this can be left for 2.2 because updating delivery services with ipv6 
works via the api route, exercised via the new traffic portal. I verified this 
today.

> 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, 2.2.0
>Reporter: Sean Aoyagi
>Assignee: Dylan Volz
> Fix For: 2.1.0, 2.2.0
>
>
> 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-490) mso.qstring_handling parameter is checked but not documented

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-490:
---
Fix Version/s: 2.2.0
   2.1.0

> mso.qstring_handling parameter is checked but not documented
> 
>
> Key: TC-490
> URL: https://issues.apache.org/jira/browse/TC-490
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Priority: Blocker
> Fix For: 2.1.0, 2.2.0
>
>
> mso.qstring_handling not listed in docs, seems to be defined elsewhere as 
> psel.qstring_handling
>but MID parent selection code checks if mso.qstring_handling is not defined
> {code}
>my $qsh= 
> $ds->{'param'}->{'parent.config'}->{'mso.qstring_handling'};
>my $parent_qstring = "ignore"; 
>  # default is ignore, unless for alg consistent_hash
>if ( !defined($qsh) && $mso_algorithm eq 'consistent_hash' && 
> $ds->{qstring_ignore} == 0 ) {
>   $parent_qstring = 'consider';
>}
> {code}
> The parameter is unlikely to ever exist, since it's not documented anywhere, 
> but either way either the code should be corrected or the documentation 
> should be.



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

[jira] [Updated] (TC-515) Traffic Portal - Show human readable protocol on DS page

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-515:
---
Fix Version/s: 2.2.0
   2.1.0

> Traffic Portal - Show human readable protocol on DS page
> 
>
> Key: TC-515
> URL: https://issues.apache.org/jira/browse/TC-515
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0, 2.2.0
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0, 2.2.0
>
>
> In the TO UI, the delivery service protocol is converted from an int (0,1,2) 
> to a human readable string (http, https, http and https, etc).  The new TO 
> portal just shows the int but it should show the human readable string.



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

[jira] [Updated] (TC-516) Deleting a DS thru the API should also delete all SSL keys (if applicable)

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-516:
---
Affects Version/s: 2.2.0

> Deleting a DS thru the API should also delete all SSL keys (if applicable)
> --
>
> Key: TC-516
> URL: https://issues.apache.org/jira/browse/TC-516
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jeremy Mitchell
>
> There are currently 4 protocols for a DS:
> 0 - HTTP
> 1 - HTTPS
> 2 - HTTP AND HTTPS
> 3 - HTTP TO HTTPS
> Currently, if you delete a DS thru the API, SSL keys are not deleted. This 
> should occur if ds.protocol > 0.



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

[jira] [Updated] (TC-514) ORT: Change Traffic Ops hostname in middle of ORT run

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-514:
---
Affects Version/s: 2.2.0

> ORT: Change Traffic Ops hostname in middle of ORT run
> -
>
> Key: TC-514
> URL: https://issues.apache.org/jira/browse/TC-514
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops ORT
>Affects Versions: 2.1.0, 2.2.0
> Environment: Traffic Ops 2.1 and ORT 2.1
>Reporter: Steve Malenfant
>Assignee: Derek Gelinas
>Priority: Minor
> Fix For: 2.2.0
>
>
> I'm not sure if this is 2.1 specifics... Worth discussing.
> - Could this prevent load balancing traffic ops from working?
> - Cookies might be different (you need to sync secrets?). These are in the 
> cdn.conf and not the database...
> When you instruct the traffic_ops_ort to go to a secondary Traffic Ops, it 
> will start on the CLI designated but will move back to the primary during the 
> "Start processing packages" process.
> Code in question : 
> https://github.com/apache/incubator-trafficcontrol/blob/2.1.x/traffic_ops/bin/traffic_ops_ort.pl#L201
> {code:java}
> [root@edge06 ~]# /opt/ort/traffic_ops_ort.pl -dispersion=0 report DEBUG 
> https://traffic-ops-0002.coxlab.net chs:w@term@rk
> Mon Aug 14 13:29:06 UTC 2017
> DEBUG OS release is EL7.
> DEBUG Script running in report mode.
> 302
> DEBUG https://traffic-ops-0002.coxlab.net/login returned HTTP 302.
> DEBUG Cookie is 
> mojolicious=eyJhdXRoX2RhdGEi4iJjaHMiLCJleHBpcmVzIjoxNTAyNzMxNzQ2fQ136010205dc8d4951e2e2194b6b463eb3d141f1e.
> DEBUG YUM_OPTS: .
> DEBUG Total connections in LWP cache: 1
> INFO Traffic Ops host: https://traffic-ops-0002.coxlab.net
> ...
> INFO:  Start processing packages 
> DEBUG Total connections in LWP cache: 1
> INFO Traffic Ops host: https://traffic-ops-0001.coxlab.net
> DEBUG lwp_get called with /ort/psp6cdedge06/packages
> ERROR https://traffic-ops-0001.coxlab.net/ort/edge06/packages returned HTTP 
> 401! Unauthorized 
> ERROR result for https://traffic-ops-0001/ort/psp6cdedge06/packages is: 
> 

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

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-510:
---
Fix Version/s: 2.2.0
   2.1.0

> 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, 2.2.0
>Reporter: Sean Aoyagi
>Assignee: Dylan Volz
> Fix For: 2.1.0, 2.2.0
>
>
> 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-513) Traffic Ops Golang must send Whole-Content-SHA512

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-513:
---
Affects Version/s: 2.2.0
   2.1.0

> Traffic Ops Golang must send Whole-Content-SHA512
> -
>
> Key: TC-513
> URL: https://issues.apache.org/jira/browse/TC-513
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Butts
>Assignee: Robert Butts
> Fix For: 2.1.0
>
>
> Once https://github.com/apache/incubator-trafficcontrol/pull/786 is merged 
> fixing TC-503, TO Golang must send a Whole-Content-SHA512 header, or ORT will 
> fail. (In fact, TO Golang fails without it, with the current MIC.)
> This is necessary for a Message Integrity Check. Previously Content-Length 
> was used, which must not be sent under certain circumstances with HTTP/1.1. 
> See pull/786 and TC-503 for more details.



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

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

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-510:
---
Affects Version/s: 2.2.0

> 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, 2.2.0
>Reporter: Sean Aoyagi
>Assignee: Dylan Volz
> Fix For: 2.1.0, 2.2.0
>
>
> 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-503) Traffic Ops ORT Fails with Chunked Encoding

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-503:
---
Fix Version/s: 2.2.0

> Traffic Ops ORT Fails with Chunked Encoding
> ---
>
> Key: TC-503
> URL: https://issues.apache.org/jira/browse/TC-503
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops ORT
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Butts
>Assignee: Dewayne Richardson
> Fix For: 2.1.0, 2.2.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> ORT fails if no 'Content-Length' header exists.
> 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.
> So far, we've just been lucky Perl/Mojolicious Traffic Ops doesn't happen to 
> send Chunked encodings to ORT. But the spec requires clients accept it, ORT 
> is in violation of HTTP/1.1. 
> Further, the upcoming Golang Traffic Ops sends Chunked encoding, and there's 
> no reasonable way in Go to prevent it. There's no HTTP-compliant way to 
> instruct the server not to send Chunked encoding either, since clients are 
> required to accept it. The right solution here is to fix ORT to accept 
> Chunked encoding, without Content-Length.
> It appears ORT only refuses it as a safety check, and doesn't actually need 
> it for anything. Should be a simple fix.



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

[jira] [Updated] (TC-503) Traffic Ops ORT Fails with Chunked Encoding

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-503:
---
Affects Version/s: 2.2.0

> Traffic Ops ORT Fails with Chunked Encoding
> ---
>
> Key: TC-503
> URL: https://issues.apache.org/jira/browse/TC-503
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops ORT
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Butts
>Assignee: Dewayne Richardson
> Fix For: 2.1.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> ORT fails if no 'Content-Length' header exists.
> 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.
> So far, we've just been lucky Perl/Mojolicious Traffic Ops doesn't happen to 
> send Chunked encodings to ORT. But the spec requires clients accept it, ORT 
> is in violation of HTTP/1.1. 
> Further, the upcoming Golang Traffic Ops sends Chunked encoding, and there's 
> no reasonable way in Go to prevent it. There's no HTTP-compliant way to 
> instruct the server not to send Chunked encoding either, since clients are 
> required to accept it. The right solution here is to fix ORT to accept 
> Chunked encoding, without Content-Length.
> It appears ORT only refuses it as a safety check, and doesn't actually need 
> it for anything. Should be a simple fix.



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

[jira] [Updated] (TC-494) Clone DS assignments button on Server times out

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-494:
---
Fix Version/s: 2.2.0
   2.1.0

> Clone DS assignments button on Server times out
> ---
>
> Key: TC-494
> URL: https://issues.apache.org/jira/browse/TC-494
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Assignee: Dylan Volz
> Fix For: 2.1.0, 2.2.0
>
>
> When you try to clone DS assignments in our current production environment, 
> it will never complete the "clone" process, and gets timed out midway 
> through, leaving you with a broken configuration on that server.



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

[jira] [Updated] (TC-500) Creating/Updating a Delivery Service via API has length constraint on displayName of 48, but no such constraint in UI code

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-500:
---
Affects Version/s: 2.2.0

> Creating/Updating a Delivery Service via API has length constraint on 
> displayName of 48, but no such constraint in UI code
> --
>
> Key: TC-500
> URL: https://issues.apache.org/jira/browse/TC-500
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Priority: Minor
> Fix For: 2.2.0
>
>
> Creating/Updating a Delivery Service via API code has length constraint on 
> `displayName` of 48, but there is no such constraint in the UI code so any 
> user can update the value to more than 48 characters.  The Database field is 
> Text which is described as "variable unlimited length" in the Postgres 
> documentation.  However, the value may be limited by the GUI field if such a 
> constraint exists.
> NOTE:  The GET methods for /api/1.2/deliveryservices does not check the 
> length on the `displayName` field, so, it will return whatever is in the 
> database for `displayName`.
> Work Around: Upon getting the Delivery Service information from the API, in 
> order to update/create the Delivery Service via the API you will need to 
> limit the number of characters in the `displayName` to 48.
> NOTE: Other versions of Traffic Ops may be affected.



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

[jira] [Updated] (TC-500) Creating/Updating a Delivery Service via API has length constraint on displayName of 48, but no such constraint in UI code

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-500:
---
Fix Version/s: 2.2.0

> Creating/Updating a Delivery Service via API has length constraint on 
> displayName of 48, but no such constraint in UI code
> --
>
> Key: TC-500
> URL: https://issues.apache.org/jira/browse/TC-500
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Priority: Minor
> Fix For: 2.2.0
>
>
> Creating/Updating a Delivery Service via API code has length constraint on 
> `displayName` of 48, but there is no such constraint in the UI code so any 
> user can update the value to more than 48 characters.  The Database field is 
> Text which is described as "variable unlimited length" in the Postgres 
> documentation.  However, the value may be limited by the GUI field if such a 
> constraint exists.
> NOTE:  The GET methods for /api/1.2/deliveryservices does not check the 
> length on the `displayName` field, so, it will return whatever is in the 
> database for `displayName`.
> Work Around: Upon getting the Delivery Service information from the API, in 
> order to update/create the Delivery Service via the API you will need to 
> limit the number of characters in the `displayName` to 48.
> NOTE: Other versions of Traffic Ops may be affected.



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

[jira] [Updated] (TC-492) Deleting Delivery Service with associated static dns entry(s) in staticdnsentry table fails due to foreign key constraint violation

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-492:
---
Affects Version/s: 2.2.0

> Deleting Delivery Service with associated static dns entry(s) in 
> staticdnsentry table fails due to foreign key constraint violation
> ---
>
> Key: TC-492
> URL: https://issues.apache.org/jira/browse/TC-492
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Assignee: Jeremy Mitchell
>Priority: Critical
> Fix For: 2.1.0, 2.2.0
>
>
> Deleting Delivery Service with associated static dns entry in staticdnsentry 
> table fails due to foreign key constraint violation.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table "deliveryservice" violates foreign 
> key constraint "fk_staticdnsentry_ds" on table "staticdnsentry"
> DETAIL:  Key (id)=(180) is still referenced from table "staticdnsentry". [for 
> Statement "DELETE FROM deliveryservice WHERE ( id = ? )" with ParamValues: 
> 1='180'] at /opt/traffic_ops/app/lib/API/Deliveryservice.pm line 642
> Workaround: Use the UI to remove the association(s) before deleting the 
> delivery service.
> NOTE: Other versions of Traffic Ops may be affected.



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

[jira] [Updated] (TC-492) Deleting Delivery Service with associated static dns entry(s) in staticdnsentry table fails due to foreign key constraint violation

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-492:
---
Fix Version/s: 2.2.0
   2.1.0

> Deleting Delivery Service with associated static dns entry(s) in 
> staticdnsentry table fails due to foreign key constraint violation
> ---
>
> Key: TC-492
> URL: https://issues.apache.org/jira/browse/TC-492
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Assignee: Jeremy Mitchell
>Priority: Critical
> Fix For: 2.1.0, 2.2.0
>
>
> Deleting Delivery Service with associated static dns entry in staticdnsentry 
> table fails due to foreign key constraint violation.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table "deliveryservice" violates foreign 
> key constraint "fk_staticdnsentry_ds" on table "staticdnsentry"
> DETAIL:  Key (id)=(180) is still referenced from table "staticdnsentry". [for 
> Statement "DELETE FROM deliveryservice WHERE ( id = ? )" with ParamValues: 
> 1='180'] at /opt/traffic_ops/app/lib/API/Deliveryservice.pm line 642
> Workaround: Use the UI to remove the association(s) before deleting the 
> delivery service.
> NOTE: Other versions of Traffic Ops may be affected.



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

[jira] [Updated] (TC-491) Deleting Delivery Service with associated job in job table fails due to foreign key constraint violation

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-491:
---
Fix Version/s: 2.2.0
   2.1.0

> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation
> 
>
> Key: TC-491
> URL: https://issues.apache.org/jira/browse/TC-491
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Assignee: Jeremy Mitchell
>Priority: Critical
> Fix For: 2.1.0, 2.2.0
>
>
> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation.
> E.g.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table "deliveryservice" violates foreign 
> key constraint "fk_job_deliveryservice1" on table "job"
> DETAIL:  Key (id)=(714) is still referenced from table "job". [for Statement 
> "DELETE FROM deliveryservice WHERE ( id = ? )" with ParamValues: 1='714'] at 
> /opt/traffic_ops/app/lib/API/Deliveryservice.pm line 642
> Workaround: No UI/API end-point to delete the associated job.  Delete 
> associated job from database.
> NOTE: Other Traffic Ops versions may also be affected.



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

[jira] [Updated] (TC-490) mso.qstring_handling parameter is checked but not documented

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-490:
---
Affects Version/s: 2.2.0

> mso.qstring_handling parameter is checked but not documented
> 
>
> Key: TC-490
> URL: https://issues.apache.org/jira/browse/TC-490
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Priority: Blocker
> Fix For: 2.1.0, 2.2.0
>
>
> mso.qstring_handling not listed in docs, seems to be defined elsewhere as 
> psel.qstring_handling
>but MID parent selection code checks if mso.qstring_handling is not defined
> {code}
>my $qsh= 
> $ds->{'param'}->{'parent.config'}->{'mso.qstring_handling'};
>my $parent_qstring = "ignore"; 
>  # default is ignore, unless for alg consistent_hash
>if ( !defined($qsh) && $mso_algorithm eq 'consistent_hash' && 
> $ds->{qstring_ignore} == 0 ) {
>   $parent_qstring = 'consider';
>}
> {code}
> The parameter is unlikely to ever exist, since it's not documented anywhere, 
> but either way either the code should be corrected or the documentation 
> should be.



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

[jira] [Updated] (TC-491) Deleting Delivery Service with associated job in job table fails due to foreign key constraint violation

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-491:
---
Affects Version/s: 2.2.0

> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation
> 
>
> Key: TC-491
> URL: https://issues.apache.org/jira/browse/TC-491
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Robert Scrimo
>Assignee: Jeremy Mitchell
>Priority: Critical
>
> Deleting Delivery Service with associated job in job table fails due to 
> foreign key constraint violation.
> E.g.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table "deliveryservice" violates foreign 
> key constraint "fk_job_deliveryservice1" on table "job"
> DETAIL:  Key (id)=(714) is still referenced from table "job". [for Statement 
> "DELETE FROM deliveryservice WHERE ( id = ? )" with ParamValues: 1='714'] at 
> /opt/traffic_ops/app/lib/API/Deliveryservice.pm line 642
> Workaround: No UI/API end-point to delete the associated job.  Delete 
> associated job from database.
> NOTE: Other Traffic Ops versions may also be affected.



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

[jira] [Updated] (TC-489) Multi Site Origin - Invalid default values for multiple config params

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-489:
---
Affects Version/s: 2.2.0

> Multi Site Origin - Invalid default values for multiple config params
> -
>
> Key: TC-489
> URL: https://issues.apache.org/jira/browse/TC-489
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Priority: Blocker
> Fix For: 2.1.0, 2.2.0
>
>
> Several of the multi site origin parameters default to 0 (including 
> mso.algorithm, possibly others ), which is an invalid argument.
>valid values: true, strict, proxy1, false, consistent_hash
>
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Configs/ApacheTrafficServer.pm#L2051
> {code}
>L2051: $text .= "$parents round_robin=$mso_algorithm 
> qstring=$parent_qstring go_direct=false parent_is_proxy=false";
> {code}
> {code}
>parent.config: dest_domain=google.com port=443 ... round_robin=0 ...
> {code}
> {code}
>[Jul 12 02:25:45.987] Server {0x2b54fb7db940} ERROR: [ParentSelection] 
> invalid argument to round_robin directive at line 2
> {code}



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

[jira] [Updated] (TC-488) Docs - Multi Site Origin not up to date

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-488:
---
Fix Version/s: 2.2.0
   2.1.0

> Docs - Multi Site Origin not up to date
> ---
>
> Key: TC-488
> URL: https://issues.apache.org/jira/browse/TC-488
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Priority: Blocker
> Fix For: 2.1.0, 2.2.0
>
>
> Current documentation for multi site origin is confusing/wrong/out of date:
>
> https://github.com/apache/incubator-trafficcontrol/blob/master/docs/source/admin/quick_howto/multi_site.rst
>Bottom has steps that references configuration that I think has been 
> replaced with delivery service profiles.
>
> https://github.com/apache/incubator-trafficcontrol/blob/master/docs/source/admin/traffic_ops/using.rst
>mentions the new delivery service profile pieces, but not the cachegroup 
> side of multi-site configuration.



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

[jira] [Updated] (TC-489) Multi Site Origin - Invalid default values for multiple config params

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-489:
---
Fix Version/s: 2.2.0
   2.1.0

> Multi Site Origin - Invalid default values for multiple config params
> -
>
> Key: TC-489
> URL: https://issues.apache.org/jira/browse/TC-489
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Priority: Blocker
> Fix For: 2.1.0, 2.2.0
>
>
> Several of the multi site origin parameters default to 0 (including 
> mso.algorithm, possibly others ), which is an invalid argument.
>valid values: true, strict, proxy1, false, consistent_hash
>
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Configs/ApacheTrafficServer.pm#L2051
> {code}
>L2051: $text .= "$parents round_robin=$mso_algorithm 
> qstring=$parent_qstring go_direct=false parent_is_proxy=false";
> {code}
> {code}
>parent.config: dest_domain=google.com port=443 ... round_robin=0 ...
> {code}
> {code}
>[Jul 12 02:25:45.987] Server {0x2b54fb7db940} ERROR: [ParentSelection] 
> invalid argument to round_robin directive at line 2
> {code}



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

[jira] [Updated] (TC-488) Docs - Multi Site Origin not up to date

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-488:
---
Affects Version/s: 2.2.0

> Docs - Multi Site Origin not up to date
> ---
>
> Key: TC-488
> URL: https://issues.apache.org/jira/browse/TC-488
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Priority: Blocker
> Fix For: 2.1.0, 2.2.0
>
>
> Current documentation for multi site origin is confusing/wrong/out of date:
>
> https://github.com/apache/incubator-trafficcontrol/blob/master/docs/source/admin/quick_howto/multi_site.rst
>Bottom has steps that references configuration that I think has been 
> replaced with delivery service profiles.
>
> https://github.com/apache/incubator-trafficcontrol/blob/master/docs/source/admin/traffic_ops/using.rst
>mentions the new delivery service profile pieces, but not the cachegroup 
> side of multi-site configuration.



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

[jira] [Updated] (TC-487) Multi Site Origin config gets applied even when no valid parents

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-487:
---
Affects Version/s: 2.2.0

> Multi Site Origin config gets applied even when no valid parents
> 
>
> Key: TC-487
> URL: https://issues.apache.org/jira/browse/TC-487
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Priority: Minor
> Fix For: 2.2.0
>
>
> If MSO is not properly configured with origin servers but is configured with 
> multi site origin, it will install the multi site origin parent.config with 
> no parent servers listed.
>(Mine had the origin servers in a non ORG type cache group, this generated 
> parent="" in the config)
>parent.config: dest_domain=google.com port=443 parent="" ...
>Jul 12 01:26:46 lab-ats-mid-2.local traffic_server[3916]: {0x2ae9206f1940} 
> ERROR: [ParentSelection] No parents specified at line 2



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

[jira] [Updated] (TC-487) Multi Site Origin config gets applied even when no valid parents

[Hank Beatty (JIRA)]

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

Hank Beatty updated TC-487:
---
Fix Version/s: 2.2.0

> Multi Site Origin config gets applied even when no valid parents
> 
>
> Key: TC-487
> URL: https://issues.apache.org/jira/browse/TC-487
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Matt Mills
>Priority: Minor
> Fix For: 2.2.0
>
>
> If MSO is not properly configured with origin servers but is configured with 
> multi site origin, it will install the multi site origin parent.config with 
> no parent servers listed.
>(Mine had the origin servers in a non ORG type cache group, this generated 
> parent="" in the config)
>parent.config: dest_domain=google.com port=443 parent="" ...
>Jul 12 01:26:46 lab-ats-mid-2.local traffic_server[3916]: {0x2ae9206f1940} 
> ERROR: [ParentSelection] No parents specified at line 2



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