Le 2015-04-15 09:41, Apollon Oikonomopoulos a écrit :
^^
This is probably caused by exporting resources with "complex"
parameters, as reported earlier[1] and is likely due to some
auto-serialization behaviour change from Rails 3 to Rails 4. Still, it
should work fine with all resource types usi
Hi Cristophe,
On 01:04 Tue 14 Apr , Christophe Guilloux wrote:
> If i activate storeconfig in puppet.conf :
>
> storeconfigs = true
> dbadapter = sqlite3
>
> i have this error :
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> can't cast Hash to text
^^
Thi
If i activate storeconfig in puppet.conf :
storeconfigs = true
dbadapter = sqlite3
i have this error :
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: can't cast Hash to text
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Hi
There still seems to be some problems with stored configs, in a test
deployment I have the following minimal node manifest:
define foo($params) {
}
node 'test.adm.easyconnect.no' {
@@foo {'bar': params => {foo => 1, bar => 2} }
}
We use this kind of pattern in quite a few places where it w
4 matches
Mail list logo
