Add check (use fcbtest snap) to test VM creation/deletion, network and storage

Bug #1835433 reported by Alvaro Uria
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
charm-openstack-service-checks
Won't Fix
Low
Unassigned

Bug Description

Create a check to verify that instances can get built, attached to networks, (de|at)tached from/to volumes, and get deleted.

To do so, test the fcbtest snap and potentially add it to a script to run the check.

Choose a subset of the tests listed at:
https://refstack.openstack.org/api/v1/guidelines/2017.09/tests

Since it is likely that probes will take more than nagios' check_timeout, possibly use a cronjob for the heavy lifting of the check, and use check_nrpe to monitor the output of the croned job.

Related branches

Alvaro Uria (aluria)
Changed in charm-openstack-service-checks:
importance: Undecided → Low
status: New → In Progress
Revision history for this message
Alvaro Uria (aluria) wrote :

First works of the tests are now released in the cs (rev=22), but a bug was found on HTTPS environments (see bug 1837234).

Additionally, this bug won't be closed until we add the capability to launch test instances per available nova-compute service (a new test scenario is being developed to achieve it, and will need to be merged into the official tempest repo + the fcbtest to sync with the latest tempest repo [since it is included in the snap]).

Revision history for this message
James Hebden (ec0) wrote :

If this has been released we should mark it as fix released and file any follow-up bugs as new bugs. It's not currently clear if this functionality is in the charm or not.

Alvaro Uria (aluria)
Changed in charm-openstack-service-checks:
assignee: Alvaro Uria (aluria) → nobody
status: In Progress → Triaged
Revision history for this message
Drew Freiberger (afreiberger) wrote :

Need specific test that creates security group, rules in that security group, port with security grou, then deploys instance, attaching to pre-created port to test codepath related to rabbitmq and security group/port updates that exhibited a specific error in a customer impacting event.

Revision history for this message
Adam Dyess (addyess) wrote :

We should also exercise creation/deletion of a loadbalancer

Revision history for this message
Eric Chen (eric-chen) wrote :

This charm is no longer being actively maintained. Please consider using the new Canonical Observability Stack instead.
(https://charmhub.io/topics/canonical-observability-stack)
I will close this new feature request.

Changed in charm-openstack-service-checks:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.