1155.md

BKR-1155

1. Review beaker PR
2. Review beaker-abs PR
3. Run beaker PR through the pipeline set in BKR-1177

• should see warning messages specified in bullet point #2 below
• because there's no ssh_connection_preference provided by beaker-abs before PR is merged
  • using the default connection prefs and ip is first method, but beaker-abs doesn't generate an ip value

4. Merge beaker-abs PR and release a new gem
5. Run beaker-abs pipeline after the beaker-abs gem release

• use beaker PR, make sure we don't get the warning messages specified in bullet point #2 below
• because now beaker-abs sets vmhostname as first method in its ssh_connection_preference and we are not skipping it as we should be able to ssh using that method.

6. Merge beaker PR

---

BKR-1155

This are the PR's for allowing users and hypervisor authors to set SSH connection prefrence without exposing the host hash key used by beaker. This is the work I did after having a 2 hours long discussion with Kevin and Nate after reviewing the original PRs mentioned in the first section of the doc.

beaker PR

beaker-vmpooler PR

beaker-abs PR

BKR-1177

The idea for this ticket is to generate a trusted pipeline to downstream test beaker using beaker-abs hypervisor.

1. Make sure beaker-abs tries to connect with IP address first when Beaker v3.21.0 is used

• takes a long time as it should attempt 12 times to connect using IP address, then fallback to vmhostname
• jenkins build

2. Make sure beaker-abs tries to connect with IP address but skips it as its value is not set

• uses beaker PR
• jenkins build
• This build will have warnings like: Skipping ip method to ssh to host as its value is not set. Refer to https://github.com/puppetlabs/beaker/tree/master/docs/how_to/ssh_connection_preference.md to remove this warning

Thank you Kevin!