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

rgw: Raise errors when rgw daemon fails to be created (backport #9137) #9138

Merged
merged 1 commit into from Nov 10, 2021

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Nov 10, 2021

This is an automatic backport of pull request #9137 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

The generation of the rgw deployment spec was swallowing errors
if any issues are raised such as the tls cert not being found
as expected in some configurations. We need to fail the reconcile
so the error will be logged and the admin can identify the issue.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 9ecd0cb)
@travisn travisn merged commit 5edcd86 into release-1.6 Nov 10, 2021
@mergify mergify bot deleted the mergify/bp/release-1.6/pr-9137 branch November 10, 2021 17:36
@ppintogbm
Copy link

There are guidelines to custom build? Need this ASAP

@travisn
Copy link
Member

travisn commented Nov 12, 2021

There are guidelines to custom build? Need this ASAP

@ppintogbm We will plan on the v1.6.11 release next week with this change. Before then you can use the image rook/ceph:v1.6.10-9.g5edcd86, which willl effectively be the same as the v1.6.11 release. Each push to the release branch triggers the image to be built such as this. All we basically will do between now and this is tag it if there are no additional fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants