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.

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

tests: make sure nvmetcli and nvme-cli are up to date #58290

Merged
merged 1 commit into from
Jun 28, 2024

Conversation

guits
Copy link
Contributor

@guits guits commented Jun 26, 2024

Otherwise jobs end up with the following failure:

2024-06-25T14:22:18.659 INFO:teuthology.orchestra.run.smithi098.stderr:Failed to write to /dev/nvme-fabrics: Invalid argument

Also, the output of nvme list has changed so we have to update qa/tasks/nvme_loop.py accordingly.

@guits guits force-pushed the fix_nvme_loop branch 3 times, most recently from 2e29c6a to 503c57e Compare June 27, 2024 11:46
Otherwise jobs end up with the following failure:

```
2024-06-25T14:22:18.659 INFO:teuthology.orchestra.run.smithi098.stderr:Failed to write to /dev/nvme-fabrics: Invalid argument
```

Also, the output of nvme list has changed so we have to update
qa/tasks/nvme_loop.py accordingly.

Fixes: https://tracker.ceph.com/issues/66707

Signed-off-by: Guillaume Abrioux <[email protected]>
@guits
Copy link
Contributor Author

guits commented Jun 27, 2024

jenkins test make check

@guits
Copy link
Contributor Author

guits commented Jun 27, 2024

jenkins test api

1 similar comment
@guits
Copy link
Contributor Author

guits commented Jun 28, 2024

jenkins test api

@guits guits merged commit cbc6d66 into ceph:main Jun 28, 2024
11 checks passed
@guits guits deleted the fix_nvme_loop branch June 28, 2024 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants