Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

flux resource list reports ERROR: ENOENT: No such file or directory when inventory not available #5882

Open
grondo opened this issue Apr 12, 2024 · 1 comment
Open

flux resource list reports ERROR: ENOENT: No such file or directory when inventory not available #5882

grondo opened this issue Apr 12, 2024 · 1 comment

Comments

@grondo
Copy link
Contributor

grondo commented Apr 12, 2024

The resource module returns an errno only when the inventory isn't available. This can be confusing to admins, so perhaps a human readable error should be added for this case. Other error returns for the status RPCs should be audited as well.
grondo added a commit to grondo/flux-core that referenced this issue Apr 12, 2024
@grondo
resource: improve errors from resource.*status RPCs
eadc2b7 
Problem: When a resource.status or resource.sched-status RPC is send
to the resource module and inventory->R is not yet set, tools such as
`flux resource list` report the mysterious error:

 flux-resource: ERROR: ENOENT: No such file or directory

For this specific case, set a human readable error string to

 resource inventory currently unavailable

To give a better idea of what's gone wrong.

Improve the error messages for several other (very unlikely) cases
in the response handling.

Fixes flux-framework#5882
@grondo
Copy link
Contributor Author

grondo commented Apr 13, 2024

Hm, it seems like we should have gotten a slightly more descriptive error message here:

flux-core/src/modules/resource/status.c

Lines 82 to 85 in 7d61efd

if (!(o = prepare_status_payload (status))) {
errprintf (&error, "error preparing response: %s", strerror (errno));
goto error;
}

Maybe the issue is on the Python side. More investigation required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@grondo