[jira] [Closed] (TC-407) Cannot update a steering type delivery service via API
[
https://issues.apache.org/jira/browse/TC-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Pappano closed TC-407.
-
Resolution: Resolved
Started working in a previous update of TO.
> Cannot update a steering type delivery service via API
> --
>
> Key: TC-407
> URL: https://issues.apache.org/jira/browse/TC-407
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops API
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Joseph Pappano
>Assignee: Jeremy Mitchell
> Fix For: 2.1.0, 2.2.0
>
>
> The API to update a delivery service requires an origin server FQDN. Steering
> type delivery services to not have one and the api fails with the following
> error.
> {code}
> {u'alerts': [{u'level': u'error', u'text': u'orgServerFqdn is required'}]}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TC-418) getting displayName too long using API but UI has no issue
Joseph Pappano created TC-418:
-
Summary: getting displayName too long using API but UI has no issue
Key: TC-418
URL: https://issues.apache.org/jira/browse/TC-418
Project: Traffic Control
Issue Type: Bug
Components: Traffic Ops API
Affects Versions: 2.1.0
Environment: API
Reporter: Joseph Pappano
Priority: Minor
Here is the API out put with the error
{code}
{'active': True,
'cacheurl': None,
'ccrDnsTtl': 3600,
'cdnId': 2,
'cdnName': u'title-vi',
'checkPath': u'crossdomain.xml',
'displayName': u'Title VI Linear - Florida-Jacksonville from CMC stack',
'dnsBypassCname': None,
'dnsBypassIp': None,
'dnsBypassIp6': None,
'dnsBypassTtl': 30,
'dscp': 40,
'edgeHeaderRewrite': None,
'geoLimit': 0,
'geoLimitCountries': u'',
'geoLimitRedirectURL': u'',
'geoProvider': 0,
'globalMaxMbps': None,
'globalMaxTps': 0,
'httpBypassFqdn': u'',
'infoUrl': u'https://tkts.sys.comcast.net/browse/CDNOPS-3176',
'initialDispersion': 1,
'ipv6RoutingEnabled': True,
'logsEnabled': False,
'longDesc': u'Title VI Linear - Florida-Jacksonville from Redundant stack in
CMC',
'longDesc1': None,
'longDesc2': u'linear-cmc-jksnv-fl-pil',
'maxDnsAnswers': 0,
'midHeaderRewrite': None,
'missLat': 41.881944,
'missLong': -87.627778,
'multiSiteOrigin': False,
'orgServerFqdn': u'http://rlr-cmc-slivel4lb-vip.cmc.co.ndcwest.comcast.net',
'originShield': None,
'profileDescription': None,
'profileId': None,
'profileName': None,
'protocol': 2,
'qstringIgnore': 1,
'rangeRequestHandling': 0,
'regexRemap': None,
'regionalGeoBlocking': False,
'remapText': None,
'signed': False,
'trRequestHeaders': 'X-MoneyTrace',
'trResponseHeaders': None,
'typeId': 13,
'xmlId': u'linear-cmc-jksnv-fl-pil'}
{u'alerts': [{u'level': u'error', u'text': u'displayName too long'}]}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TC-408) Documentation for creating ssl keys is missing a field.
Joseph Pappano created TC-408:
-
Summary: Documentation for creating ssl keys is missing a field.
Key: TC-408
URL: https://issues.apache.org/jira/browse/TC-408
Project: Traffic Control
Issue Type: Bug
Components: Documentation
Reporter: Joseph Pappano
Priority: Minor
The documentation to generate ssl keys is missing the delivery service field.
generating keys with that field being null will cause issues on Riak.
{code}
POST /api/1.2/deliveryservices/sslkeys/generate
Generates SSL crt, csr, and private key for a delivery service
Authentication Required: Yes
Role(s) Required: Admin
Request Properties
Parameter TypeDescription
key string xml_id of the delivery service
version string version of the keys being generated
hostnamestring the pristine hostname of the delivery service
country string
state string
citystring
org string
unitboolean
Request Example
{
"key": "ds-01",
"businessUnit": "CDN Engineering",
"version": "3",
"hostname": "tr.ds-01.ott.kabletown.com",
"certificate": {
"key": "some_key",
"csr": "some_csr",
"crt": "some_crt"
},
"country": "US",
"organization": "Kabletown",
"city": "Denver",
"state": "Colorado"
}{code}
These are the fields required. Notice the delivery service is null.
{code}
{
"cdn": null,
"certificate": {
"crt":
"csr": "key": },
"city": "Denver",
"country": "US",
"deliveryservice": null,
"hostname": "*.linear-chi-pil-red.xcr.comcast.net",
"key": "linear-chi-pil-red",
"org": null,
"state": "Colorado",
"unit": "IPCDN",
"version": "1"
}{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TC-407) Cannot update a steering type delivery service via API
Joseph Pappano created TC-407:
-
Summary: Cannot update a steering type delivery service via API
Key: TC-407
URL: https://issues.apache.org/jira/browse/TC-407
Project: Traffic Control
Issue Type: Bug
Components: Traffic Ops API
Affects Versions: 2.1.0
Reporter: Joseph Pappano
The API to update a delivery service requires an origin server FQDN. Steering
type delivery services to not have one and the api fails with the following
error.
{code}
{u'alerts': [{u'level': u'error', u'text': u'orgServerFqdn is required'}]}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TC-369) ORT recreates certain files on each run.
Joseph Pappano created TC-369: - Summary: ORT recreates certain files on each run. Key: TC-369 URL: https://issues.apache.org/jira/browse/TC-369 Project: Traffic Control Issue Type: Bug Components: Traffic Ops ORT Affects Versions: 2.1.0 Reporter: Joseph Pappano Priority: Minor each time ORT runs there will be subtle differences in parent.config and other files and they are needlessly recreated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-277) setting Raik server offline fails with error
Joseph Pappano created TC-277: - Summary: setting Raik server offline fails with error Key: TC-277 URL: https://issues.apache.org/jira/browse/TC-277 Project: Traffic Control Issue Type: Bug Components: Traffic Ops, Traffic Ops Client Affects Versions: 2.1.0 Environment: Chrome on Mac OS X Reporter: Joseph Pappano Priority: Minor Attachments: Screen Shot 2017-05-08 at 3.23.42 PM.png Setting Riak server offline by clicking edit -> edit -> changing status to offline and adding comment -> submit will result in an error. clicking edit -> offline server button will succeed. attached screenshot of error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
