Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1145742 - [RFE] Support case, cant specify level of support
[RFE] Support case, cant specify level of support
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 6
Classification: Red Hat
Component: rubygem-foreman-redhat_access (Show other bugs)
6.0.4
Unspecified Unspecified
low Severity low (vote)
: Unspecified
: Unused
Assigned To: Lindani Phiri
Tazim Kolhar
: FutureFeature, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-23 11:33 EDT by Chris Roberts
Modified: 2017-02-23 15:54 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-10 15:47:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
New case (55.58 KB, image/png)
2015-03-04 03:15 EST, Tazim Kolhar
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Chris Roberts 2014-09-23 11:33:37 EDT
Description of problem:

When creating a support case from the WEBUI it does not let you pick a support level such as standard, self support, or premium. I have tested this on a test system here 6.04 and was able to reproduce the issue. 

How reproducible:


Steps to Reproduce:
1. from webui click on Red Hat Access - Support New Case
2. Try to make a new case but you cant pick the level of support
3.
Comment 3 RHEL Product and Program Management 2014-09-23 11:43:17 EDT
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.
Comment 6 Lindani Phiri 2014-09-25 09:28:00 EDT
This issue has already been addressed upstream. Fix will be added in the next release of the RHA plugin.
Comment 9 Tazim Kolhar 2015-03-04 03:14:04 EST
FAILEDQA

# rpm -qa | grep foreman
foreman-1.7.2.8-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.2-1.el6_6sat.noarch
foreman-compute-1.7.2.8-1.el6_6sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.2-1.el6_6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.1-1.el6_6sat.noarch
foreman-proxy-1.7.2.3-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch
foreman-vmware-1.7.2.8-1.el6_6sat.noarch
foreman-libvirt-1.7.2.8-1.el6_6sat.noarch
ruby193-rubygem-foreman_abrt-0.0.5-2.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch
rubygem-hammer_cli_foreman-0.1.4.6-1.el6_6sat.noarch
foreman-selinux-1.7.2.8-1.el6_6sat.noarch
foreman-debug-1.7.2.8-1.el6_6sat.noarch
foreman-gce-1.7.2.8-1.el6_6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.0.8-2.el6_6sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.5-1.el6_6sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch
foreman-postgresql-1.7.2.8-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch
foreman-ovirt-1.7.2.8-1.el6_6sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.8-1.el6_6sat.noarch

screenshot attached
Comment 10 Tazim Kolhar 2015-03-04 03:15:11 EST
Created attachment 997765 [details]
New case
Comment 11 Lindani Phiri 2015-03-04 15:52:53 EST
Hi Tazim,

The attached screen shot seems related to https://bugzilla.redhat.com/show_bug.cgi?id=1145742 , and not this one.

There is also a blocker BZ https://bugzilla.redhat.com/show_bug.cgi?id=1197764
for all Red Hat Access functionality in Satellite 6.1


Lindani

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