[jira] [Closed] (TC-481) ORT should expire yum cache rather than purging it completely
[ https://issues.apache.org/jira/browse/TC-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Tucker closed TC-481. --- Resolution: Fixed > ORT should expire yum cache rather than purging it completely > - > > Key: TC-481 > URL: https://issues.apache.org/jira/browse/TC-481 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops ORT >Reporter: Jason Tucker >Priority: Minor > > Currenty, ORT is performing `yum clean metadata`, which purges all metadata > (and the db files for each repo). This should be switched to `yum clean > expire-cache` which is more lightweight, as it simply causes revalidation of > metadata. > (PR forthcoming) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-484) traffic_ops/experimental - existing DNS Delivery Service shows blank field for 'Max DNS Answers'
[ https://issues.apache.org/jira/browse/TC-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Tucker closed TC-484. --- Resolution: Duplicate Closing - dup. > traffic_ops/experimental - existing DNS Delivery Service shows blank field > for 'Max DNS Answers' > > > Key: TC-484 > URL: https://issues.apache.org/jira/browse/TC-484 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Reporter: Jason Tucker > Attachments: legacy.png, new.png > > > Existing DS in legacy Traffic Ops shows a value of '1' for Max DNS Answers, > however, the field shows up blank in the new Traffic Ops UI. Screenshots > attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-484) traffic_ops/experimental - existing DNS Delivery Service shows blank field for 'Max DNS Answers'
Jason Tucker created TC-484: --- Summary: traffic_ops/experimental - existing DNS Delivery Service shows blank field for 'Max DNS Answers' Key: TC-484 URL: https://issues.apache.org/jira/browse/TC-484 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Reporter: Jason Tucker Attachments: legacy.png, new.png Existing DS in legacy Traffic Ops shows a value of '1' for Max DNS Answers, however, the field shows up blank in the new Traffic Ops UI. Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-481) ORT should expire yum cache rather than purging it completely
Jason Tucker created TC-481: --- Summary: ORT should expire yum cache rather than purging it completely Key: TC-481 URL: https://issues.apache.org/jira/browse/TC-481 Project: Traffic Control Issue Type: Improvement Components: Traffic Ops ORT Reporter: Jason Tucker Priority: Minor Currenty, ORT is performing `yum clean metadata`, which purges all metadata (and the db files for each repo). This should be switched to `yum clean expire-cache` which is more lightweight, as it simply causes revalidation of metadata. (PR forthcoming) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-472) traffic_ops/experimental - failure to assign servers to new Delivery Service
Jason Tucker created TC-472: --- Summary: traffic_ops/experimental - failure to assign servers to new Delivery Service Key: TC-472 URL: https://issues.apache.org/jira/browse/TC-472 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Reporter: Jason Tucker Priority: Minor While using the new UI, I was unable to assign servers to a newly-created DS. After submitting the change, no servers were linked. No error apparent when submitting. Tried multiple times with same results. Browser: chrome 58.0.3029.110 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-416) traffic_router: tomcat shutdown problems
[ https://issues.apache.org/jira/browse/TC-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Tucker closed TC-416. --- Resolution: Fixed PR was merged; closing. > traffic_router: tomcat shutdown problems > > > Key: TC-416 > URL: https://issues.apache.org/jira/browse/TC-416 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Router >Reporter: Jason Tucker > Labels: tomcat > > The tomcat init script has a few problems: > 1. "Clean" shutdowns frequently timeout, and the scripts give up, leaving > tomcat running > 2. Normal tomcat shutdown actually involves spinning up a second jvm > instance. Right now, we start this second instance with the same > CATALINA_OPTS as traffic_router, which can be problematic on > memory-constrained hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (TC-416) traffic_router: tomcat shutdown problems
[ https://issues.apache.org/jira/browse/TC-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Tucker updated TC-416: Comment: was deleted (was: PR: https://github.com/apache/incubator-trafficcontrol/pull/724) > traffic_router: tomcat shutdown problems > > > Key: TC-416 > URL: https://issues.apache.org/jira/browse/TC-416 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Router >Reporter: Jason Tucker > Labels: tomcat > > The tomcat init script has a few problems: > 1. "Clean" shutdowns frequently timeout, and the scripts give up, leaving > tomcat running > 2. Normal tomcat shutdown actually involves spinning up a second jvm > instance. Right now, we start this second instance with the same > CATALINA_OPTS as traffic_router, which can be problematic on > memory-constrained hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-416) traffic_router: tomcat shutdown problems
Jason Tucker created TC-416: --- Summary: traffic_router: tomcat shutdown problems Key: TC-416 URL: https://issues.apache.org/jira/browse/TC-416 Project: Traffic Control Issue Type: Bug Components: Traffic Router Reporter: Jason Tucker The tomcat init script has a few problems: 1. "Clean" shutdowns frequently timeout, and the scripts give up, leaving tomcat running 2. Normal tomcat shutdown actually involves spinning up a second jvm instance. Right now, we start this second instance with the same CATALINA_OPTS as traffic_router, which can be problematic on memory-constrained hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TC-416) traffic_router: tomcat shutdown problems
[ https://issues.apache.org/jira/browse/TC-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083031#comment-16083031 ] Jason Tucker commented on TC-416: - PR: https://github.com/apache/incubator-trafficcontrol/pull/724 > traffic_router: tomcat shutdown problems > > > Key: TC-416 > URL: https://issues.apache.org/jira/browse/TC-416 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Router >Reporter: Jason Tucker > Labels: tomcat > > The tomcat init script has a few problems: > 1. "Clean" shutdowns frequently timeout, and the scripts give up, leaving > tomcat running > 2. Normal tomcat shutdown actually involves spinning up a second jvm > instance. Right now, we start this second instance with the same > CATALINA_OPTS as traffic_router, which can be problematic on > memory-constrained hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-403) Comments/Notes field in UI for configurations
Jason Tucker created TC-403: --- Summary: Comments/Notes field in UI for configurations Key: TC-403 URL: https://issues.apache.org/jira/browse/TC-403 Project: Traffic Control Issue Type: Wish Components: Traffic Ops Reporter: Jason Tucker Priority: Minor As a Traffic Ops admin user, there are times that I want to attach additional configuration notes, comments, caveats, etc to an object (particularly DS and Server configs) so that they are readily available to any admin that may need to later update the config. Having an arbitrary text field attached to the config that could be used for any extra information would be helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-183) api/1.2/servers/:id returns 'offline_reason' instead of the expected 'offlineReason'
Jason Tucker created TC-183:
---
Summary: api/1.2/servers/:id returns 'offline_reason' instead of
the expected 'offlineReason'
Key: TC-183
URL: https://issues.apache.org/jira/browse/TC-183
Project: Traffic Control
Issue Type: Bug
Components: Traffic Ops API
Affects Versions: 1.8.0
Reporter: Jason Tucker
Priority: Minor
{{GET /api/1.2/servers/:id}} returns 'offline_reason', but {{PUT
/api/1.2/servers/:id}} is expecting 'offlineReason'. This is causes problems if
you are fetching, modifying, and resubmitting server properties.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
