Bug 1228292
Summary: | Incremental Update: Unable to filter my content hosts with environment if the selected errata contains atleast one installable errata | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | sthirugn <sthirugn> |
Component: | Content Management | Assignee: | Walden Raines <walden> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | sthirugn <sthirugn> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.0 | CC: | bkearney, walden |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/10705 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-12 16:04:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sthirugn@redhat.com
2015-06-04 14:38:29 UTC
Created redmine issue http://projects.theforeman.org/issues/10705 from this bug Moving to POST since upstream bug http://projects.theforeman.org/issues/10705 has been closed ------------- Walden Raines Applied in changeset commit:katello|881198cd4da2c491d9c7362dbeefd030dc6a370f. *** Bug 1226381 has been marked as a duplicate of this bug. *** Failed. Test scenario: 1. Select two erratas - one applicable and one installable for a content host 2. Click Apply Errata 3. Now try to apply the check box to show content hosts where the errata is currently installable in the host's Lifecycle environment 4. The content host is still shown although one of the selected errata is not in content host's lifecycle environment. Merged to master with 5ff9a792e1b5314d3345e35d6a73a4461bb54022. Delivered in Snap10 Verified in GA snap 11. Now I am able to filter errata based on the environment. This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015. |