Bug 2033678

Summary:	nvmetcli initial install fails to load preferences file
Product:	Red Hat Enterprise Linux 9	Reporter:	John Pittman <jpittman>
Component:	nvmetcli	Assignee:	Maurizio Lombardi <mlombard>
Status:	CLOSED MIGRATED	QA Contact:	Storage QE <storage-qe>
Severity:	low	Docs Contact:
Priority:	medium
Version:	9.0	CC:	jbrassow
Target Milestone:	rc	Keywords:	MigratedToJIRA, Reopened, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-23 12:55:53 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:

Description John Pittman 2021-12-17 15:27:46 UTC

Description of problem:

nvmetcli package initial install fails to load preferences file

[root@localhost ~]# nvmetcli
bash: nvmetcli: command not found...
Install package 'nvmetcli' to provide command 'nvmetcli'? [N/y] y


 * Waiting in queue... 
 * Loading list of packages.... 
The following packages have to be installed:
 nvmetcli-0.7-3.el9.noarch	An adminstration shell for NVMe storage targets
Proceed with changes? [N/y] y


 * Waiting in queue... 
 * Waiting for authentication... 
 * Waiting in queue... 
 * Downloading packages... 
 * Requesting data... 
 * Testing changes... 
 * Installing packages... 
Warning: Could not load preferences file /root/.nvmetcli/prefs.bin.
/> exit

Version-Release number of selected component (if applicable):

nvme-cli-1.14-3.el9.x86_64
nvmetcli-0.7-3.el9.noarch
kernel-5.14.0-21.el9.x86_64

How reproducible:

Every time on first install

Actual results:

Warning about failure to load preferences file

Expected results:

Initial preferences should be loaded successfully

Comment 2 RHEL Program Management 2023-06-17 07:29:17 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 3 Maurizio Lombardi 2023-06-17 08:37:52 UTC

Reopen it, I will look at it when time permits

Comment 5 RHEL Program Management 2023-09-23 12:54:18 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-23 12:55:53 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.