Running on weblogic 10.3.6, so perhaps this behaviour is different in more recent versions.
When running against v2.0.20 of the module, the puppet agent eventually times out while waiting for a response from:
migration_policy = get('MigrationPolicy')
within the index.py script for jdbc_persistence_store. As near as I can figure, this looks to stem from that attribute not existing at that level, so the get fails and it isn't exiting cleanly. The same then happens with the next line (DistributionPolicy,) since that's also not at that level of the directory in v10.3.6.
Perhaps these items have moved around in v12.x.y? I haven't got an environment to check that in.
Running on weblogic 10.3.6, so perhaps this behaviour is different in more recent versions.
When running against v2.0.20 of the module, the puppet agent eventually times out while waiting for a response from:
migration_policy = get('MigrationPolicy')within the index.py script for jdbc_persistence_store. As near as I can figure, this looks to stem from that attribute not existing at that level, so the
getfails and it isn't exiting cleanly. The same then happens with the next line (DistributionPolicy,) since that's also not at that level of the directory in v10.3.6.Perhaps these items have moved around in v12.x.y? I haven't got an environment to check that in.