-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeIPA nightly tests failure when installing a CA replica (pki nightly) #3330
Comments
Comment from frenaud (@flo-renaud) at 2020-09-22 03:19:51 Companion issue logged against FreeIPA: https://pagure.io/freeipa/issue/8509 |
This was referenced Oct 23, 2020
This was referenced Nov 2, 2020
This was referenced Nov 15, 2020
This was referenced Nov 18, 2020
The issue seems to happen when the 2nd replica is created (replica1 is cloned from master and replica2 is cloned from replica1). |
This is probably a regression of #40 then? |
This was referenced Jan 12, 2021
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 29, 2021
In commit e0b2496 the configurePorts() invocation was moved to happen later during server startup process. It's not clear how, but apparently the replica ID range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the configurePorts() has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 29, 2021
In commit e0b2496 the configurePorts() invocation was moved to happen later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the configurePorts() has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 29, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 29, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
that referenced
this issue
Jan 29, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: #3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 29, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: #3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
edewata
added a commit
to edewata/pki
that referenced
this issue
Jan 30, 2021
In commit e0b2496 the CMSEngine.configurePorts() invocation was moved later during server startup process. It's not clear how, but apparently the cert number range assignment depends on this code so it failed when installing a clone of an existing clone. To fix the problem the invocation has been moved back into its original position. Resolves: dogtagpki#3330
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was migrated from Pagure Issue #3213. Originally filed by frenaud (@flo-renaud) on 2020-09-22 03:19:01:
2 nightly tests using pki's nightly copr repo failed in ipa-replica-install, see PR #421:
test_replication_layouts_TestLineTopologyWithCA
: report, logstest_replication_layouts_TestLineTopologyWithCAKRA
: report, logsThe replica installation fails in the pkispawn step with the following message:
and we also see the following in the logs:
The same error can be seen in the server used as source for the CA replication in /var/log/pki/pki-tomcat/ca/debug.2020-09-21.log.gz :
Installed packages (full list here):
The text was updated successfully, but these errors were encountered: