Storage filter name fails with puppetdb.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-swift |
Fix Released
|
Undecided
|
Sofer Athlan-Guyot | ||
Havana |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
While using puppet client/server 3.3.2 with puppetdb 1.5.2 on debian wheezy I bump into this regression from a puppet 2.7 without puppetdb on the same os release:
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid relationship: Concat:
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
The problem comes from this https:/
To sum up, puppetdb's parser is stricter about how one can named resources constraint (before, require, notify) than the puppet's parser.
In the previous error it should be:
before => Swift::
instead of
before => Swift::
beware of the capitalization.
Changed in puppet-swift: | |
assignee: | nobody → Athlan-Guyot sofer (sofer-athlan-guyot) |
Changed in puppet-swift: | |
milestone: | none → 3.0.0 |
Changed in puppet-swift: | |
milestone: | 3.0.0 → none |
Changed in puppet-swift: | |
milestone: | none → 4.0.0 |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/57393
Review: https:/