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

ceph: use next ceph v16.2.6 pacific version (backport #8743) #8775

Merged
merged 3 commits into from Sep 21, 2021

Conversation

leseb
Copy link
Member

@leseb leseb commented Sep 21, 2021

Description of your changes:

This is a backport of #8743.

Which issue is resolved by this Pull Request:
Resolves #

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
  • Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
  • Reviewed the developer guide on Submitting a Pull Request
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.
  • Pending release notes updated with breaking and/or notable changes, if necessary.
  • Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
  • Code generation (make codegen) has been run to update object specifications, if necessary.

New version is out so let's use it.

Signed-off-by: Sébastien Han <seb@redhat.com>
(cherry picked from commit 0c33493)
The new version v16.2.6 has a different behavior when it comes to the
number of cephfs-mirror socket files. Previous version had exactly 3 and
now has like way more...
So let's just check for the presence of more sockets.

Signed-off-by: Sébastien Han <seb@redhat.com>
(cherry picked from commit f040c37)
The MDS core team suggested with deploy the MDS daemon first and then do
the filesystem creation and configuration. Reversing the sequence lets
us avoid spurious FS_DOWN warnings when creating the filesystem.

Closes: rook#8745
Signed-off-by: Sébastien Han <seb@redhat.com>
(cherry picked from commit c1a88f3)
@leseb leseb requested a review from travisn September 21, 2021 14:49
@leseb leseb added this to In progress in v1.7 via automation Sep 21, 2021
@jbw976 jbw976 moved this from In progress to Blocking Release in v1.7 Sep 21, 2021
@travisn travisn merged commit 6acb7ab into rook:release-1.7 Sep 21, 2021
v1.7 automation moved this from Blocking Release to Done Sep 21, 2021
@leseb leseb deleted the bkp-8743 branch September 22, 2021 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
v1.7
Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants