[jira] [Commented] (TC-255) Manage SSL Keys button results in an error for a DS that doesn't already have keys.

[ASF GitHub Bot (JIRA)]

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

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

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/522
  
@mitchell852  That error is coming from 
`/incubator-trafficcontrol/traffic_ops/app/lib/UI/DnssecKeys.pm line 242` which 
I did not change in my PR.


> Manage SSL Keys button results in an error for a DS that doesn't already have 
> keys.
> ---
>
> Key: TC-255
> URL: https://issues.apache.org/jira/browse/TC-255
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: David Neuman
>Assignee: David Neuman
>Priority: Critical
> Fix For: 2.1.0
>
>
> If you have a deliveryservice that you are migrating to HTTPS or a DS that is 
> HTTPS but doesn't yet have keys, you get an error when you click the "Manage 
> SSL Keys" button.  The issue is that there was a method, get_cdn_domain() 
> that was removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol issue #522: [TC-255] and [TC-256] -- Fixes issues w...

[dneuman64]

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/522
  
@mitchell852  That error is coming from 
`/incubator-trafficcontrol/traffic_ops/app/lib/UI/DnssecKeys.pm line 242` which 
I did not change in my PR.


---
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-255) Manage SSL Keys button results in an error for a DS that doesn't already have keys.

[ASF GitHub Bot (JIRA)]

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

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

Github user mitchell852 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/522
  
for this error:

 column reference "id" is ambiguous so change that query to 
my $profile = $self->db->resultset('Profile')->search( { 'me.id' => 
$profile_id }

^^ me.id




> Manage SSL Keys button results in an error for a DS that doesn't already have 
> keys.
> ---
>
> Key: TC-255
> URL: https://issues.apache.org/jira/browse/TC-255
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: David Neuman
>Assignee: David Neuman
>Priority: Critical
> Fix For: 2.1.0
>
>
> If you have a deliveryservice that you are migrating to HTTPS or a DS that is 
> HTTPS but doesn't yet have keys, you get an error when you click the "Manage 
> SSL Keys" button.  The issue is that there was a method, get_cdn_domain() 
> that was removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-258) setup_kabletown.pl needs to be updated

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood resolved TC-258.
-
Resolution: Fixed
  Assignee: Dan Kirkwood

> setup_kabletown.pl needs to be updated
> --
>
> Key: TC-258
> URL: https://issues.apache.org/jira/browse/TC-258
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
>
> app/bin/db/setup_kabletown.pl loads data from app/lib/Fixtures (via 
> lib/Test/IntegrationHelper.pm), but appears to be out of date.   Several 
> issues:
> - sub teardown {} tries to delete all rows from a table,  but doesn't succeed 
> many times with postgresql -- possibly because of foreign key constraints. 
> Suggest using a TRUNCATE table CASCADE sql command rather than 
> $resultset->delete_all
> - sub unload_core_data {} runs teardown on a bunch of tables, but doesn't 
> list all of them.   May be leftover data.
> - new unique constraints are violated by parameter and profile_parameter data 
> in the Fixtures.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-264) Traffic Monitor Proxy should not be part of default parameter

[Dewayne Richardson (JIRA)]

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

Dewayne Richardson resolved TC-264.
---
   Resolution: Fixed
Fix Version/s: 2.1.0

Removed the tm.traffic_mon_fwd_proxy from a fresh install in post install

> Traffic Monitor Proxy should not be part of default parameter 
> --
>
> Key: TC-264
> URL: https://issues.apache.org/jira/browse/TC-264
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Steve Malenfant
>Assignee: Dewayne Richardson
>Priority: Minor
>  Labels: documentation, newbie
> Fix For: 2.1.0
>
>
> During Traffic Portal integration, the API could not reach Traffic Ops. Found 
> out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter 
> was defined as orphaned variable and was actually being used. 
> Few things :
> 1 - This parameter is set at install as an orphan. 
> 2 - This parameter is used even if not assigned to the GLOBAL profile
> 3 - The code is silent about the proxy not being reachable
> 4 - The documentation doesn't mention that parameter and which component uses 
> it.
> I would suggest the following :
> 1 - Removed from default parameter install AND/OR 2)
> 2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not 
> assigned to a profile should not be used.
> 3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used 
> and show the failed proxy requests
> 4 - Mention that profile parameter in the documentation 
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (TC-264) Traffic Monitor Proxy should not be part of default parameter

[Dewayne Richardson (JIRA)]

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

Dewayne Richardson reassigned TC-264:
-

Assignee: Dewayne Richardson

> Traffic Monitor Proxy should not be part of default parameter 
> --
>
> Key: TC-264
> URL: https://issues.apache.org/jira/browse/TC-264
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Steve Malenfant
>Assignee: Dewayne Richardson
>Priority: Minor
>  Labels: documentation, newbie
>
> During Traffic Portal integration, the API could not reach Traffic Ops. Found 
> out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter 
> was defined as orphaned variable and was actually being used. 
> Few things :
> 1 - This parameter is set at install as an orphan. 
> 2 - This parameter is used even if not assigned to the GLOBAL profile
> 3 - The code is silent about the proxy not being reachable
> 4 - The documentation doesn't mention that parameter and which component uses 
> it.
> I would suggest the following :
> 1 - Removed from default parameter install AND/OR 2)
> 2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not 
> assigned to a profile should not be used.
> 3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used 
> and show the failed proxy requests
> 4 - Mention that profile parameter in the documentation 
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TC-264) Traffic Monitor Proxy should not be part of default parameter

[Dewayne Richardson (JIRA)]

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

Dewayne Richardson commented on TC-264:
---

This is fixed in master, so will be in 2.1

> Traffic Monitor Proxy should not be part of default parameter 
> --
>
> Key: TC-264
> URL: https://issues.apache.org/jira/browse/TC-264
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Steve Malenfant
>Priority: Minor
>  Labels: documentation, newbie
>
> During Traffic Portal integration, the API could not reach Traffic Ops. Found 
> out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter 
> was defined as orphaned variable and was actually being used. 
> Few things :
> 1 - This parameter is set at install as an orphan. 
> 2 - This parameter is used even if not assigned to the GLOBAL profile
> 3 - The code is silent about the proxy not being reachable
> 4 - The documentation doesn't mention that parameter and which component uses 
> it.
> I would suggest the following :
> 1 - Removed from default parameter install AND/OR 2)
> 2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not 
> assigned to a profile should not be used.
> 3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used 
> and show the failed proxy requests
> 4 - Mention that profile parameter in the documentation 
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TC-264) Traffic Monitor Proxy should not be part of default parameter

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Traffic Monitor Proxy should not be part of default parameter 
> --
>
> Key: TC-264
> URL: https://issues.apache.org/jira/browse/TC-264
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Steve Malenfant
>Priority: Minor
>  Labels: documentation, newbie
>
> During Traffic Portal integration, the API could not reach Traffic Ops. Found 
> out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter 
> was defined as orphaned variable and was actually being used. 
> Few things :
> 1 - This parameter is set at install as an orphan. 
> 2 - This parameter is used even if not assigned to the GLOBAL profile
> 3 - The code is silent about the proxy not being reachable
> 4 - The documentation doesn't mention that parameter and which component uses 
> it.
> I would suggest the following :
> 1 - Removed from default parameter install AND/OR 2)
> 2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not 
> assigned to a profile should not be used.
> 3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used 
> and show the failed proxy requests
> 4 - Mention that profile parameter in the documentation 
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #534: removed tm.traffic_mon_fwd_proxy...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-264) Traffic Monitor Proxy should not be part of default parameter

[ASF GitHub Bot (JIRA)]

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

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

GitHub user dewrich opened a pull request:

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

removed tm.traffic_mon_fwd_proxy per TC-264



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

$ git pull https://github.com/dewrich/incubator-trafficcontrol TC-264

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

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






> Traffic Monitor Proxy should not be part of default parameter 
> --
>
> Key: TC-264
> URL: https://issues.apache.org/jira/browse/TC-264
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Steve Malenfant
>Priority: Minor
>  Labels: documentation, newbie
>
> During Traffic Portal integration, the API could not reach Traffic Ops. Found 
> out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter 
> was defined as orphaned variable and was actually being used. 
> Few things :
> 1 - This parameter is set at install as an orphan. 
> 2 - This parameter is used even if not assigned to the GLOBAL profile
> 3 - The code is silent about the proxy not being reachable
> 4 - The documentation doesn't mention that parameter and which component uses 
> it.
> I would suggest the following :
> 1 - Removed from default parameter install AND/OR 2)
> 2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not 
> assigned to a profile should not be used.
> 3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used 
> and show the failed proxy requests
> 4 - Mention that profile parameter in the documentation 
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #534: removed tm.traffic_mon_fwd_proxy...

[dewrich]

GitHub user dewrich opened a pull request:

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

removed tm.traffic_mon_fwd_proxy per TC-264



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

$ git pull https://github.com/dewrich/incubator-trafficcontrol TC-264

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

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






---
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-264) Traffic Monitor Proxy should not be part of default parameter

[Steve Malenfant (JIRA)]

Steve Malenfant created TC-264:
--

 Summary: Traffic Monitor Proxy should not be part of default 
parameter 
 Key: TC-264
 URL: https://issues.apache.org/jira/browse/TC-264
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops
Affects Versions: 1.8.0
Reporter: Steve Malenfant
Priority: Minor


During Traffic Portal integration, the API could not reach Traffic Ops. Found 
out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter was 
defined as orphaned variable and was actually being used. 

Few things :

1 - This parameter is set at install as an orphan. 
2 - This parameter is used even if not assigned to the GLOBAL profile
3 - The code is silent about the proxy not being reachable
4 - The documentation doesn't mention that parameter and which component uses 
it.

I would suggest the following :

1 - Removed from default parameter install AND/OR 2)
2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not 
assigned to a profile should not be used.
3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used 
and show the failed proxy requests
4 - Mention that profile parameter in the documentation 


 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #533: [TC-64] - TO experimental - impl...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-263) TO API - fetching deliveryservices by type returns internal server error

[Jeremy Mitchell (JIRA)]

Jeremy Mitchell created TC-263:
--

 Summary: TO API - fetching deliveryservices by type returns 
internal server error
 Key: TC-263
 URL: https://issues.apache.org/jira/browse/TC-263
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops API
Reporter: Jeremy Mitchell
Assignee: Jeremy Mitchell
Priority: Minor
 Fix For: 2.1.0


GET /api/version/deliveryservices?type=typeId returns internal server error. 

[2017-05-01 10:39:10,604] [ERROR] DBIx::Class::Storage::DBI::_dbh_execute(): 
DBI Exception: DBD::Pg::st execute failed: ERROR:  column reference "type" is 
ambiguous



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TC-64) TO experimental SPA application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-64:
--

Github user asfgit closed the pull request at:

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


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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #529: [TC-64] - TO exp - fixes bug in ...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Commented] (TC-64) TO experimental SPA application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-64:
--

GitHub user mitchell852 opened a pull request:

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

[TC-64] - TO experimental - implements 1 way binding where possible to 
avoid creating uneccessary…

… data watchers

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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-64-performance-boosts

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

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


commit 5d1ad7dc02f03a6929c7b6a1c733e0172e4ef4da
Author: Jeremy Mitchell 
Date:   2017-05-01T16:30:46Z

implements 1 way binding where possible to avoid creating uneccessary data 
watchers




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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-234) TO postinstall error moving coverage-zone.json

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood resolved TC-234.
-
Resolution: Fixed

This was resolved in https://github.com/apache/incubator-trafficcontrol/pull/468

and backported to  2.0.x: 
https://github.com/apache/incubator-trafficcontrol/pull/490

> TO postinstall error moving coverage-zone.json
> --
>
> Key: TC-234
> URL: https://issues.apache.org/jira/browse/TC-234
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0
>Reporter: Dan Kirkwood
> Fix For: 2.0.0
>
>
> This is a regression from 1.8.x -- if answering "no" to "Download MaxMind 
> data", I get this message from postinstall:
> Not downloading Maxmind data
> Copying coverage zone file to public dir
> /bin/mv: cannot stat ‘/opt/traffic_ops/app/public/coverage-zone.json’: No 
> such file or directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TC-167) api/1.1/cachegroupparameter.t test fails

[ASF GitHub Bot (JIRA)]

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

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

GitHub user dangogh opened a pull request:

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

[Backport TC-167] 2.0.x fix cachegroupparameter.t



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
2.0-fix-old-test

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

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


commit 628dc8ee612fad550966676376416ed15e2b3deb
Author: Jan van Doorn 
Date:   2017-02-25T22:16:42Z

[TC-167] fix old test; not sure how it ever worked.

(cherry picked from commit aa01b7c0f5563164e0f864a5e3009db42d3ca425)

commit 30e2f807b6db464bf43a86eec2797384637c6b63
Author: Jan van Doorn 
Date:   2017-02-27T14:52:01Z

Order of second thing is still arbitrary

(cherry picked from commit 89e64ecb1bcc1dfc7df08162088394b73e6766b3)




> api/1.1/cachegroupparameter.t test fails 
> -
>
> Key: TC-167
> URL: https://issues.apache.org/jira/browse/TC-167
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0
>Reporter: Jan van Doorn
>Assignee: Jan van Doorn
>Priority: Minor
> Fix For: 2.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #532: [Backport TC-167] 2.0.x fix cach...

[dangogh]

GitHub user dangogh opened a pull request:

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

[Backport TC-167] 2.0.x fix cachegroupparameter.t



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
2.0-fix-old-test

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

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


commit 628dc8ee612fad550966676376416ed15e2b3deb
Author: Jan van Doorn 
Date:   2017-02-25T22:16:42Z

[TC-167] fix old test; not sure how it ever worked.

(cherry picked from commit aa01b7c0f5563164e0f864a5e3009db42d3ca425)

commit 30e2f807b6db464bf43a86eec2797384637c6b63
Author: Jan van Doorn 
Date:   2017-02-27T14:52:01Z

Order of second thing is still arbitrary

(cherry picked from commit 89e64ecb1bcc1dfc7df08162088394b73e6766b3)




---
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 #531: remove KEYS -- stored in dist.ap...

[dangogh]

GitHub user dangogh opened a pull request:

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

remove KEYS -- stored in dist.apache.org svn repo



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
2.0-remove-KEYS

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

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


commit 3329cb0bdc656ef7973f00aeac273e3dbbb71a99
Author: Dan Kirkwood 
Date:   2017-05-01T16:00:10Z

remove KEYS -- stored in dist.apache.org svn repo




---
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-150) generateCert script not echoing prompts from openssl

[ASF GitHub Bot (JIRA)]

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

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

GitHub user dangogh opened a pull request:

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

[Backport TC-150] 2.0 document cert generation



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
2.0-document-cert

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

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


commit 788bb7cba492bcf1f207438dad358c54097183a0
Author: Robert Scrimo 
Date:   2017-03-27T22:28:08Z

Added manual procedure for generating dev and prod certs in traffic ops 
install wiki.

(cherry picked from commit 16fa0ea8835adabd64a9fe4e378762bee86af35b)

commit fb89ebddccdebedb876dab3ea5885bb1384f9434
Author: Robert Scrimo 
Date:   2017-03-28T00:52:14Z

Minor change to a note.

(cherry picked from commit 49177a734e24cad85e772255fb3195c68b6a7ba1)




> generateCert script not echoing prompts from openssl
> 
>
> Key: TC-150
> URL: https://issues.apache.org/jira/browse/TC-150
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0, 2.1.0
> Environment: New install on Centos 7
>Reporter: Dan Kirkwood
>Priority: Minor
> Fix For: 2.0.0, 2.1.0
>
>
> using the script to generate certs,  the initial prompts are shown,  but when 
> it gets to asking for city, state, organization, etc,  the prompt isn't shown 
> and appears to hang.  Hit  9 times, and it shows the next prompt 
> after that portion..
> This should be trivial to fix...Script is 
> traffic_ops/install/bin/generateCert



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #530: [Backport TC-150] 2.0 document c...

[dangogh]

GitHub user dangogh opened a pull request:

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

[Backport TC-150] 2.0 document cert generation



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
2.0-document-cert

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

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


commit 788bb7cba492bcf1f207438dad358c54097183a0
Author: Robert Scrimo 
Date:   2017-03-27T22:28:08Z

Added manual procedure for generating dev and prod certs in traffic ops 
install wiki.

(cherry picked from commit 16fa0ea8835adabd64a9fe4e378762bee86af35b)

commit fb89ebddccdebedb876dab3ea5885bb1384f9434
Author: Robert Scrimo 
Date:   2017-03-28T00:52:14Z

Minor change to a note.

(cherry picked from commit 49177a734e24cad85e772255fb3195c68b6a7ba1)




---
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] [Closed] (TC-251) DNSSEC keys refresh doesn't work

[David Neuman (JIRA)]

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

David Neuman closed TC-251.
---

This was merged, closing

> DNSSEC keys refresh doesn't work
> 
>
> Key: TC-251
> URL: https://issues.apache.org/jira/browse/TC-251
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0, 2.1.0
>Reporter: David Neuman
>Assignee: David Neuman
> Fix For: 2.0.0, 2.1.0
>
>
> They DNSSEC keys route doesn't work.  It never returns a reponse to the 
> client, so the client times out, and it also isn't actually updating the 
> expired keys.  I think the client issues was introduced with changes to the 
> "fork_and_daemonize()" method.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-203) Mojo doesn't set cacheable headers on the /public static files.

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood resolved TC-203.
-
Resolution: Fixed

This was merged and backported to 2.0.x

> Mojo doesn't set cacheable headers on the /public static files.
> ---
>
> Key: TC-203
> URL: https://issues.apache.org/jira/browse/TC-203
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Jan van Doorn
>Assignee: Jan van Doorn
> Fix For: 2.0.0
>
>
> All /public objects (images, css, js) are not being cached by the browser 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (TC-188) postinstall -r option should be removed

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood updated TC-188:

Affects Version/s: 2.1.0
   2.0.0
Fix Version/s: (was: 2.0.0)
   2.1.0

-r has no effect at this point,  but not worth back-porting change to actually 
remove the option.  Moved to 2.1.

> postinstall -r option should be removed
> ---
>
> Key: TC-188
> URL: https://issues.apache.org/jira/browse/TC-188
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0, 2.0.0, 2.1.0
>Reporter: Peter Ryder
>Priority: Minor
> Fix For: 2.1.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> With the changes to postinstall, a -r option was introduced to remove a 
> hidden file on the system which determined when to reconfigure the database. 
> Since postinstall is only run during initial installs, it only makes sense to 
> always run in reconfigure mode. If postinstall is run a second time, it will 
> look for files it creates on the system and will warn the user before 
> continuing that their database will be recreated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-185) postinstall doesn't run due to missing perl module

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood resolved TC-185.
-
Resolution: Fixed

> postinstall doesn't run due to missing perl module
> --
>
> Key: TC-185
> URL: https://issues.apache.org/jira/browse/TC-185
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0
> Environment: CentOS 7
>Reporter: Hank Beatty
>Priority: Minor
> Fix For: 2.0.0
>
>
> I did a minimal install of CentOS 7, installed TO, when I run postinstall I 
> get:
> # ./postinstall Can't locate Term/ReadPassword.pm in @INC (@INC contains: 
> /opt/traffic_ops/install/lib /opt/traffic_ops/install/lib/perl5 
> /opt/traffic_ops/app/local/lib/perl5 /opt/traffic_ops/app/lib 
> /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl 
> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at 
> /opt/traffic_ops/install/lib/InstallUtils.pm line 37. BEGIN 
> failed--compilation aborted at /opt/traffic_ops/install/lib/InstallUtils.pm 
> line 37.
> This perl module isn't available via yum.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TC-185) postinstall doesn't run due to missing perl module

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood commented on TC-185:
-

Resolved by  https://github.com/apache/incubator-trafficcontrol/pull/468

Cherry-picked to 2.0.x: 
https://github.com/apache/incubator-trafficcontrol/commit/c43f6aa8dfdd0858c30d1ccd5592b9b6eb7caa38

> postinstall doesn't run due to missing perl module
> --
>
> Key: TC-185
> URL: https://issues.apache.org/jira/browse/TC-185
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0
> Environment: CentOS 7
>Reporter: Hank Beatty
>Priority: Minor
> Fix For: 2.0.0
>
>
> I did a minimal install of CentOS 7, installed TO, when I run postinstall I 
> get:
> # ./postinstall Can't locate Term/ReadPassword.pm in @INC (@INC contains: 
> /opt/traffic_ops/install/lib /opt/traffic_ops/install/lib/perl5 
> /opt/traffic_ops/app/local/lib/perl5 /opt/traffic_ops/app/lib 
> /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl 
> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at 
> /opt/traffic_ops/install/lib/InstallUtils.pm line 37. BEGIN 
> failed--compilation aborted at /opt/traffic_ops/install/lib/InstallUtils.pm 
> line 37.
> This perl module isn't available via yum.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-251) DNSSEC keys refresh doesn't work

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood resolved TC-251.
-
Resolution: Fixed

> DNSSEC keys refresh doesn't work
> 
>
> Key: TC-251
> URL: https://issues.apache.org/jira/browse/TC-251
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0, 2.1.0
>Reporter: David Neuman
>Assignee: David Neuman
> Fix For: 2.0.0, 2.1.0
>
>
> They DNSSEC keys route doesn't work.  It never returns a reponse to the 
> client, so the client times out, and it also isn't actually updating the 
> expired keys.  I think the client issues was introduced with changes to the 
> "fork_and_daemonize()" method.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-228) TO: postinstall changes needed for postgres

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood resolved TC-228.
-
Resolution: Fixed
  Assignee: Dan Kirkwood

> TO: postinstall changes needed for postgres
> ---
>
> Key: TC-228
> URL: https://issues.apache.org/jira/browse/TC-228
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 2.0.0
>
>
> more changes needed to get postinstall working correctly for a postgres 
> installation.
> This is needed for 2.0.x release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-232) TO postinstall fails with 401 Unauthorized

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood resolved TC-232.
-
Resolution: Fixed
  Assignee: Dan Kirkwood

> TO postinstall fails with 401 Unauthorized
> --
>
> Key: TC-232
> URL: https://issues.apache.org/jira/browse/TC-232
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 2.0.0
>
>
> Running postinstall immediately after initial  traffic_ops install,  I get 
> this error after traffic_ops is started:
> Checking profiles at https://localhost using username admin
> Error checking if profiles exist: 401 Unauthorized



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (TC-6) Traffic Ops postinstall: non-interactive configuration

[Dan Kirkwood (JIRA)]

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

Dan Kirkwood resolved TC-6.
---
Resolution: Fixed

> Traffic Ops postinstall: non-interactive configuration
> --
>
> Key: TC-6
> URL: https://issues.apache.org/jira/browse/TC-6
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 2.0.0
>
> Attachments: Automated_Postinstall_for_Traffic_Ops_v4.docx
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Traffic Ops postinstall currently requires interactive user input.   This 
> makes it difficult to install exactly the same way each time,  and can be 
> error prone.  It also makes installation within a docker container difficult.
> There should be a way to get this same input from a file that can be 
> configured ahead of time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)