Bug 1169876
| Summary: | Going back to an old version of a content view does not work as expected | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Sergio Ocón-Cárdenas <soconcar> |
| Component: | Content Management | Assignee: | Christine Fouant <cfouant> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tazim Kolhar <tkolhar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.6 | CC: | ahuchcha, bbuckingham, bkearney, cwelton, dlobatog, mmccune, riehecky, sthirugn, tkolhar |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/10351 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-12 16:04:48 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
Sergio Ocón-Cárdenas
2014-12-02 15:29:34 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. This issue appears to be reproducible. If a user deletes a version (e.g. version2) entirely (e.g from library & development), when they go to re-promote version 1, the library is not selectable; therefore, they cannot get that version back to development. There is an additional side of this. Installing a version of a content view should be marked with a time, so you can downgrade all packages to the version of the content view. In the way it works, it will present old versions of the packages, but as newer versions will be available it won't work at all. Being able to install old versions of the packages, and deinstall dependencies not needed, would be necessary to fulfill the use case. There are also issues with the rendering of the versions of the content views in the details screen of a content view. If you have: Library [1,2,3,4] DEV [1,2,3,4] and delete version 4 from DEV you should have version 3 available as the last previously promoted version. This doesn't appear to be the case and like Brad said in #3, the UI does not let you re-promote prior versions. This will be addressed in 6.1 so we can support proper 'rollback' of an environment via the delete mechanism. Moving to POST since upstream bug http://projects.theforeman.org/issues/10351 has been closed ------------- Christine Fouant Applied in changeset bastion:commit:bastion|5b2db62a2a24e48eaa3b81b982ce066285c67e78. VERIFIED: # rpm -qa | grep foreman foreman-compute-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.13-1.el6_6sat.noarch foreman-vmware-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-postgresql-1.7.2.26-1.el6_6sat.noarch foreman-libvirt-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.7-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el6_6sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el6_6sat.noarch foreman-selinux-1.7.2.13-1.el6_6sat.noarch foreman-debug-1.7.2.26-1.el6_6sat.noarch foreman-ovirt-1.7.2.26-1.el6_6sat.noarch foreman-gce-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.15-1.el6_6sat.noarch foreman-proxy-1.7.2.5-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el6_6sat.noarch intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman_docker-1.2.0.14-1.el6_6sat.noarch intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el6_6sat.noarch steps: 1. Create a content view 2. Promote to developement 3. Create a new version, promote it to development. 4. Delete new version as not working. You can use an old version of the content view promoting it again to Library, and then through the content path This has a missing cherry-pick. we need this PR: https://github.com/Katello/katello/pull/5216 Delivered in Snap10 VERIFIED: # rpm -qa | grep foreman ruby193-rubygem-foreman-tasks-0.6.12.8-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el7sat.noarch foreman-debug-1.7.2.29-1.el7sat.noarch foreman-postgresql-1.7.2.29-1.el7sat.noarch foreman-vmware-1.7.2.29-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch foreman-1.7.2.29-1.el7sat.noarch foreman-ovirt-1.7.2.29-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch foreman-proxy-1.7.2.5-1.el7sat.noarch ibm-x3655-03.ovirt.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch foreman-compute-1.7.2.29-1.el7sat.noarch foreman-gce-1.7.2.29-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.0-8.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch foreman-libvirt-1.7.2.29-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch ibm-x3655-03.ovirt.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch ibm-x3655-03.ovirt.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.18-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.15-1.el7sat.noarch steps: 1. Create a content view 2. Promote to developement 3. Create a new version, promote it to development. 4. Delete the version is working This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015. |