| Summary: | Error when pushing Content Spec if Skynet Datasource is read-only | ||
|---|---|---|---|
| Product: | [Community] PressGang CCMS | Reporter: | Joshua Wulf <jwulf> |
| Component: | CSProcessor | Assignee: | Lee Newson <lnewson> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.x | CC: | jwulf, lcarlon |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 0.14.0 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-07 23:22:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 751250 | ||
|
Description
Joshua Wulf
2011-10-31 06:22:11 UTC
At the moment, a snapshot of the topics is created when a build is performed. A side-effect of reading the Revision level of the topics is an update to the Rev History table in the topic database. We can turn off the snapshot on build, and move this functionality to the snapshot command. With that one we'll make snapshot only work with a descriptive, post-processed Content Spec (existing topics only). Snapshot functionality shouldn't require write access, so we'll deal with the Rev History side effect there. Completed. At this stage you can still specify a revision when building, however it will pull topics from the latest revision and not a snapshot. Snapshots still have to be implemented (See bug #750976). Verified with build 14. Pushing a new content spec that is pure reuse when the skynet datasource is read-only, works. |