fix: fixed cri-o service not being active after the installation (#6)

* fix: fixed cri-o service not being active at the end of the role

* test: updated tests to check the real status of the cri-o service

handlers/main.yml

@@ -0,0 +1,6 @@
+---
+- name: Start CRI-O service
+  service:
+    name: cri-o
+    state: started
+  become: true

molecule/openstack-debian10/verify.yml

@@ -6,12 +6,8 @@
   gather_facts: false
   tasks:
   - name: "Gather CRI-O service status"
-    systemd:
-      name: cri-o
-      state: started
-    register: crio_status
-    become: true
+    ansible.builtin.service_facts:
 
-  - name: "Make sure CRI-O is reloaded"
+  - name: "Make sure CRI-O is running"
     assert:
-      that: crio_status.state == "started"
+      that: ansible_facts.services["cri-o.service"].state == "active"

molecule/vagrant-virtualbox-debian10/molecule.yml

@@ -4,7 +4,7 @@ dependency:
 lint: |
   set -e
   yamllint -c .yamllint .
-  ansible-lint --exclude .travis.yml .
+  ansible-lint .
 driver:
   name: vagrant
   provider: 

molecule/vagrant-virtualbox-debian10/verify.yml

@@ -6,12 +6,8 @@
   gather_facts: false
   tasks:
   - name: "Gather CRI-O service status"
-    systemd:
-      name: cri-o
-      state: started
-    register: crio_status
-    become: true
+    ansible.builtin.service_facts:
 
-  - name: "Make sure CRI-O is reloaded"
+  - name: "Make sure CRI-O is running"
     assert:
-      that: crio_status.state == "started"
+      that: ansible_facts.services["cri-o.service"].state == "active"

tasks/Debian.yml

@@ -27,3 +27,5 @@
       "{{ _cri_o_packages }}"
     state: present
     update_cache: yes
+  notify:
+    - "Start CRI-O service"