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

core: revert increase storage deviceset name limit to 50 (backport #14362) #14369

Merged
merged 2 commits into from
Jun 21, 2024
Merged

core: revert increase storage deviceset name limit to 50 (backport #14362) #14369

merged 2 commits into from
Jun 21, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jun 21, 2024

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Reviewed the developer guide on Submitting a Pull Request
  • Pending release notes updated with breaking and/or notable changes for the next minor release.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.
This is an automatic backport of pull request #14362 done by [Mergify](https://mergify.com).

@subhamkrai @mergify
core: revert increase storage deviceset name limit to 50
f6eff6d 
This reverts commit 1dcc99e.

Signed-off-by: subhamkrai <srai@redhat.com>
(cherry picked from commit c7d0756)
@subhamkrai @mergify
osd: revert limit storageClassDeviceSets to 63 chars
b37af76 
This reverts commit 6f5cc9b.

Signed-off-by: subhamkrai <srai@redhat.com>
(cherry picked from commit e8aeb0d)
@mergify mergify bot merged commit 8a94553 into release-1.14 Jun 21, 2024
53 checks passed
@mergify mergify bot deleted the mergify/bp/release-1.14/pr-14362 branch June 21, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@BlaineEXE BlaineEXE BlaineEXE approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@BlaineEXE @subhamkrai