Ceph : Issueshttps://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2020-09-30T14:58:47ZCeph
Redmine Dashboard - Tasks #47701 (New): mgr/dashboard: QA: Split Dashboard test suite by Ceph componenthttps://tracker.ceph.com/issues/477012020-09-30T14:58:47ZLenz Grimmer
<p>Currently, the dashboard tests are part of the "rados" test suite and have to be run in full for each QA run. It was suggested if it might be possible to splie the Dashboard QA suite into separate YAML file for each component. This way, the entire test suite could be run for dashboard PRs, and the applicable pieces could be symlinked into the component suites for other components like RBD, CephFS, RGW, RADOS, etc.</p> Dashboard - Tasks #47338 (Fix Under Review): mgr/dashboard: Add E2E test to check external linkshttps://tracker.ceph.com/issues/473382020-09-07T13:10:07ZLenz Grimmer
<p>The Dashboard contains several locations that point to external documentation pages for reference purposes (e.g. how to configure certain services like Grafana or RGW).</p>
<p>As these links are not maintained by us directly, we should at least perform a check if following these links actually get us to the expected page or result in a 404 error.</p>
<p>Creating an E2E test might be the best approach for this.</p> Dashboard - Feature #46108 (Resolved): mgr/dashboard: add scss lintinghttps://tracker.ceph.com/issues/461082020-06-19T12:16:49ZIshan Rai
Ceph currently does not have linter for scss files. We should add one.<br />Possible linters that can be used :
<ul>
<li>stylelint</li>
<li>sass-lint (not maintained since 2017)</li>
</ul> Dashboard - Feature #44637 (Resolved): mgr/dashboard: create e2e tests for Orchestrator-involved ...https://tracker.ceph.com/issues/446372020-03-17T10:21:55ZKiefer Chang
<p>We integrated Orchestrator features since Octopus.<br />It would be nice if we can increase e2e tests for components that are connected with Orchestrator.</p>
<p>This requires infrastructure support to create orchestrator-spawn clusters.</p> Dashboard - Feature #44307 (Resolved): mgr/dashboard: ability to pass custom credentials for E2E ...https://tracker.ceph.com/issues/443072020-02-26T10:35:15ZAlfonso Martínezalmartin@redhat.comDashboard - Feature #41063 (Resolved): mgr/dashboard: Verify details and performance counters tab...https://tracker.ceph.com/issues/410632019-08-02T18:52:19ZAdam KingDashboard - Feature #41035 (Resolved): mgr/dashboard: Add E2E tests which verify that logs page c...https://tracker.ceph.com/issues/410352019-07-31T18:12:38ZAdam KingDashboard - Tasks #40748 (Rejected): mgr/dashboard: Automate merging pull requests using Mergifyhttps://tracker.ceph.com/issues/407482019-07-12T09:08:02ZLenz Grimmer
<p>This was brought up during today's stand-up: the process of merging pending github pull requests should be fully automated. This removes the bottleneck of having an individual performing this task manually.</p>
<p>There is a third-party service called <a href="https://mergify.io/#how-it-works" class="external">Mergify</a> that could be utilized for this.</p>
<p>We should evaluate the functionality and define a workflow that would make sense for the majority of Dashboard PRs to pass through this workflow without manual interaction.</p>
<p>Some things to consider: how to deal with tests that fail quite frequently, e.g. <code>make check</code> on ARM64? How about QA tests that are triggered and checked manually? What are the risks of automating the final step of merging a PR?</p>
<p><img src="https://tracker.ceph.com/attachments/download/4269/Automate_1allthethings.png" alt="" /></p> Dashboard - Feature #40296 (In Progress): mgr/dashboard: Maintain and improve code coverage on da...https://tracker.ceph.com/issues/402962019-06-12T12:46:28ZStephan Müller
<p>Find <a href="https://github.com/marketplace?utf8=%E2%9C%93&query=coverage" class="external">github plugins</a> or extend Jenkins to enforce a test coverage that cannot decrease.</p>
<p>Best would be on a per file basis for unit tests.</p>
<p>Currently no idea how to measure E2E and API tests, may be there is a way.</p> Dashboard - Bug #40008 (Resolved): mgr/dashboard: Need a method to check references to Grafana da...https://tracker.ceph.com/issues/400082019-05-23T04:46:19ZKiefer Chang
<p>Ceph Dashboard embeds Grafana dashboards by specifying <strong>uid</strong> in <cd-grafana> components.<br />If a Grafana dashboard is updated with uid changed, uid property in corresponding <cd-grafana> component should also be updated.<br />We need a method to ensure these references are correct, or at least exist.</p>
<p>In the short term, a script can be added to check a <cd-grafana> always refer to a existing Grafana dashboard. <br />In the long term, we can add some e2e tests to verify correctness of embedded dashboards.</p> Dashboard - Cleanup #39408 (New): mgr/dashboard: Add missings tests to DimlessBinary and DimlessB...https://tracker.ceph.com/issues/394082019-04-23T12:44:19ZPatrick Seidensal
<p>In addition to adding the missing tests, the mentioned two directives have nearly identical content and hence it might also be a able and reasonable to clean them up before adding the missing tests. The DimlessBinaryPerSecond directive is derived from the DimlessBinary directive. They are mentioned both because of their similarities.</p> Dashboard - Bug #37572 (Resolved): mgr/dashboard: Add backend tests for RBD configurationhttps://tracker.ceph.com/issues/375722018-12-07T13:36:26ZPatrick Seidensal
<p>The backend lacks tests for the RBD configuration in `controller/pool.py`:PoolConfiguration and `controller/rbd.py`:ImageConfiguration.</p>