[
https://issues.apache.org/jira/browse/TC-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123332#comment-16123332
]
Steve Malenfant commented on TC-375:
------------------------------------
[~dewrich] I just tried upgrading from 2.0 to
traffic_ops-2.1.0-6795.e2e89e12.el7.x86_64.rpm and the same thing happened.
goose was in the path. Does the fix introduced take care of the 2.0 -> 2.1 RPM
upgrade?
{code:java}
Preparing... ################################# [100%]
trafops:x:995:ansible
trafops:x:997:995::/opt/traffic_ops:/sbin/nologin
Backing up config files.
Stopping traffic_ops (via systemctl): [ OK ]
Updating / installing...
1:traffic_ops-2.1.0-6795.e2e89e12.ewarning:
/opt/traffic_ops/app/conf/cdn.conf created as
/opt/traffic_ops/app/conf/cdn.conf.rpmnew
################################# [ 50%]
Restoring config files.
Migrating database...
Can't exec "goose": No such file or directory at db/admin.pl line 183.
Can't run goose
Database migration failed.
Upgrade complete.
{code}
> yum upgrade traffic_ops... can't find goose
> -------------------------------------------
>
> Key: TC-375
> URL: https://issues.apache.org/jira/browse/TC-375
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
> Affects Versions: 2.1.0
> Reporter: Dan Kirkwood
> Assignee: Dewayne Richardson
> Labels: goose, postinstall, yum
> Fix For: 2.1.0
>
>
> Traffic Ops postinstall puts goose in /opt/traffic_ops/go/bin. The rpm
> upgrade path executes `db/admin.pl upgrade` which tries to run goose, but
> can't find it because it's not in the root PATH.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
