-
Notifications
You must be signed in to change notification settings - Fork 45
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
salt: Add a udevadm trigger when persistentPath
does not exists
#3630
salt: Add a udevadm trigger when persistentPath
does not exists
#3630
Conversation
Hello teddyandrieux,My role is to assist you with the merge of this Status report is not available. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1f28c03
to
cf178f0
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
cf178f0
to
8e726f3
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
In some cases, a volume may be properly created but the path symlink ( `/dev/disks/by-XXX/`) does not exist because udevadm did not get triggered on this device for... whatever reason. To avoid that kind of issue we now trigger udevadm manually in the salt execution module when the `persistentPath` does not exist and the volume is actually "prepared". Fixes: #3341
8e726f3
to
3ff1e49
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
|
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
/approve |
Build failedThe build for commit did not succeed in branch bugfix/update-udev-db-before-dev-detect. The following options are set: approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue None. Goodbye teddyandrieux. |
In some cases, a volume may be properly created but the path symlink (
/dev/disks/by-XXX/
) does not exist because udevadm did not gettriggered on this device for... whatever reason.
To avoid that kind of issue we now trigger udevadm manually in the salt
execution module when the
persistentPath
does not exist and thevolume is actually "prepared".
Fixes: #3341