Bug 975419

Summary: "restart nova-api" is not a valid command
Product: Red Hat OpenStack Reporter: Rami Vaknin <rvaknin>
Component: doc-Installation_and_Configuration_GuideAssignee: Stephen Gordon <sgordon>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.0CC: sgordon, yeylon
Target Milestone: ---Keywords: Documentation
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Red_Hat_OpenStack-Installation_and_Configuration_Guide-3-en-US-3-29 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build: CSProcessor Builder Version 1.10 Build Name: 15807, Installation and Configuration Guide-3-1 Build Date: 18-06-2013 14:37:34 Topic ID: 15858-460943 [Latest]
Last Closed: 2013-07-24 19:14:48 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:
Bug Depends On:    
Bug Blocks: 1011085    

Description Rami Vaknin 2013-06-18 12:40:58 UTC 
Title: Configuring Database Session Storage

Describe the issue:


Suggestions for improvement:


Additional information:
Comment 2 Stephen Gordon 2013-06-24 14:26:07 UTC 
"Configuring Database Session Storage" - ID: 15858 [rev: 469723]
Comment 4 Rami Vaknin 2013-06-25 12:53:04 UTC 
hmm, shouldn't it be:
service openstack-nova-api restart?
Comment 7 Stephen Gordon 2013-06-27 12:41:57 UTC 
"Updating Compute Service Quotas on the Command Line" - ID: 18108 [rev: 472141]
Comment 8 Stephen Gordon 2013-07-02 13:02:50 UTC 
"Configuring Database Session Storage" - ID: 15858 [rev: 473470]
Comment 9 Stephen Gordon 2013-07-02 13:09:15 UTC 
"Configuring Database Session Storage" - ID: 15858 [rev: 473472]
Comment 10 Stephen Gordon 2013-07-02 13:10:40 UTC 
Will show up for QA in the next build, I found that there was more than one instance where this mistake was made in the document. The 'nova-api' service is also referred to in the intro but I believe this is ok/intentional because the services are introduced with their upstream names and then the RH packaged names are provided.