Bug 755044 - Can't add errata to changeset at top level errata screen
Summary: Can't add errata to changeset at top level errata screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Garik Khachikyan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-18 16:28 UTC by Justin Sherrill
Modified: 2019-09-25 21:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 20:55:10 UTC
Target Upstream Version:


Attachments (Terms of Use)
errata - Add (38.64 KB, image/png)
2012-03-21 12:05 UTC, Garik Khachikyan
no flags Details

Description Justin Sherrill 2011-11-18 16:28:51 UTC
Description of problem:


On the promotions page if you drill down into a product you can add errata to a changeset.  If you instead go to "HOME" on that page and click errata and then select ALL or a filter to see  a list of errata, you cannot add them. 


Steps:

1.  Create a product and next environment 'Devel"
2.  promote product
3.  sync the product (product must have errata)
4.  create a changeset for 'Devel'
5.  On the promotions page (on the left hand side) do not go into the product, but instead at the top level (home icon), click errata
6.  Click all or another filter

Results,  no 'add' link beside any errata.

Comment 1 Mike McCune 2012-01-26 19:39:22 UTC
mass move to CFSE product.

Comment 2 Eric Helms 2012-02-10 17:20:52 UTC
b4c296f83c307cf144eede7b08ec36287140ba61

This is the merge commit for work that brought in search capabilities to errata within promotions.  This work in turn has fixed the issue of not being able to errata via the top level view.  If errata is promotable and a changeset is open in the right pane an Add link should appear next to the errata and add it to the changeset for all products to which the errata belongs and is promotable.

Comment 3 Mike McCune 2012-03-07 23:44:39 UTC
mass move ON_QA after brewing

Comment 4 Corey Welton 2012-03-15 17:51:32 UTC
testing notes:


< jsherrill>  cswiii the goal here is to get into a state where you are able to promote an errata
< jsherrill> by having you promote teh product before syncing, then sync
< jsherrill> then attempt to add an errata to a changeset

Comment 5 Garik Khachikyan 2012-03-21 12:04:59 UTC
# VERIFIED

Scenario:
1. create repo and promote the product of it (without syncing still)
2. sync repo
3. prepare another changeset, and then refer to Errata->All (not from the "Product")

There is "Add" link and it adds erratas (allowing to promote).

verified on:
---
mod_wsgi-3.3-3.pulp.el6.x86_64
katello-common-0.2.15-1.git.0.16f633a.el6.noarch
pulp-selinux-server-1.0.0-6.el6.noarch
katello-repos-testing-0.2.1-1.el6.noarch
qpid-cpp-server-ssl-0.12-6.el6.x86_64
candlepin-0.5.26-1.el6.noarch
candlepin-tomcat6-0.5.26-1.el6.noarch
katello-certs-tools-1.1.3-1.el6.noarch
qpid-cpp-server-0.12-6.el6.x86_64
katello-glue-foreman-0.2.15-1.git.0.16f633a.el6.noarch
katello-0.2.15-1.git.0.16f633a.el6.noarch
qpid-cpp-client-ssl-0.12-6.el6.x86_64
katello-qpid-client-key-pair-1.0-1.noarch
m2crypto-0.21.1.pulp-7.el6.x86_64
python-oauth2-1.5.170-2.pulp.el6.noarch
pulp-common-1.0.0-6.el6.noarch
katello-cli-0.2.15-1.git.0.821013f.el6.noarch
qpid-cpp-client-0.12-6.el6.x86_64
katello-glue-pulp-0.2.15-1.git.0.16f633a.el6.noarch
katello-selinux-0.2.3-1.git.57.6c5edb8.el6.noarch
katello-all-0.2.15-1.git.0.16f633a.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
python-qpid-0.12-1.el6.noarch
katello-cli-common-0.2.15-1.git.0.821013f.el6.noarch
katello-glue-candlepin-0.2.15-1.git.0.16f633a.el6.noarch
pulp-1.0.0-6.el6.noarch
katello-repos-0.2.1-1.el6.noarch
katello-configure-0.2.15-1.git.4.94aa90a.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
---

Comment 6 Garik Khachikyan 2012-03-21 12:05:31 UTC
Created attachment 571693 [details]
errata - Add

Comment 7 Mike McCune 2013-08-16 18:09:17 UTC
getting rid of 6.0.0 version since that doesn't exist


Note You need to log in before you can comment on or make changes to this bug.