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/16 15:22:00 UTC

[jira] [Updated] (TC-250) RPM tries to back up nonexistent on-disk CRConfigs

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

Hank Beatty updated TC-250:
---------------------------
    Fix Version/s: 2.2.0

> RPM tries to back up nonexistent on-disk CRConfigs
> --------------------------------------------------
>
>                 Key: TC-250
>                 URL: https://issues.apache.org/jira/browse/TC-250
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>    Affects Versions: 2.1.0, 2.2.0
>            Reporter: Jeff Elsloo
>            Priority: Trivial
>              Labels: crconfig, rpm
>             Fix For: 2.2.0
>
>
> The spec file for the Traffic Ops RPM backs up config files and restores them during an upgrade. The the <2.0 versions of Traffic Ops stored the CRConfig config on disk, while it's in the database in >=2.0. This should be removed from the 2.x spec file.
> {code}
> traffic_ops/build/traffic_ops.spec:	  cd %{PACKAGEDIR} && tar cf /var/tmp/traffic_ops-backup.tar app/public/*Snapshots app/public/routing  app/conf app/db/dbconf.yml app/local app/cpanfile.snapshot
> {code}
> Specifically, the {{app/public/*Snapshots}} path likely will not exist. There might be {{Trafficserver-Snapshots}} but definitely not CRConfig.



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