[jira] [Created] (TC-418) getting displayName too long using API but UI has no issue

2017-07-12 Thread Joseph Pappano (JIRA) 
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-407) Cannot update a steering type delivery service via API

2017-06-30 Thread Joseph Pappano (JIRA) 
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-277) setting Raik server offline fails with error

2017-05-08 Thread Joseph Pappano (JIRA) 
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)