Re: Invalidate Content Error

Jeremy +1. Unless someone still got a "purge" agent running around the extra dependancies can be removed. There is no purge going on, just revalidate. On Wed, Feb 1, 2017 at 4:57 PM, Jeremy Mitchell wrote: > I also created this issue to remove unused job tables if anyone

Re: Invalidate Content Error

I created this issue to account for seed data lost in the transition from 1.8 to 2.0 https://issues.apache.org/jira/browse/TC-126 On Wed, Feb 1, 2017 at 10:26 AM, Jeremy Mitchell wrote: > hmmm. i think you've stumbled on a larger issue. the move from 1.8 to 2.0 >

Re: Invalidate Content Error

hmmm. i think you've stumbled on a larger issue. the move from 1.8 to 2.0 (master) included the consolidation of migration files into create_tables.sql file but.some of those migrations represented the seeding of data (i.e. 2015120800_add_job_status.sql) which would not be represented in

Re: Invalidate Content Error

Indeed I failed to notice that the file traffic_ops/app/db/migrations/2015120800_add_job_status.sql does not exist anymore in master, and the seeds.sql file in master does not contain any insert to a job-related table to compensate for that. So the job_agent and job_status tables are empty

Re: Invalidate Content Error

I am pretty sure he already said it works in master? On Wed, Feb 1, 2017 at 8:30 AM, Jeremy Mitchell wrote: > So going forward with the master branch (it's too late for 1.8 so your > workaround will have to suffice), I think 2 lines need to be added to > seeds.sql so

Re: Invalidate Content Error

Please look at the release notes of 1.3.0, might solve your problem. https://github.com/Comcast/traffic_control/releases/tag/RELEASE-1.3.0 The revalidation feature doesn't work out of the box. The entry id=1 in the job_agent table MUST exist as well as name=PURGE must be present in the

Re: Invalidate Content Error

In my opinion, the job agent id should have been passed to the newjob() subroutine rather than depending on a hard-coded value...actually, it looks like that was the intent but the $agent variable never got used.

Re: Invalidate Content Error

Thanks for the investigation. Sounds like there is definitely a bug there. I would vote don't worry about fixing the issue in 1.8 since it is fixed in master. We should, however, make a release note or something explaining the issue and the work around. --Dave On Tue, Jan 31, 2017 at 12:32