Skip to content

Revert "Merge pull request #65940 from Tom-Sollers/fixing_blaum_roth_…#66114

Merged
batrick merged 1 commit intoceph:mainfrom
batrick:revert-65940
Nov 4, 2025
Merged

Revert "Merge pull request #65940 from Tom-Sollers/fixing_blaum_roth_…#66114
batrick merged 1 commit intoceph:mainfrom
batrick:revert-65940

Conversation

@batrick
Copy link
Member

@batrick batrick commented Nov 3, 2025

…for_ec_profiles"

This reverts commit a222787, reversing changes made to cf11d9d.

This was not QA'd or reviewed by SME for mon code changes.

Contribution Guidelines

  • To sign and title your commits, please refer to Submitting Patches to Ceph.

  • If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands

You must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.

…oth_for_ec_profiles"

This reverts commit a222787, reversing
changes made to cf11d9d.

This was not QA'd or reviewed by SME for mon code changes.

Signed-off-by: Patrick Donnelly <pdonnell@ibm.com>
@gregsfortytwo
Copy link
Member

The second referenced commit hash leads to a dashboard change set, so I think you have the wrong reference there

@gregsfortytwo
Copy link
Member

+1 on revert until issue is fixed, though

@batrick
Copy link
Member Author

batrick commented Nov 3, 2025

The second referenced commit hash leads to a dashboard change set, so I think you have the wrong reference there

That's what happens when you do git revert -m1 <merge commit>. The commit message is correct.

@gregsfortytwo
Copy link
Member

The second referenced commit hash leads to a dashboard change set, so I think you have the wrong reference there

That's what happens when you do git revert -m1 <merge commit>. The commit message is correct.

Then write a commit message that makes sense, because the auto-generated statement is meaningless. I was sitting here trying to figure out how a dashboard text change is relevant to monitor code and check that the merge revert did the right thing (it got fixed, but in older git releases they were super broken).

@batrick
Copy link
Member Author

batrick commented Nov 3, 2025

The second referenced commit hash leads to a dashboard change set, so I think you have the wrong reference there

That's what happens when you do git revert -m1 <merge commit>. The commit message is correct.

Then write a commit message that makes sense, because the auto-generated statement is meaningless. I was sitting here trying to figure out how a dashboard text change is relevant to monitor code and check that the merge revert did the right thing (it got fixed, but in older git releases they were super broken).

There is value in a standardized commit message for processes automated by tooling; it builds confidence that I didn't do anything manually which could introduce human error. In any case, the automated message is technically correct and clear so I do not see any reason to change it.

@batrick batrick merged commit 022e052 into ceph:main Nov 4, 2025
23 of 26 checks passed
@batrick batrick deleted the revert-65940 branch November 4, 2025 13:09
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.

4 participants