Bug 1396938 - "Error: could not get certifications"
Summary: "Error: could not get certifications"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack Certification Program
Classification: Retired
Component: rhoscts
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Neeti Dahiya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 09:00 UTC by Lenny Verkhovsky
Modified: 2020-03-27 15:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 15:46:36 UTC

Attachments (Terms of Use)
error (29.07 KB, image/gif)
2016-11-21 09:00 UTC, Lenny Verkhovsky 		no flags Details
log (198 bytes, text/plain)
2016-11-21 09:01 UTC, Lenny Verkhovsky 		no flags Details
log (206 bytes, text/plain)
2016-11-21 09:01 UTC, Lenny Verkhovsky 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Lenny Verkhovsky 2016-11-21 09:00:30 UTC 
Created attachment 1222332 [details]
error

Description of problem:
Unable to add Certification. Getting Error "Could not get certifications response:[]"


Version-Release number of selected component (if applicable):
RHOSP9
yum list|grep certification
redhat-certification.noarch          4.1-20161031.el7        @rhel-7-server-cert-rpms
redhat-certification-backend.noarch  4.1-20161031.el7        @rhel-7-server-cert-rpms
redhat-certification-commons.noarch  1.3-1.el7               @rhel-7-server-cert-rpms


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Lenny Verkhovsky 2016-11-21 09:01:04 UTC 
Created attachment 1222333 [details]
log
Comment 2 Lenny Verkhovsky 2016-11-21 09:01:20 UTC 
Created attachment 1222334 [details]
log
Comment 4 Lenny Verkhovsky 2016-11-27 15:14:54 UTC 
Hello RedHat Team,
any tips/workarounds/ideas about the issue above?

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