Travis CI currently broken

oasis-roles / ansible-role-redhat_satellite6_storage

GNU General Public License v3.0

3 stars 1 forks source link

Travis CI currently broken #4

Open stdevel opened 4 years ago

stdevel commented 4 years ago

Currently, the Travis CI is broken:

ERROR: Failed to pre-validate.
...
...
{'lint': ['must be of string type'], 'driver': [{'name': ['unallowed value openstack']}]}
...
{'lint': ['must be of string type']}

Will have a look at it and send a PR.

stdevel commented 4 years ago

Hey @itewk @greg-hellings, I think I need your help.

I fixed some issues preventing Travis CI to work properly, but I have two issues:

for testing the role an additional disk is required (e.g. /dev/sdb, /dev/vdb,...) - I don't know how to assign it
the PIP module molecule-openstack required for testing is not available for Python 2.7 anymore - should we still support Python 2.7? It became EOL on 01/01/2020.

How should we deal with this?

itewk commented 4 years ago

@stdevel i have no clue how Travis CI works so no clue how to solve those issues. I do know red hat is supporting python 2.7 for a while so those packages are available and in use, but don't know how that applies here. I will have to defer to @greg-hellings .

greg-hellings commented 4 years ago

Hmm, I don't know if additional disks are available on Travis.

If you need to move a test to run with specialized hardware requirements, you might have to switch to just an openstack driver. Then the downstream Jenkins can pick up the Jenkinsfile and report results back to here. Our OpenStack provisioning role supports adding volumes to a VM, so you should be able to handle that sort of testing there.

Once that's going, then just change the Travis test to running lint, if there isn't a way to get volume support in the Docker container.

You might also be able to create a loopback device attached to a file just to fool it along? I'd have to resort to Google Fu to get the details of that right, but it's a possibility.