Bug 1145742

Summary:

[RFE] Support case, cant specify level of support

Product:

Red Hat Satellite

Reporter:

Chris Roberts <chrobert>

Component:

RH Cloud - Insights

Assignee:

Lindani Phiri <lphiri>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Tazim Kolhar <tkolhar>

Severity:

low

Docs Contact:

Priority:

low

Version:

6.0.4

CC:

bkearney, cwelton, dcleal, kroberts, lphiri, shughes, sthirugn, tkolhar, xdmoon

Target Milestone:

Unspecified

Keywords:

FutureFeature, Triaged

Target Release:

Unused

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Enhancement

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-07-10 19:47:19 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:

Attachments:

Description	Flags
New case	none

Description Chris Roberts 2014-09-23 15:33:37 UTC

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 Program Management 2014-09-23 15:43:17 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.

Comment 6 Lindani Phiri 2014-09-25 13:28:00 UTC

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 08:14:04 UTC

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 08:15:11 UTC

Created attachment 997765 [details]
New case

Comment 11 Lindani Phiri 2015-03-04 20:52:53 UTC

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