Observation: On F28 upon running banner-show or banner-validate ERROR: invalid mode: 'UTF-8' appears.
[root@pki1 fedora]# rm -rf /etc/pki/topology-02-CA/banner.txt [root@pki1 fedora]# pki-server banner-show -i topology-02-CA ERROR: Banner is not installed [root@pki1 fedora]# pki-server banner-validate -i topology-02-CA ----------------------- Banner is not installed ----------------------- [root@pki1 fedora]# echo "Warning" > /etc/pki/topology-02-CA/banner.txt [root@pki1 fedora]# pki-server banner-validate -i topology-02-CA ERROR: invalid mode: 'UTF-8' [root@pki1 fedora]# file /etc/pki/topology-02-CA/banner.txt /etc/pki/topology-02-CA/banner.txt: ASCII text [root@pki1 fedora]# pki-server banner-show -i topology-02-CA ERROR: invalid mode: 'UTF-8' Stack trace: [root@pki1 ~]# pki-server banner-show -i topology-02-CA -vv Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/pki/server/pkiserver.py", line 119, in <module> cli.execute(sys.argv) File "/usr/lib/python3.6/site-packages/pki/server/pkiserver.py", line 111, in execute super(PKIServerCLI, self).execute(args) File "/usr/lib/python3.6/site-packages/pki/cli/__init__.py", line 204, in execute module.execute(module_args) File "/usr/lib/python3.6/site-packages/pki/cli/__init__.py", line 204, in execute module.execute(module_args) File "/usr/lib/python3.6/site-packages/pki/server/cli/banner.py", line 97, in execute print(instance.get_banner()) File "/usr/lib/python3.6/site-packages/pki/server/__init__.py", line 980, in get_banner return codecs.open(self.banner_file, "UTF-8").read().strip() File "/usr/lib64/python3.6/codecs.py", line 897, in open file = builtins.open(filename, mode, buffering) ValueError: invalid mode: 'UTF-8' ERROR: invalid mode: 'UTF-8' Build: [root@pki1 ~]# rpm -qa | grep pki python3-pki-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-ca-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-tps-10.6.1-3.20180520020012.b743abbe.fc28.x86_64 pki-tools-10.6.1-3.20180520020012.b743abbe.fc28.x86_64 pki-server-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-tks-10.6.1-3.20180520020012.b743abbe.fc28.noarch dogtag-pki-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-base-java-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-ocsp-10.6.1-3.20180520020012.b743abbe.fc28.noarch dogtag-pki-server-theme-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-base-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-console-10.6.1-3.20180520020012.b743abbe.fc28.noarch dogtag-pki-console-theme-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-kra-10.6.1-3.20180520020012.b743abbe.fc28.noarch pki-symkey-10.6.1-3.20180520020012.b743abbe.fc28.x86_64
Metadata Update from @bbhavsar: - 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 type adjusted to None - Custom field version adjusted to None - Issue priority set to: blocker
Metadata Update from @mharmsen: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @edewata: - Issue assigned to edewata
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
This problem is no longer happening in the latest build.
Metadata Update from @edewata: - Issue set to the milestone: 10.6.7 (was: 0.0 NEEDS_TRIAGE)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/3140
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.