Uploaded image for project: 'Community Linux Engineering'
  1. Community Linux Engineering
  2. CLE-4122

Create manual package test case for Flannel

SetAsigneesSync from "Extern...update-metadata-from-f...XMLWordPrintable

    • rhel-cle-nexus

      A couple of years ago (yikes) I noticed a [blog post](https://jebpages.com/2016/02/05/testing-flannel/) that talked about how a Fedora update for [Flannel](https://github.com/coreos/flannel) didn't get any feedback in Bodhi, and the author - hi, @jasonbrooks , and thank you! - thought this might be because no-one knew how to test it.

      He very awesomely provided a great set of test instructions right in [the post](https://jebpages.com/2016/02/05/testing-flannel/), and I thought "hey, it'd be really easy to [write a test case](https://fedoraproject.org/wiki/QA:SOP_test_case_creation) using the [package test plan convention](https://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation) so that test case shows up in Bodhi updates to flannel and people know how to test it." And put an item in my todo list for it.

      Cut to two years later and I STILL haven't done it, so I'm moving it from my task tracker to this one so at least more people can not get around to doing it!

      @sumantrom , I think this would maybe make a great onboarding task for someone, especially someone interested in cloud-y, atomic-y, container-y, Kubernetes-y stuff.

      A next-level thing would be to do an automated test for this, but this is an easyfix.

              Unassigned Unassigned
              cle_bot CLE bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: