Skip to content

rgw/frontend: fix typo in function name#66107

Merged
cbodley merged 1 commit intoceph:mainfrom
yuvalif:wip-yuval-fix-typo
Nov 6, 2025
Merged

rgw/frontend: fix typo in function name#66107
cbodley merged 1 commit intoceph:mainfrom
yuvalif:wip-yuval-fix-typo

Conversation

@yuvalif
Copy link
Contributor

@yuvalif yuvalif commented Nov 3, 2025

regression from: d8a3f3e

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.

regression from: d8a3f3e

Signed-off-by: Yuval Lifshitz <ylifshit@ibm.com>
@yuvalif yuvalif requested a review from a team as a code owner November 3, 2025 08:45
@github-actions github-actions bot added the rgw label Nov 3, 2025
@yuvalif
Copy link
Contributor Author

yuvalif commented Nov 3, 2025

jenkins test api

@yuvalif
Copy link
Contributor Author

yuvalif commented Nov 3, 2025

@h3nryc0ding could you please review?

Copy link
Contributor

@henrichter henrichter 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 for addressing this and sorry for the oversight!

@jmundack
Copy link
Contributor

jmundack commented Nov 4, 2025

@cbodley / @yuvalif - What do we need to change/update in our CI to catch this?

@cbodley
Copy link
Contributor

cbodley commented Nov 4, 2025

@cbodley / @yuvalif - What do we need to change/update in our CI to catch this?

cc @adamemerson @ivancich

i couldn't figure out from https://tracker.ceph.com/issues/73623 how this typo got through qa to break the build on main. the linked git branch does show this typo, but the linked shaman builds were all green for the same sha1

i guess this is another difference between ceph-dev-build and ceph-dev-pipeline. from https://shaman.ceph.com/builds/ceph/main/ i see the failed ubuntu jammy build yesterday, but the more recent builds are all green. it looks like we finally switched over to ceph-dev-pipeline for main, where logs for ubuntu jammy are now showing gcc-12.3.0 instead gcc-11.4.0

@yuvalif
Copy link
Contributor Author

yuvalif commented Nov 4, 2025

@cbodley / @yuvalif - What do we need to change/update in our CI to catch this?

i discovered that by running containarized build on a vanilla centos9 machine.

@cbodley
Copy link
Contributor

cbodley commented Nov 4, 2025

i discovered that by running containarized build on a vanilla centos9 machine.

centos 9 builds are supposed to install and use gcc-toolset-13

@yuvalif
Copy link
Contributor Author

yuvalif commented Nov 4, 2025

i discovered that by running containarized build on a vanilla centos9 machine.

centos 9 builds are supposed to install and use gcc-toolset-13

i ran install-deps.sh in the container. is it supposed to install gcc13?

@cbodley
Copy link
Contributor

cbodley commented Nov 4, 2025

i ran install-deps.sh in the container. is it supposed to install gcc13?

yes, and it's supposed to dump this error message if your default gcc is older: https://github.com/ceph/ceph/blob/70417d2173/install-deps.sh#L257-L263

i see this warning was never added for centos 9, though, so opened #66122 to add it back

@cbodley
Copy link
Contributor

cbodley commented Nov 4, 2025

@yuvalif would you be willing to help test #66122 to verify that it prints the warning, and that the command it suggests works to select gcc-13 by default?

@cbodley
Copy link
Contributor

cbodley commented Nov 4, 2025

@yuvalif would you be willing to help test #66122 to verify that it prints the warning, and that the command it suggests works to select gcc-13 by default?

nevermind, i tested in a vm and it worked: #66122 (comment)

@cbodley
Copy link
Contributor

cbodley commented Nov 5, 2025

@yuvalif @anrao19 does this really need qa, when we know that ceph-dev-pipeline isn't going to build this #else branch?

@yuvalif
Copy link
Contributor Author

yuvalif commented Nov 6, 2025

@yuvalif @anrao19 does this really need qa, when we know that ceph-dev-pipeline isn't going to build this #else branch?

probably not. i think we can merge if it builds for ubuntu jammy

@cbodley cbodley merged commit 2f8f2cd into ceph:main Nov 6, 2025
14 checks passed
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.

5 participants