openstack-service fails to restart zaqar

Bug #1697184 reported by David Hill
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Won't Fix
Medium
Unassigned

Bug Description

Using the latest trunk repository, openstack-service fails to restart zaqar as openstack-zaqar@.service is lacking the instance name:

(undercloud) [stack@undercloud-0-pike cloud]$ sudo bash -c "openstack-service restart"
Failed to restart openstack-zaqar@.service: Unit name openstack-zaqar@.service is missing the instance name.
See system logs and 'systemctl status openstack-zaqar@.service' for details.

Tags: containers
Changed in tripleo:
status: New → Triaged
tags: added: containers
Changed in tripleo:
milestone: none → pike-3
importance: Undecided → Medium
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Revision history for this message
David Peacock (davidjpeacock) wrote :

This is no longer the recommended way to restart services.

Changed in tripleo:
status: Triaged → Won't Fix
Revision history for this message
David Peacock (davidjpeacock) wrote :

For clarity, now we have containerized services, the correct way to handle restarts is to do it at the container level.

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14-beta/html-single/director_installation_and_usage/#managing-containerized-services-temp

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.