[jira] [Created] (TC-502) ORT fails to handle non-file arguments

[Chris Lemmons (JIRA)]

Chris Lemmons created TC-502:


 Summary: ORT fails to handle non-file arguments
 Key: TC-502
 URL: https://issues.apache.org/jira/browse/TC-502
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops ORT
Reporter: Chris Lemmons


ORT currently processes the parameters of all plugins on the remap.config line 
as though they were files. However, parameters to `cachekey.config` are parsed 
as parameters directly on the remap line. So, for example, if you have a remap 
line that contains something like this:

{{@plugin=cachekey.so @pparam=--remove-path=true}}

That will cause ORT to attempt to load a config file named 
{{--remove-path=true}}. ORT fails to accomplish this in several ways and 
produces a variety of errors:

DEBUG Starting processing of config file: --remove-path=true
WARN --remove-path=true is being processed with an unknown service

{code:none}
INFO:  Start processing config file: --remove-path=true 
Use of uninitialized value in concatenation (.) or string at 
/opt/ort/traffic_ops_ort.pl line 2515.
Use of uninitialized value $dir in -d at /opt/ort/traffic_ops_ort.pl line 645.
Use of uninitialized value $dir in concatenation (.) or string at 
/opt/ort/traffic_ops_ort.pl line 648.
/bin/mkdir: missing operand
Try '/bin/mkdir --help' for more information.
Use of uninitialized value $dir in pattern match (m//) at 
/opt/ort/traffic_ops_ort.pl line 649.
Use of uninitialized value $dir in pattern match (m//) at 
/opt/ort/traffic_ops_ort.pl line 653.
Use of uninitialized value $dir in concatenation (.) or string at 
/opt/ort/traffic_ops_ort.pl line 657.
DEBUG Directory created: .
Use of uninitialized value $result in pattern match (m//) at 
/opt/ort/traffic_ops_ort.pl line 2482.
Use of uninitialized value $size in numeric eq (==) at 
/opt/ort/traffic_ops_ort.pl line 2488.
Use of uninitialized value $url in concatenation (.) or string at 
/opt/ort/traffic_ops_ort.pl line 2489.
ERROR URL:  returned empty!
{code}

ORT should probably skip "files" that start with {{-}}.



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

[GitHub] incubator-trafficcontrol issue #781: WIP - Adding contact information to Ten...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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 #781: WIP - Adding contact information to Ten...

[dangogh]

Github user dangogh commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/781
  
retest this please


---
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 #783: [TC-437] - adds the ability to generate...

[asfgit]

Github user asfgit commented on the issue:

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

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



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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

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



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



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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user dangogh commented on the issue:

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


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



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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

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



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



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

[GitHub] incubator-trafficcontrol issue #783: [TC-437] - adds the ability to generate...

[asfgit]

Github user asfgit commented on the issue:

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

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



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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user dangogh commented on the issue:

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




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



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

[GitHub] incubator-trafficcontrol issue #783: [TC-437] - adds the ability to generate...

[dangogh]

Github user dangogh commented on the issue:

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




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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

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



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



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

[GitHub] incubator-trafficcontrol issue #783: [TC-437] - adds the ability to generate...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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 #783: [TC-437] - adds the ability to generate...

[asfgit]

Github user asfgit commented on the issue:

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

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



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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user dangogh commented on the issue:

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


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



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

[GitHub] incubator-trafficcontrol issue #783: [TC-437] - adds the ability to generate...

[dangogh]

Github user dangogh commented on the issue:

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


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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

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



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



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

[GitHub] incubator-trafficcontrol issue #783: [TC-437] - adds the ability to generate...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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-501) TPv2 installation - better defaults are required

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell commented on TC-501:


i’m not sure the best solution off the top of my head.

the default values found in 
https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_portal/conf/config.js
 work well when you are in “dev” mode, aka when you have run `grunt` or `grunt 
dev` your output files are put in files in ./app/dist/public/ as the config.js 
file says and it starts an express server that will write an access.log to 
whereever you tell it to. by default i tell it to write it to 
`./server/log/access.log` but yes, when TP is installed, you need to change 
both of those values per the comments in that config.js file.

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



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

[jira] [Created] (TC-501) TPv2 installation - better defaults are required

[Nir Sopher (JIRA)]

Nir Sopher created TC-501:
-

 Summary: TPv2 installation - better defaults are required
 Key: TC-501
 URL: https://issues.apache.org/jira/browse/TC-501
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Portal
Affects Versions: 2.1.0
Reporter: Nir Sopher


After basic install of traffic-portal based on the documentation, traffic 
portal failed to launch. this is due to relative pathes to the logs and static 
files appear in the default configuration.
Note that the working directory of the server is "/"

First, the log path (./server/log) does not exists. A possible fix is to change 
the dir to /opt/traffic_portal/server/log and create the log dir if needed. 

Second. the files static path should be set to "opt/traffic_portal/public"



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

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

[Robert Scrimo (JIRA)]

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

Robert Scrimo updated TC-492:
-
Description: 
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.

  was:
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: A hack is to use the UI to remove the association(s) before 
deleting the delivery service.

NOTE: Other versions of Traffic Ops may be affected.


> 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
>Reporter: Robert Scrimo
>Priority: Critical
>
> 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)

[GitHub] incubator-trafficcontrol issue #781: WIP - Adding contact information to Ten...

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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 #783: [TC-437] - adds the ability to generate...

[asfgit]

Github user asfgit commented on the issue:

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

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



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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

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



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



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

[GitHub] incubator-trafficcontrol issue #781: WIP - Adding contact information to Ten...

[dangogh]

Github user dangogh commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/781
  
retest this please


---
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-492) Deleting Delivery Service with associated static dns entry(s) in staticdnsentry table fails due to foreign key constraint violation

[Robert Scrimo (JIRA)]

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

Robert Scrimo updated TC-492:
-
Description: 
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: A hack is to use the UI to remove the association(s) before 
deleting the delivery service.

NOTE: Other versions of Traffic Ops may be affected.

  was:
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: A hack is to use the UI end-point GET "/staticdnsentry/:id/delete" 
to remove the association(s) before deleting the delivery service.

NOTE: Other versions of Traffic Ops may be affected.


> 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
>Reporter: Robert Scrimo
>
> 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: A hack is to 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

[Robert Scrimo (JIRA)]

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

Robert Scrimo updated TC-492:
-
Priority: Critical  (was: Major)

> 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
>Reporter: Robert Scrimo
>Priority: Critical
>
> 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: A hack is to 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-500) Creating/Updating a Delivery Service via API has length constraint on displayName of 48, but no such constraint in UI code

[Robert Scrimo (JIRA)]

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

Robert Scrimo updated TC-500:
-
Description: 
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.

  was:
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, this 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.


> 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
>Reporter: Robert Scrimo
>
> 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] [Created] (TC-500) Creating/Updating a Delivery Service via API has length constraint on displayName of 48, but no such constraint in UI code

[Robert Scrimo (JIRA)]

Robert Scrimo created TC-500:


 Summary: 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
Reporter: Robert Scrimo


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, this 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] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/783
  
Can one of the admins verify this patch?


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



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

[GitHub] incubator-trafficcontrol issue #783: [TC-437] - adds the ability to generate...

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/783
  
Can one of the admins verify this patch?


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

[jira] [Commented] (TC-437) TPv2 - add the ability to generate ISO

[ASF GitHub Bot (JIRA)]

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

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

GitHub user mitchell852 opened a pull request:

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

[TC-437] - adds the ability to generate an ISO to the api / traffic portal 
v2



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-437-generate-iso

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

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






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



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

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

[mitchell852]

GitHub user mitchell852 opened a pull request:

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

[TC-437] - adds the ability to generate an ISO to the api / traffic portal 
v2



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-437-generate-iso

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

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






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

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

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reopened TC-402:


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



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

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

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-402.

   Resolution: Fixed
Fix Version/s: 2.1.0

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



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

[GitHub] incubator-trafficcontrol pull request #782: updates tp dev install doc

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #738: make delivery service `MultiSiteOrigin`...

[mdb]

Github user mdb commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/738
  
@dneuman64 I trust your judgement; I may be mistaken here -- apologies, 
I've been a bit swamped with other things.


---
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 #782: updates tp dev install doc

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/782
  
Can one of the admins verify this patch?


---
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 #782: updates tp dev install doc

[mitchell852]

GitHub user mitchell852 opened a pull request:

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

updates tp dev install doc



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
updates-tp-install-doc

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

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


commit dd454ad04fd1822a30a2dc99323ae27c3b8a48c1
Author: Jeremy Mitchell 
Date:   2017-08-07T15:25:59Z

updates tp dev install doc




---
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 #781: WIP

[asfgit]

Github user asfgit commented on the issue:

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

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



---
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 #781: WIP

[dangogh]

Github user dangogh commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/781
  
Please change the PR title to be descriptive of the change.   WIP is an 
appropriate label to show it's not complete,  but still must describe the 
purpose of the change.

Also,  individual commit messages should be descriptive.


---
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 #781: WIP

[limited]

Github user limited commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/781
  
ok to test


---
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 #781: WIP

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/781
  
Can one of the admins verify this patch?


---
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 #781: WIP

[wmbrown18]

GitHub user wmbrown18 opened a pull request:

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

WIP

This is a working progress of adding a contact information from the tenant 
table. It works, but other a part of the mailing list were deciding on how to 
make it better. So this is what was made for the time being.

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

$ git pull https://github.com/wmbrown18/incubator-trafficcontrol wip

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

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


commit a9a63e812e76bc8d98a64238e7d65c21ed5108c6
Author: Will 
Date:   2017-08-07T13:25:00Z

wip

commit f1bff2c9612c87cff2b02418436b9a6c922d5dcf
Author: Will 
Date:   2017-08-07T13:28:55Z

wip




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