[
https://issues.apache.org/jira/browse/TC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126362#comment-16126362
]
Jeff Elsloo commented on TC-250:
--------------------------------
It appears that we're still backing up an invalid location, from
traffic_ops.spec:
{{ 84 cd %{PACKAGEDIR} && tar cf /var/tmp/traffic_ops-backup.tar
app/public/routing app/conf app/db/dbconf.yml app/local app/cpanfile.snapshot}}
I don't think that the following is valid anymore in the psql world:
{{app/public/routing}}
> 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
> Reporter: Jeff Elsloo
> Priority: Trivial
> Labels: crconfig, rpm
>
> 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)
