- How to join
- How to contribute
- Who is available for help
- Prerequisites for test day
- Resources ( where to get RPMs, fedora images, etc)
- How to test
- Confirming existing issues
- Filing new issues
- How to report results
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find here on https://pulp.plan.io, and report your results as detailed in "How to report results" section below.
RSVP with this form to let us know you are coming and request help getting set up:
RSVP and request help
If you don't get around to RSVPing, just show up!
Join the #pulp channel on freenode
You can join via your favorite IRC client, or either of the two web clients below:
pulp channel on freenode webchat
Specify a nickname that you would like to go by, and keep it safe for work please!
Many people choose something close to their name, as in Elijah's nickname is "elijah_d".
The August 8th Pulp Test Day will focus on the Pulp 2.14 beta release and the new pulp debian plugin
Things you can do:
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion.
Specifically in the case of problem related to test day wiki, please reach out to Elijah DeLee at email@example.com or on irc (nick: elijah_d)
Ansible install on Fedora 26 is currently broken. Rumor is, it is manually installable. Unless you want to battle install issues today, it is best to go with Fedora 25
pulp-admin login -u admin -p admin
For a guide on some ways to spin up a VM on your machine. see Virtualization quickstart
For some information on how to provision a machine from a cloud provider such as digital ocean see Provisioning Test Machine from Cloud
The Pulp 2.14 beta repository is included in the pulp repo files:
2.14 beta repo file for fedora 24 & 25
2.14 beta repo file for RHEL7
You can also find the packages themselves here:
2.14 beta RPMs
You can find fedora "live" images here to install with:
If you'd like to run the integration test suite, pulp-smash or any individual tests, you can run them either locally on the pulp_server or remotely from any machine that can SSH into the pulp_server.
For docs on pulp-smash, see http://pulp-smash.readthedocs.io/en/latest/ where you can find instructions on how to install and configure pulp-smash to run against your pulp install.
If you have trouble, email us or ping us on IRC and we can help you get it set up!
You can help out by playing around with the tool in whatever ways you can think of: try out all the things you can find.
Get creative! Any problems you find please file a bug, or report to the IRC channel. See Filing new issues
Find the 2.14 User Guide here.
Find the 2.14 RPM Quick Start Guide here.
Look for other quick start guides among the plugin documentation. Note that the main docs.pulpproject.org may direct you to docs for 2.13, check the URL to make sure you are looking at the right version.
As a user, you should be able to Create, Read, Update, and Delete repositories and the data within. Is this the case? Where do you run into trouble?
There are three different ways you can use existing issues.
User stories closed in the 2.14 beta release
Bugs fixed in 2.14
Validate existence of outstanding bugs in 2.14 beta.
If the bug is replicable and seems suitable for for pulp-smash tests, file an issue on pulp-smash github issues
If you have problems with any of the tests, first search for a issue related to the same bug and add a comment on the issue at https://pulp.plan.io.
Otherwise, report the bug to https://pulp.plan.io in the appropriate project section.
For example, you can file a new bug or find an existing issue for the debian plugin under the Debain issues
Again, if you are having trouble finding where to file your issue or search for existing ones, join us on IRC to get help!
If you found a new bug, then you can file a new issue as described above. Also, refer to Issue filing template
If you verified that a fix is correct or that a bug still exists, then comment on the issue with details about your system including all information pertinent to filing a new bug: Issue filing template
More thoughts on what make a good bug report