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

Return empty list of loop devices when losetup doesn't print anything #1776

Merged

Conversation

zimnx
Copy link
Collaborator

@zimnx zimnx commented Feb 28, 2024

Version of losetup installed on EKS has different behavior when there are no loop devices on the node. On GKE and local env, it returns an empty list of loop devices as json output, where on EKS it doesn't print anything, even though we ask for json explicitly.
Losetup library now supports both behaviors.

Fixes #1775

@zimnx zimnx added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 28, 2024
@scylla-operator-bot scylla-operator-bot bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 28, 2024
@scylla-operator-bot scylla-operator-bot bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 28, 2024
Copy link
Contributor

@tnozicka tnozicka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
(lgtm)

Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tnozicka, zimnx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Version of `losetup` installed on EKS has different behavior when there
are no loop devices on the node. On GKE and local env, it returns an
empty list of loop devices as json output, where on EKS it doesn't print
anything, even though we ask for json explicitly.
Losetup library now supports both behaviors.
@zimnx zimnx force-pushed the mz/fix-losetup-prinitng-nothing branch from fbafbf9 to 77ee77c Compare February 29, 2024 09:45
@zimnx
Copy link
Collaborator Author

zimnx commented Feb 29, 2024

Flake - #1426 (comment)
/retest

Copy link
Contributor

@tnozicka tnozicka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
thanks

@scylla-operator-bot scylla-operator-bot bot added the lgtm Indicates that a PR is ready to be merged. label Feb 29, 2024
@scylla-operator-bot scylla-operator-bot bot merged commit 30e8d2f into scylladb:master Feb 29, 2024
12 checks passed
@zimnx zimnx deleted the mz/fix-losetup-prinitng-nothing branch February 29, 2024 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

NodeConfig can't create raid device on EKS
2 participants