Normalizing pki_token_name=Internal to internal for the pkispawn is not working

pki-bot / pki-issues-final

0 stars 0 forks source link

Open pki-bot opened 4 years ago

pki-bot commented 4 years ago

This issue was migrated from Pagure Issue #3013. Originally filed by mharmsen (@mharmsen) on 2018-05-02 20:05:54:

KRA pkispawn failure when pki_token_name=Internal

Installation of subsystems fail when pkispawn has pki_token_name=Internal.

Normalizing pki_token_name=Internal to internal is not working.

Its a regression, the original issue was fixed in https://pagure.io/dogtagpki/issue/2311

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2018-05-02 20:08:05

Per 10.5.x/10.6 Triage: 10.6

edewata: negative case/usability issue

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2018-05-02 20:08:09

Metadata Update from @mharmsen:

Custom field component adjusted to None
Custom field feature adjusted to None
Custom field origin adjusted to None
Custom field proposedmilestone adjusted to None
Custom field proposedpriority adjusted to None
Custom field reviewer adjusted to None
Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1550673
Custom field type adjusted to None
Custom field version adjusted to None