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
Clone CA: pkispawn does not throw an error when master CA has serialCloneTransferNumber=0 set #2104
Comments
Comment from mharmsen (@mharmsen) at 2015-08-10 23:36:47 Per CS/DS meeting of 08/10/2015 - 10.3 |
Comment from mharmsen (@mharmsen) at 2015-08-10 23:38:49 Bugzilla Bug 1252173 was filed to document this as a known issue in the release notes. |
Comment from mharmsen (@mharmsen) at 2016-05-06 21:58:31 Per Bug Triage of 05/05/2016: 10.4 NOTE: (corner case) |
Comment from mharmsen (@mharmsen) at 2016-12-01 21:12:46 Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - minor |
Comment from mharmsen (@mharmsen) at 2017-02-27 14:03:48 Metadata Update from @mharmsen:
|
Comment from mharmsen (@mharmsen) at 2017-08-31 00:13:02 Metadata Update from @mharmsen:
|
Comment from mharmsen (@mharmsen) at 2018-04-23 21:01:12 Per 10.5.x/10.6 Triage: FUTURE RHBZ: CLOSED UPSTREAM |
Comment from mharmsen (@mharmsen) at 2018-04-23 21:01:12 Metadata Update from @mharmsen:
|
This issue was migrated from Pagure Issue #1545. Originally filed by mharmsen (@mharmsen) on 2015-08-06 22:34:37:
Clone CA: pkispawn does not throw an error when master CA has
serialCloneTransferNumber=0 set
Steps to Reproduce:
Actual results:
Expected results:
The text was updated successfully, but these errors were encountered: