Bugs and Feature Requests¶
How to File an Issue¶
Is this security related? If so, please follow the Security Disclosures procedure.
Please set only the fields in this table. See Redmine Fields for more detailed descriptions of all the fields and how they are used.
|Tracker||For a bug, select
|Subject||Strive to be specific and concise.|
|Description||This is the most important part! Please see Description Field.|
|Category||Choose one if applicable, blank is OK.|
|Version||The version of pulpcore that you discovered the issue.|
|OS||Please select your operating system.|
|Tags||For searching. Select 0 or many, best judgement. If an issue requires a functional test. Add the tag Functional test.|
A well written description is very helpful to developers and other users with similar problems. It is ok if you aren’t able to provide all the information requested here, but clear and detailed issues are more likely to be fixed quickly. Bonus points if they are pretty.
For Issues (Bugs) please include:
- Detailed explanation of the problem. For problems involving external content sources, please indicate the source (and a link) if you can.
- Clear steps to reproduce the problem. Commands and/or REST calls are highly encouraged.
- Expected results
- Actual results
- Snippet of relevant logs, especially Exceptions.
You can also upload attachments, but please only upload relevant data. For example, if you have an entire log which contains some errors, please trim it to just the relevant portions and upload those.
For Feature Requests (Stories), the description will depend on the feature. Please be specific when describing the requested behavior and include the motivation for adding it. If you have suggestions for how the commands/REST calls would look, please include that as well. Feature requests require follow-up from the filer, so please reach out with a link to your issue.
Twice per week, the Pulp team triages all new bugs, at which point its Severity rating and other aspects of the report will be evaluated. If necessary, the bug may be commented on requesting more information or clarification from the reporter. When a bug has enough information, its Priority rating set and is marked as triaged using the Triaged boolean.
We take security issues seriously and welcome responsible disclosure of security vulnerabilities in Pulp. Please email email@example.com (a private address for the Pulp Security Team) with all reports.
Your report should include:
- Pulp version
- A vulnerability description
- Reproduction steps
- Feel free to submit a patch with your disclosure. A member of the Pulp Security Team will confirm the vulnerability, determine its impact, and develop a fix.
|Description||A detailed explanation of the problem please see Description Field|
|Priority||Assigned during Triage.|
|Assignee||Contributor who is working on this issue.|
|Milestone||A set of work that has been grouped together.|
|Parent Task||Indicates that this is a sub-task of the larger issue.|
|Severity||Assigned during Triage.|
|Version||Filer experienced the problem while running this version of pulpcore|
|Triaged||Indicates whether an issue has gone through bug triage|
|Groomed||Core developers mark issues groomed when they include all necessary information.|
|Sprint||If set, indicates that the issue is accepted and is ready to be worked on.|
|Tags||Used for filtering.|