You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Hank Beatty (JIRA)" <ji...@apache.org> on 2017/08/14 15:15:01 UTC

[jira] [Commented] (TC-195) Traffic Router requires status to be set to OFFLINE to remove an active Traffic Router

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

Hank Beatty commented on TC-195:
--------------------------------

[~elsloo] Is this still an issue? If so, are we planning on fixing it in 2.1?

> Traffic Router requires status to be set to OFFLINE to remove an active Traffic Router
> --------------------------------------------------------------------------------------
>
>                 Key: TC-195
>                 URL: https://issues.apache.org/jira/browse/TC-195
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Router
>    Affects Versions: 2.1.0
>            Reporter: Jeff Elsloo
>            Assignee: Jeff Elsloo
>            Priority: Minor
>              Labels: crconfig, routing
>
> Traffic Router currently requires the status of a given Traffic Router to be set to OFFLINE if it is to be removed from DNS answers. When set to OFFLINE, Traffic Ops will drop it from the CrConfig, so naturally it would drop from the configuration. If, however, a Traffic Router is set to ADMIN_DOWN, it remains in the CrConfig and Traffic Router leaves it in the DNS zones because the status is not OFFLINE.
> Ideally, instead of checking if the status is OFFLINE, we would check to see if it's a "positive" status (ONLINE or REPORTED). Any other status should be considered invalid and the Traffic Router should be skipped with regard to DNS.



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