Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1724894

Summary:	[RHEL8]warning: bogus date in %changelog: Tue May 08 2019
Product:	Red Hat Enterprise Linux 8	Reporter:	Zhang Yi <yizhan>
Component:	nvme-cli	Assignee:	David Milburn <dmilburn>
Status:	CLOSED ERRATA	QA Contact:	Zhang Yi <yizhan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	dmilburn
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nvme-cli-1.9-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1724267	Environment:
Last Closed:	2020-04-28 17:03:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1724267
Bug Blocks:	1776957

Comment 2 David Milburn 2020-01-14 17:29:50 UTC

Hi Yi,

Would you be able to do a quick test on nvme-cli-1.9-2.TEST.el8.x86_64.rpm?

http://people.redhat.com/dmilburn/.bz1753373_bz1731599.98030607080910702011/

If it works for you please give a qa_ack. Thanks.

Comment 3 Zhang Yi 2020-01-15 07:41:19 UTC

Hi David

This issue need the src package to verify.

Thanks
Yi

Comment 4 David Milburn 2020-01-15 11:05:55 UTC

Hi Yi,

(In reply to Zhang Yi from comment #3)
> Hi David
> 
> This issue need the src package to verify.
> 

Oops, sorry, please check now. Thanks.

Comment 5 David Milburn 2020-01-15 17:03:50 UTC

I think this one is fixed. Thanks.

Comment 6 Zhang Yi 2020-01-16 08:05:06 UTC

(In reply to David Milburn from comment #5)
> I think this one is fixed. Thanks.

Yes, it fixed now.

[root@rdma-perf-07 ~]$ rpmbuild -bp rpmbuild/SPECS/nvme-cli.spec 
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.PUaaCd
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd /root/rpmbuild/BUILD
+ rm -rf nvme-cli-1.9
+ /usr/bin/gzip -dc /root/rpmbuild/SOURCES/v1.9.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd nvme-cli-1.9
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ echo 'Patch #0 (nvmf-autoconnect-fix-abls-path-systemctl-patch):'
Patch #0 (nvmf-autoconnect-fix-abls-path-systemctl-patch):
+ /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
patching file nvmf-autoconnect/udev-rules/70-nvmf-autoconnect.rules
+ echo 'Patch #1 (systemd-fix-echo-call-with-absolute-path-patch):'
Patch #1 (systemd-fix-echo-call-with-absolute-path-patch):
+ /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
patching file nvmf-autoconnect/systemd/nvmf-connect@.service
+ echo 'Patch #2 (nvme-cli-check-sysfs-interface-before-nvme-disc-patch):'
Patch #2 (nvme-cli-check-sysfs-interface-before-nvme-disc-patch):
+ /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
patching file nvmf-autoconnect/systemd/nvmefc-boot-connections.service
+ echo 'Patch #3 (nvmf-autoconnect-add-udev-rules-to-set-iopolicy-netapp-patch):'
Patch #3 (nvmf-autoconnect-add-udev-rules-to-set-iopolicy-netapp-patch):
+ /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
patching file nvmf-autoconnect/udev-rules/71-nvmf-iopolicy-netapp.rules
+ echo 'Patch #4 (fix-systemd-service-script-use-connect-args-patch):'
Patch #4 (fix-systemd-service-script-use-connect-args-patch):
+ /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
patching file nvmf-autoconnect/systemd/nvmf-connect@.service
+ exit 0

Comment 8 Zhang Yi 2020-01-17 07:56:45 UTC

(In reply to Zhang Yi from comment #6)
> (In reply to David Milburn from comment #5)
> > I think this one is fixed. Thanks.
> 
> Yes, it fixed now.
> 
> [root@rdma-perf-07 ~]$ rpmbuild -bp rpmbuild/SPECS/nvme-cli.spec 
> Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.PUaaCd
> + umask 022
> + cd /root/rpmbuild/BUILD
> + cd /root/rpmbuild/BUILD
> + rm -rf nvme-cli-1.9
> + /usr/bin/gzip -dc /root/rpmbuild/SOURCES/v1.9.tar.gz
> + /usr/bin/tar -xof -
> + STATUS=0
> + '[' 0 -ne 0 ']'
> + cd nvme-cli-1.9
> + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
> + echo 'Patch #0 (nvmf-autoconnect-fix-abls-path-systemctl-patch):'
> Patch #0 (nvmf-autoconnect-fix-abls-path-systemctl-patch):
> + /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
> patching file nvmf-autoconnect/udev-rules/70-nvmf-autoconnect.rules
> + echo 'Patch #1 (systemd-fix-echo-call-with-absolute-path-patch):'
> Patch #1 (systemd-fix-echo-call-with-absolute-path-patch):
> + /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
> patching file nvmf-autoconnect/systemd/nvmf-connect@.service
> + echo 'Patch #2 (nvme-cli-check-sysfs-interface-before-nvme-disc-patch):'
> Patch #2 (nvme-cli-check-sysfs-interface-before-nvme-disc-patch):
> + /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
> patching file nvmf-autoconnect/systemd/nvmefc-boot-connections.service
> + echo 'Patch #3
> (nvmf-autoconnect-add-udev-rules-to-set-iopolicy-netapp-patch):'
> Patch #3 (nvmf-autoconnect-add-udev-rules-to-set-iopolicy-netapp-patch):
> + /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
> patching file nvmf-autoconnect/udev-rules/71-nvmf-iopolicy-netapp.rules
> + echo 'Patch #4 (fix-systemd-service-script-use-connect-args-patch):'
> Patch #4 (fix-systemd-service-script-use-connect-args-patch):
> + /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
> patching file nvmf-autoconnect/systemd/nvmf-connect@.service
> + exit 0

Move to VERIFIED.

Comment 10 errata-xmlrpc 2020-04-28 17:03:41 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1915