[
https://issues.apache.org/jira/browse/OAK-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-3499:
--------------------------------
Attachment: OAK-3499.diff
This patch (1) introduces a system property through which a specific hardware
address (or the lack of) can be simulated and (2) changes the cluster node
lookup code to skip entries that are going to be deleted (because using random
IDs and being expired).
With these changes the three tests pass even if no hardware address is
available, however {{LastRevRecoveryRandomizedIT}} fails; it assumes that
LastRevRecovery is run, however it doesn't as the cluster node info document
gets deleted and re-created.
> Test failures when there is no network interface
> ------------------------------------------------
>
> Key: OAK-3499
> URL: https://issues.apache.org/jira/browse/OAK-3499
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Affects Versions: 1.3.8
> Reporter: Marcel Reutegger
> Assignee: Julian Reschke
> Priority: Minor
> Attachments: OAK-3499.diff
>
>
> There are test failures when no network interface is available.
> {noformat}
> Tests in error:
> purge(org.apache.jackrabbit.oak.plugins.document.CollisionTest): Configured
> cluster node id 1 already in use:
>
> inactiveClusterId(org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreTest):
> Configured cluster node id 2 already in use:
>
> purgeUnmergedBranch(org.apache.jackrabbit.oak.plugins.document.UnmergedBranchTest):
> Configured cluster node id 1 already in use:
> {noformat}
> I'm quite confident these used to work before.
> [~reschke], could this be caused by recent changes for OAK-3449?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
