Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-07-28T11:43:11ZPulp
Planio Debian Support - Issue #9164 (CLOSED - CURRENTRELEASE): Dropping Python 3.6 and 3.7 from the 2.14...https://pulp.plan.io/issues/91642021-07-28T11:43:11Zquba42
<p>It looks like this was merged prematurely on my part.</p>
<p>Users have reported the following:</p>
<pre><code>I tried to update pulp_deb plugins using ansible but getting error as per below.
TASK [pulp.pulp_installer.pulp_common : Install prerequisites] ******************************************************************************************************************************************************************************
fatal: [pulptest008.karmalab.net]: FAILED! => {"changed": false, "msg": "No package matching 'rh-python38-python' found available, installed or updated", "rc": 126, "results": ["python-setuptools-0.9.8-7.el7.noarch providing python-setuptools is already installed", "No package matching 'rh-python38-python' found available, installed or updated"]}
</code></pre>
<p>Fresh installs are also suffering weird dependency effects where Python 3 is not being installed at all.</p> Debian Support - Issue #8910 (CLOSED - CURRENTRELEASE): When syncing with architecture filtering,...https://pulp.plan.io/issues/89102021-06-17T09:33:41Zquba42
<p>In addition to upstream repos using this format, this also affects pulp_deb (APT publisher) to pulp_deb syncs.</p>
<p>See also: <a href="https://community.theforeman.org/t/katello-3-18-debian-packages-are-not-fully-synchronized-on-smart-proxy/24047" class="external">https://community.theforeman.org/t/katello-3-18-debian-packages-are-not-fully-synchronized-on-smart-proxy/24047</a></p> Debian Support - Task #8682 (CLOSED - CURRENTRELEASE): Migrate to new Distribution model for pulp...https://pulp.plan.io/issues/86822021-05-03T12:21:35Zquba42Debian Support - Issue #8671 (CLOSED - CURRENTRELEASE): Sync with Main Debian Repo fails on a tra...https://pulp.plan.io/issues/86712021-04-30T08:43:16Ztp-hlawatsch
<p>Hello everybody,</p>
<p>we plan to use pulp as our main tool for repos . We testing at the moment Debian mirroring
Our pulp testinstance is runing with the latest offical docker image</p>
<p>This is the configured remote repo</p>
<p>{
"name": "debian",
"url": "<a href="http://ftp.de.debian.org/debian/" class="external">http://ftp.de.debian.org/debian/</a>",
"ca_cert": null,
"client_cert": null,
"client_key": null,
"tls_validation": false,
"proxy_url": null,
"proxy_username": null,
"proxy_password": null,
"username": null,
"password": null,
"pulp_labels": {},
"download_concurrency": "10",
"policy": "immediate",
"total_timeout": null,
"connect_timeout": null,
"sock_connect_timeout": null,
"sock_read_timeout": null,
"rate_limit": null,
"distributions": "buster",
"components": "main",
"architectures": "amd64",
"sync_sources": false,
"sync_udebs": false,
"sync_installer": false,
"gpgkey": null,
"ignore_missing_package_indices": false
}</p>
<p>the sync run in to the following error</p>
<p>{
"pulp_href": "/pulp/api/v3/tasks/a7bd851b-f001-4f5f-89eb-0e0de529a556/",
"pulp_created": "2021-04-30T07:53:11.537345Z",
"state": "failed",
"name": "pulp_deb.app.tasks.synchronizing.synchronize",
"logging_cid": "00de2125667f4c7e8b8e01554c401eeb",
"started_at": "2021-04-30T07:53:11.648803Z",
"finished_at": "2021-04-30T07:53:19.135647Z",
"error": {
"traceback": " File "/usr/local/lib/python3.6/site-packages/rq/worker.py", line 1008, in perform_job\n rv = job.perform()\n File "/usr/local/lib/python3.6/site-packages/rq/job.py", line 706, in perform\n self._result = self._execute()\n File "/usr/local/lib/python3.6/site-packages/rq/job.py", line 729, in _execute\n result = self.func(*self.args, **self.kwargs)\n File "/usr/local/lib/python3.6/site-packages/pulp_deb/app/tasks/synchronizing.py", line 122, in synchronize\n DebDeclarativeVersion(first_stage, repository, mirror=mirror).create()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/declarative_version.py", line 149, in create\n loop.run_until_complete(pipeline)\n File "/usr/lib64/python3.6/asyncio/base_events.py", line 484, in run_until_complete\n return future.result()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/api.py", line 225, in create_pipeline\n await asyncio.gather(*futures)\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/api.py", line 43, in <strong>call</strong>\n await self.run()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/artifact_stages.py", line 266, in run\n RemoteArtifact.objects.bulk_get_or_create(self._needed_remote_artifacts(batch))\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/artifact_stages.py", line 324, in _needed_remote_artifacts\n msg.format(rp=content_artifact.relative_path, c=d_content.content)\n",
"description": "No declared artifact with relative path "dists/buster/main/i18n/Translation-ml.bz2" for content """
},</p>
<p>We do not see a misconfiguration on our side so I raised this issue here</p>
<p>Regards
Stephan Hlawatsch</p> Debian Support - Task #8642 (CLOSED - DUPLICATE): Fix nightly testshttps://pulp.plan.io/issues/86422021-04-28T07:05:19Zquba42
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/404":<a href="https://github.com/pulp/pulp_deb/issues/404" class="external">https://github.com/pulp/pulp_deb/issues/404</a></p>
<hr>
<p>Nightly tests have been consistently failing for a long time.</p>
<p>Nightly tests provide important information and should be fixed.</p> Debian Support - Task #8640 (CLOSED - DUPLICATE): Signature tests should provide proper SigningSe...https://pulp.plan.io/issues/86402021-04-28T06:59:31Zquba42
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/402":<a href="https://github.com/pulp/pulp_deb/issues/402" class="external">https://github.com/pulp/pulp_deb/issues/402</a></p>
<hr>
<p>The setup of the SigningService for the test pipeline is currently a dirty hack, that causes frequent failures and complications in new pipelines.</p>
<p>It should be possible for the test itself to handle the setup using the pulpcore-manager utility functions provided by pulp-smash.</p> Debian Support - Issue #8506 (CLOSED - CURRENTRELEASE): apt install - File has unexpected size - ...https://pulp.plan.io/issues/85062021-04-02T18:01:50Zrgp
<p>Apt install downloads packages by default using http pipelining. However, apt relies on "Size" field from "Packages" file to match responses, but pulp_deb repos do not appear to have it. In certain condition that causes apt to fail.</p>
<pre><code>root@aptbug:~# curl -sS https://repo.saltproject.io/py3/ubuntu/18.04/amd64/latest/dists/bionic/main/binary-amd64/Packages | grep -c ^Size
14
root@aptbug:~# curl -sS http://foreman.example.com/pulp/deb/MyOrg/Library/custom/Saltstack/ubuntu_18_04_salt_latest/dists/default/all/binary-amd64/Packages | grep -c ^Size
0
</code></pre>
<p>More details: <a href="https://projects.theforeman.org/issues/32178#note-9" class="external">https://projects.theforeman.org/issues/32178#note-9</a></p> Debian Support - Task #8388 (CLOSED - CURRENTRELEASE): Handle ALLOWED_CONTENT_CHECKSUMS settinghttps://pulp.plan.io/issues/83882021-03-11T14:59:24Zquba42
<p>Right now the pulp_deb plugin is dependend on the following hashs being present on artifacts: md5, sha1, sha256, sha512.</p>
<p>Starting with pulpcore 3.11 will exclude md5 and sha1 from ALLOWED_CONTENT_CHECKSUMS by default.</p>
<p>Pulp deb will need to handle this gracefully. There is still some debate on whether pulp_deb makes sense without md5 feature wise. As a result, the solution may need to include demanding or encouraging a different configuration from pulp_deb users than the pulpcore default configuration.</p>
<p>See the following mailing list threads:</p>
<ul>
<li><a href="https://listman.redhat.com/archives/pulp-dev/2021-February/msg00017.html" class="external">https://listman.redhat.com/archives/pulp-dev/2021-February/msg00017.html</a></li>
<li><a href="https://listman.redhat.com/archives/pulp-dev/2021-March/msg00013.html" class="external">https://listman.redhat.com/archives/pulp-dev/2021-March/msg00013.html</a></li>
</ul> Debian Support - Issue #8232 (CLOSED - CURRENTRELEASE): APT publications do not retain all fields...https://pulp.plan.io/issues/82322021-02-09T15:26:04Zmathiasdasilva
<p>Dear support,</p>
<p>When we plug our servers to our apt pulp repository, same packages are installed again an again.
I checked and there is a difference between source package manifest and pulp deb manifest.
There is an example for wget :</p>
<p>Ubuntu repository :</p>
<p>Package: wget
Architecture: amd64
Version: 1.20.3-1ubuntu1
Multi-Arch: foreign
Priority: standard
Section: web
Origin: Ubuntu
Maintainer: Ubuntu Developers <a href="mailto:ubuntu-devel-discuss@lists.ubuntu.com" class="email">ubuntu-devel-discuss@lists.ubuntu.com</a>
Original-Maintainer: Noël Köthe <a href="mailto:noel@debian.org" class="email">noel@debian.org</a>
Bugs: <a href="https://bugs.launchpad.net/ubuntu/+filebug" class="external">https://bugs.launchpad.net/ubuntu/+filebug</a>
Installed-Size: 992
Depends: libc6 (>= 2.17), libidn2-0 (>= 0.6), libpcre2-8-0 (>= 10.32), libpsl5 (>= 0.16.0), libssl1.1 (>= 1.1.0), libuuid1 (>= 2.16), zlib1g (>= 1:1.1.4)
Recommends: ca-certificates
Conflicts: wget-ssl
Filename: pool/main/w/wget/wget_1.20.3-1ubuntu1_amd64.deb
Size: 348824
MD5sum: ae9eb859432505828dab97c80edcb5b5
SHA1: 45504b6e948d4f1a7e2ba0233bb57a67b392ceea
SHA256: 68144dde6d45e1a54fa983d6d10be7043e6695e259c8d2b12fd03ea5e475d56a
Homepage: <a href="https://www.gnu.org/software/wget/" class="external">https://www.gnu.org/software/wget/</a>
Description: retrieves files from the web
Task: standard
Description-md5: 63a4a740bcd9e8e94bf661e4f1806e02</p>
<p>Pulp repository :
Package: wget
Version: 1.20.3-1ubuntu1
Architecture: amd64
Section: web
Priority: standard
Origin: Ubuntu
Bugs: <a href="https://bugs.launchpad.net/ubuntu/+filebug" class="external">https://bugs.launchpad.net/ubuntu/+filebug</a>
Installed-Size: 992
Maintainer: Ubuntu Developers <a href="mailto:ubuntu-devel-discuss@lists.ubuntu.com" class="email">ubuntu-devel-discuss@lists.ubuntu.com</a>
Description: retrieves files from the web
Homepage: <a href="https://www.gnu.org/software/wget/" class="external">https://www.gnu.org/software/wget/</a>
Conflicts: wget-ssl
Depends: libc6 (>= 2.17), libidn2-0 (>= 0.6), libpcre2-8-0 (>= 10.32), libpsl5 (>= 0.16.0), libssl1.1 (>= 1.1.0), libuuid1 (>= 2.16), zlib1g (>= 1:1.1.4)
Recommends: ca-certificates
MD5sum: ae9eb859432505828dab97c80edcb5b5
SHA1: 45504b6e948d4f1a7e2ba0233bb57a67b392ceea
SHA256: 68144dde6d45e1a54fa983d6d10be7043e6695e259c8d2b12fd03ea5e475d56a
Filename: pool/main/w/wget/wget_1.20.3-1ubuntu1_amd64.deb</p>
<p>This behavior seems to be identical to this ticket : <a href="https://pulp.plan.io/issues/7190" class="external">https://pulp.plan.io/issues/7190</a></p>
<p>Pulp version:</p>
<p>Pulp core: 3.9.0
Pulp deb: 2.9.0</p>
<p>Best regards,</p> CertGuard - Issue #7182 (CLOSED - CURRENTRELEASE): The docs aren't buildinghttps://pulp.plan.io/issues/71822020-07-21T20:25:23Zbmbouterbmbouter@redhat.com
<a name="The-docs-site-on-RTD-is-no-longer-building"></a>
<h2 >The docs site on RTD is no longer building<a href="#The-docs-site-on-RTD-is-no-longer-building" class="wiki-anchor">¶</a></h2>
<p>You can see the 1.0.0 and 1.0.1 changelogs are not present: <a href="https://pulp-certguard.readthedocs.io/en/latest/changes.html" class="external">https://pulp-certguard.readthedocs.io/en/latest/changes.html</a></p>
<p>The last successful build was Completed June 30, 2020. 6:54 p.m from (6d951eb3203a19f627d1f3e0e729f8c3a3107c0b)</p>
<p>The RTD builder fails with:</p>
<pre><code>DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Collecting PyOpenSSL
Downloading pyOpenSSL-19.1.0-py2.py3-none-any.whl (53 kB)
ERROR: Could not find a version that satisfies the requirement pulpcore<3.6,>=3.3 (from -r requirements.txt (line 2)) (from versions: 3.0.0a1.dev3, 3.0.0a1.dev4, 3.0.0a1.dev5, 3.0.0a1, 3.0.0a2, 3.0.0a3, 3.0.0a4, 3.0.0a5, 3.0.0a6, 3.0.0a7, 3.0.0a8, 3.0.0a9, 3.0.0a10, 3.0.0a11, 3.0.0a12, 3.0.0a13, 3.0.0a14, 3.0.0a15, 3.0.0a16, 3.0.0a17, 3.0.0a18, 3.0.0a19, 3.0.0a20, 3.0.0a21, 3.0.0a22, 3.0.0a23, 3.0.0a24, 3.0.0a25, 3.0.0a26, 3.0.0a27, 3.0.0a28, 3.0.0a29, 3.0.0b1, 3.0.0b2, 3.0.0b3, 3.0.0b4, 3.0.0b5, 3.0.0b6, 3.0.0b7)
ERROR: No matching distribution found for pulpcore<3.6,>=3.3 (from -r requirements.txt (line 2))
</code></pre> CertGuard - Task #6830 (CLOSED - DUPLICATE): Update yum/dnf documentation on how .repo files can ...https://pulp.plan.io/issues/68302020-05-26T20:09:01Zbmbouterbmbouter@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp-certguard/142":<a href="https://github.com/pulp/pulp-certguard/issues/142" class="external">https://github.com/pulp/pulp-certguard/issues/142</a></p>
<hr>
<p>The cert and key from clients now occur during TLS submission. That means <a href="https://pulp-certguard.readthedocs.io/en/latest/yum-howto.html" class="external">these docs</a> are out of date.</p>
<p>We should update the docs to show how a yum/dnf client can be configured to submit the cert and key via TLS.</p> Container Support - Test #5267 (CLOSED - WONTFIX): Test - As a user I can filter Manifests and Ma...https://pulp.plan.io/issues/52672019-08-13T18:36:40Zkersom
<p>ManifestTags will need a custom filter to allow the query through tagged_manifest.media_type.</p> Container Support - Test #5260 (CLOSED - WONTFIX): Test - As a user, I can filter Manifests and M...https://pulp.plan.io/issues/52602019-08-13T17:35:25Zkersom
<p>For example, I would like to retrieve all v1 and v2 manifests without any manifest lists.</p> Pulp - Story #3778 (CLOSED - CURRENTRELEASE): [Epic] As a user, I can run Pulp 3 in a FIPS-enable...https://pulp.plan.io/issues/37782018-06-21T16:13:49ZdaviddavisCrane - Issue #2719 (CLOSED - WONTFIX): Need to choose a port, and ship SELinux policy for networ...https://pulp.plan.io/issues/27192017-04-17T18:56:09ZIchimonji10jerebear@protonmail.com
<p>The Crane documentation weakly suggests that port 5,000 be used for its configuration. Additionally, the Crane RPM package does not (AFAICT) install an SELinux policy that makes some port available for use. Can we more strongly suggest which port should be used and make the Crane RPM package install an SELinux policy making that network port available for use?</p>
<p>There's at least two good options for which port to use. One is to use 5,000, because we already weakly suggest that users use this port, and because the Docker documentation <a href="https://docs.docker.com/engine/reference/commandline/dockerd/#insecure-registries" class="external">weakly suggests</a> that port 5,000 be used for private registries. Another option is to use the official ports assigned to Docker. From <code>/etc/services</code>:</p>
<pre><code>docker 2375/tcp # Docker REST API (plain text)
docker-s 2376/tcp # Docker REST API (ssl)
</code></pre>
<p>Given that Crane implements a sub-set of the Docker API, why not use the ports set aside for the Docker API?</p>
<p>Here's what happens when the following configuration file is installed in <code>/etc/httpd/conf.d/pulp_crane.conf</code>:</p>
<pre><code># Place this config in /etc/httpd/conf.d/. Use with Apache 2.4+. See:
#
# * https://docs.pulpproject.org/plugins/crane/index.html
# * https://modwsgi.readthedocs.io/en/develop/user-guides/quick-configuration-guide.html
#
# Note the following entries in /etc/services:
#
# docker 2375/tcp
# docker-s 2376/tcp
#
# At the same time, the Docker documentation weakly suggests using port 5000/tcp
# for a private registry.
#
Listen 2375
<VirtualHost *:2375>
WSGIScriptAlias / /usr/share/crane/crane.wsgi
<Location /crane>
Require host localhost
</Location>
<Directory /usr/share/crane/>
Require all granted
</Directory>
</VirtualHost>
</code></pre>
<p>When <code>systemctl start httpd</code> is executed on Fedora 24, the following is logged:</p>
<pre><code>[root@fedora-24-pulp-2-12 ~]# journalctl -u httpd | tail
Apr 17 14:39:03 fedora-24-pulp-2-12 systemd[1]: Starting The Apache HTTP Server...
Apr 17 14:39:03 fedora-24-pulp-2-12 httpd[3607]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.100.131. Set the 'ServerName' directive globally to suppress this message
Apr 17 14:39:03 fedora-24-pulp-2-12 httpd[3607]: (13)Permission denied: AH00072: make_sock: could not bind to address [::]:2375
Apr 17 14:39:03 fedora-24-pulp-2-12 httpd[3607]: (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:2375
Apr 17 14:39:03 fedora-24-pulp-2-12 httpd[3607]: no listening sockets available, shutting down
Apr 17 14:39:03 fedora-24-pulp-2-12 httpd[3607]: AH00015: Unable to open logs
Apr 17 14:39:03 fedora-24-pulp-2-12 systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 17 14:39:03 fedora-24-pulp-2-12 systemd[1]: Failed to start The Apache HTTP Server.
Apr 17 14:39:03 fedora-24-pulp-2-12 systemd[1]: httpd.service: Unit entered failed state.
Apr 17 14:39:03 fedora-24-pulp-2-12 systemd[1]: httpd.service: Failed with result 'exit-code'.
</code></pre>
<p>Here's some debugging output:</p>
<pre><code>[root@fedora-24-pulp-2-12 ~]# audit2allow -al
#============= httpd_t ==============
#!!!! This avc can be allowed using the boolean 'httpd_use_openstack'
allow httpd_t commplex_main_port_t:tcp_socket name_bind;
[root@fedora-24-pulp-2-12 ~]# audit2allow -Ral
could not open interface info [/var/lib/sepolgen/interface_info]
[root@fedora-24-pulp-2-12 ~]# cat /var/log/audit/audit.log
type=USER_AVC msg=audit(1492453129.831:473): pid=691 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0
:c0.c1023 msg='avc: received policyload notice (seqno=2) exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
type=MAC_POLICY_LOAD msg=audit(1492453129.841:474): policy loaded auid=0 ses=3
type=USER_AVC msg=audit(1492453134.644:475): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: re
ceived setenforce notice (enforcing=0) exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
type=USER_AVC msg=audit(1492453134.644:476): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: re
ceived policyload notice (seqno=2) exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
type=AVC msg=audit(1492453134.689:477): avc: denied { name_bind } for pid=1867 comm="httpd" src=5000 scontext=system_u:system_r:htt
pd_t:s0 tcontext=system_u:object_r:commplex_main_port_t:s0 tclass=tcp_socket permissive=1
type=SERVICE_START msg=audit(1492453134.743:478): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='uni
t=httpd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
type=CRYPTO_KEY_USER msg=audit(1492453136.054:479): pid=1044 uid=0 auid=0 ses=1 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=d
estroy kind=server fp=SHA256:82:0b:b4:05:e1:a8:86:b9:12:b9:63:2c:93:47:23:02:ac:ef:28:f3:c3:d9:04:83:e7:de:29:4f:04:c9:50:83 direction
=? spid=1081 suid=0 exe="/usr/sbin/sshd" hostname=? addr=192.168.100.1 terminal=? res=success'
type=CRYPTO_KEY_USER msg=audit(1492453136.055:480): pid=1044 uid=0 auid=0 ses=1 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=d
estroy kind=session fp=? direction=both spid=1081 suid=0 rport=55880 laddr=192.168.100.131 lport=22 exe="/usr/sbin/sshd" hostname=? a
ddr=192.168.100.1 terminal=? res=success'
type=USER_END msg=audit(1492453136.062:481): pid=1044 uid=0 auid=0 ses=1 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=PAM:sess
ion_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_namespace,pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="ro
ot" exe="/usr/sbin/sshd" hostname=192.168.100.1 addr=192.168.100.1 terminal=ssh res=success'
type=CRED_DISP msg=audit(1492453136.063:482): pid=1044 uid=0 auid=0 ses=1 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=PAM:set
cred grantors=pam_env,pam_unix,pam_reauthorize acct="root" exe="/usr/sbin/sshd" hostname=192.168.100.1 addr=192.168.100.1 terminal=ssh
res=success'
type=CRYPTO_KEY_USER msg=audit(1492453136.063:483): pid=1044 uid=0 auid=0 ses=1 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=d
estroy kind=server fp=SHA256:6c:43:63:95:4b:66:1f:fd:ca:5b:26:56:62:ee:5e:38:21:ed:a9:1b:64:8d:b1:ef:29:7d:ee:76:41:af:18:b7 direction
=? spid=1044 suid=0 exe="/usr/sbin/sshd" hostname=? addr=192.168.100.1 terminal=? res=success'
type=CRYPTO_KEY_USER msg=audit(1492453136.065:484): pid=1044 uid=0 auid=0 ses=1 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=d
estroy kind=server fp=SHA256:6c:fc:0e:72:92:8d:8e:8d:c0:3f:6a:9a:02:9e:59:73:a9:18:87:e3:bf:f2:28:d3:dd:30:06:e5:41:f4:f1:66 direction
=? spid=1044 suid=0 exe="/usr/sbin/sshd" hostname=? addr=192.168.100.1 terminal=? res=success'
type=CRYPTO_KEY_USER msg=audit(1492453136.065:485): pid=1044 uid=0 auid=0 ses=1 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=d
estroy kind=server fp=SHA256:82:0b:b4:05:e1:a8:86:b9:12:b9:63:2c:93:47:23:02:ac:ef:28:f3:c3:d9:04:83:e7:de:29:4f:04:c9:50:83 direction
=? spid=1044 suid=0 exe="/usr/sbin/sshd" hostname=? addr=192.168.100.1 terminal=? res=success'
</code></pre>
<p>Similar errors occur when port 5,000 is listed in the Apache configuration file, and similar errors also occur on Fedora 25 and RHEL 7.</p>