Puppet run keeps adding resource adapter (scope lookup issue?) #542
Comments
|
Just to update, I've added more debugging and believe I have found the issue Debugging the scope I can see puppet is creating the value as: I have double checked our hiera and I can't see where we are adding the leading "config/". My statement returns: We can see the module is trying to match on just == plan. It looks as thought the strip doesn't work. I can fix this by changing the statement to: But of course I would like your suggestions first. I don't want our module to go out of sync with the releases. |
|
Thanks , I thinks the generating of facts is not working properly. So in orawls.rb the analyse of the domain went wrong and the resource facts are not set. Or it can be some ruby issue. Because I don’t have your domain can you check if orawls.rb is not crashing ( this happens in the beginning of the run) and what are all the facts. |
|
Best way is to have a new vm with only a domain and these resource adapters , I think 1 of the other wls artifacts are failing to detect on the domain and then the resource adapter facts are not set. |
|
Thanks Edwin, |
|
I've disabled most other things in the domain but sadly no change. I searched for orawls.rb errors but couldn't see any either. The full ora_mdw facts resolve as follows: |
|
The plot is thickening but not in a good way. Hiera Debug statement in orawls.rb (note the leading config/ ) Facts being set by puppet: Interestingly if I try and set an adapter_plan_dir ending on config. i.e. The fact gets set as: |
|
it is the same I have. I will do some tests myself so it cannot find the entries because the plan is not updated, or resource adapter reload went wrong. In the domain xml there should be a reference to this plan. it should be updated to yours and reload the resource adapter. my config |
|
Hi Edwin, My colleague put it in domain_home so that it gets zipped up and distributed as part of the domain creation. I'll change the location and rebuild these AWS instances to see it the application works as expected or if the plan.xml does indeed need shipping. Thanks again |
|
ah ok. I forget that part I guess. yeah you need to put it on a shared storage ( or some rsync step) and on all vm the plan path should be the same. with jms and xa they have now DB support but not yet for resource adapters (I think ) |
|
We're not quite at the shared storage point yet (next 6 month maybe) but I can write a quick shipper and store it in s3 and then get the managed servers to download it from there. That way puppet can manage the file state and only update the file when it's edited. Thanks again for the quick replies. If anything I've learnt a good deal more about the module. Dave |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm hoping you can help. I've got a domain with multiple resource adapters, puppet creates them as per the yaml, yet on the next run puppet says they don't exist and creates them again.
I've added some debugging to the module and narrowed it down to the scope lookups in "resource_adapter_exists.rb", planValue and planEntry - here's my config and logs. We're running on
hiera.yaml
resource_adapter_exists.rb (with my added debug messages)
Puppet Server log:
and
I can see a prefix at the top of the file specifying a domain name but I assume this is something to do with the module?
If I hard code planValue with the plan_db.xml's full path the module returns true, so I can only think that the scope isn't getting created properly. Do I need to update to the latest module?
Thanks
Dave
The text was updated successfully, but these errors were encountered: