Bug 1314709 – openstack-nova-cert service down after deployment

Bug 1314709 - openstack-nova-cert service down after deployment

Summary:	openstack-nova-cert service down after deployment

Status:	CLOSED DUPLICATE of bug 1314711

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	rhosp-director (Show other bugs)
Sub Component:
Version:	8.0 (Liberty)
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	---
Target Release:	8.0 (Liberty)
Assigned To:	Angus Thomas
QA Contact:	Arik Chernetsky
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-03-04 05:18 EST by tkammer
Modified:	2016-03-04 06:15 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-03-04 06:15:17 EST
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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description tkammer 2016-03-04 05:18:52 EST

Description of problem:
After deploying OSP8 using director, the openstack-nova-cert service is dead on the controller.
[root@overcloud-controller-0 ~]# systemctl status openstack-nova-cert
● openstack-nova-cert.service - OpenStack Nova Cert Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-cert.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

This causes the following tempest failures:
tempest.api.compute.certificates.test_certificates.CertificatesV2TestJSON.test_create_root_certificate
tempest.api.compute.certificates.test_certificates.CertificatesV2TestJSON.test_get_root_certificate

Once manually starting the service, the tests pass.

How reproducible:
100%

Steps to Reproduce:
1. deploy OSP8 using director
2. run the above tempest tests

Comment 2 tkammer 2016-03-04 06:15:17 EST


*** This bug has been marked as a duplicate of bug 1314711 ***

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