"You cannot collect exported resources without storeconfigs being set" at manifests/resource/upstream.pp:89:5

[herzmut]

Hello.

When I start my puppet script to create a virtual machine, I get the error message above. I feed your module with the following configuration:

upstreams:
        nxv_394dk0458afs:
            name: django
            upstream_fail_timeout: 10s
            members:
                - '127.0.0.1:8000'

Yes, the YAML syntax derived from a generated template of PuPHPet (https://puphpet.com). I still think the configuration is valid as the other modules in your project work perfectly. The error messages mentions location.pp explicitly.

This error does not keep me from creating my machine and makes this a low-priority issue.

[alex-harvey-z3q]

I assume I'm hitting the same issue when I see:

Warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 103 in file /etc/puppet/modules/nginx/manifests/resource/upstream.pp

Although I have passed in an array of members to $members, this warning is emitted anyway, although the collection statement is inside an else block that isn't applied.

A solution for this issue is proposed in here.

[dniel]

got the same error, any idea how to fix?
just added an simple hard coded array of members, the error message is printed and not upstream config generated.

[alex-harvey-z3q]

Did the link I proposed above not help for you?

[dniel]

I dont understand the link, I just added
nginx::resource::upstream { 'app_backend':
members => ['app-1','app-2']
}

to the script, and expected it to produce upstream config for nginx.

[3flex]

Can someone test the fix proposed in #832?

[dniel]

Somehow, my problem solved itself when l left it alone long enough and did alot of other development. When I returned to the nginx config, everything was working as excpected even that the nginx code was unchanged. Must have been something about my whole module setup. Unfortunately I cant verify the fix above in my current setup.

[sorreltree]

Just to be clear, I can verify that the test does in fact kill the warning message in puppet apply mode when no upstream members are there to be gathered -- that's to say, in the case where there's nothing to be collected, the warning no longer fires.

What I can't test is whether in the case that there is something to be collected that it either does the collection or throws the warning that storeconfigs isn't set up, because I have no puppet master and don't use collected upstreams.