nautilus: mgr/dashboard: table detail rows overflow

[aaSharma14]

backport tracker: https://tracker.ceph.com/issues/47570

---

backport of #37183
parent tracker: https://tracker.ceph.com/issues/47434

this backport was staged using ceph-backport.sh version 15.1.1.389
find the latest version at https://github.com/ceph/ceph/blob/master/src/script/ceph-backport.sh

[aaSharma14]

jenkins test api

[epuertat]

Thanks!

[smithfarm]

Thanks for contributing this backport, @aaSharma14 ! It looks like this might be one of your first contributions.

In order to keep things running smoothly, over the years we have developed some rules that must be followed for backport PRs to be considered. These are listed here:

https://github.com/ceph/ceph/blob/master/SubmittingPatches-backports.rst#cherry-picking-rules

So, backports should be done using git cherry-pick -x from master, not by merging.

[smithfarm]

You can fix this PR by running the following commands (replace ceph with the name of your upstream ceph remote):

git fetch ceph
git reset --hard ceph/nautilus
git cherry-pick -x 7196e03449d585a6b7e1e4065120a571fe2ab894

Then force-push (git push --force ...) to update the PR.

[aaSharma14]

Thanks for contributing this backport, @aaSharma14 ! It looks like this might be one of your first contributions.

In order to keep things running smoothly, over the years we have developed some rules that must be followed for backport PRs to be considered. These are listed here:

https://github.com/ceph/ceph/blob/master/SubmittingPatches-backports.rst#cherry-picking-rules

So, backports should be done using git cherry-pick -x from master, not by merging.

Thanks @smithfarm , yes this was indeed my first backport, I have redone it according to your suggestions.

[yuriw]

wip-yuri8-testing-2020-09-23-1220-nautilus

Thanks!