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
verify_certificate_exists still fails when token is empty #3190
Comments
Comment from cheimes (@tiran) at 2018-10-25 09:12:19 PR #80 |
Comment from cheimes (@tiran) at 2018-10-25 09:12:20 Metadata Update from @tiran:
|
Comment from cheimes (@tiran) at 2018-10-25 09:59:05 Committed 0fba3c2 |
Comment from edewata (@edewata) at 2018-10-25 10:07:45 The fix has been pushed to master: |
Comment from edewata (@edewata) at 2018-10-25 10:07:46 Metadata Update from @edewata:
|
Comment from edewata (@edewata) at 2018-10-25 10:11:41 Metadata Update from @edewata:
|
Comment from edewata (@edewata) at 2018-10-26 00:14:17 Metadata Update from @edewata:
|
Comment from edewata (@edewata) at 2018-10-26 00:15:32 Apparently there is a related bug: |
Comment from edewata (@edewata) at 2018-10-26 13:26:37 Fixed in master branch: |
Comment from edewata (@edewata) at 2018-10-26 13:26:38 Metadata Update from @edewata:
|
This issue was migrated from Pagure Issue #3073. Originally filed by cheimes (@tiran) on 2018-10-25 08:49:58:
Commit 17677ae changed how default token name is handled. Dogtag now passes
None
to signal default internal token. Howeververify_certificate_exists
method was not changed. This bug breaks some of FreeIPA CI tests like TestServerReplicaCALessToCAFull.The text was updated successfully, but these errors were encountered: