Re: Reworking ostree's upstream CI to use the STI
On Wed, Mar 7, 2018, at 3:37 PM, Colin Walters wrote:
https://github.com/ostreedev/ostree/pull/1462
Some things I like specifically:
- The qcow2 inventory is useful (though I want it to be more
configurable)
- Ansible is mostly better than shell script
OK so...I have spent a good chunk of time trying hard to get
rebooting to work in Ansible;
https://stackoverflow.com/questions/29955605/how-to-reboot-centos-7-with-...
etc.
My most recent fixups for some of this are in:
https://github.com/ostreedev/ostree/pull/1548
and it seems OK locally but we're hitting races in CI still.
Has anyone else battled the ansible+rebooting issue?
Without this it's hard for me to invest much in converting
our tests to use Ansible more deeply.
I'm not yet to the point of adding a `- reboot` task
into Ansible...I'm uncertain of the value of doing that
versus just tossing it and going back to using shell scripts
or something more like what Cockpit's tests do with
custom code.