Bug 1017058
Summary: | openstack nova: nova-api and nova-metadata-api services are using the same port | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Yogev Rabl <yrabl> |
Component: | openstack-nova | Assignee: | Xavier Queralt <xqueralt> |
Status: | CLOSED NOTABUG | QA Contact: | Ami Jeain <ajeain> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.0 | CC: | dallan, hateya, ndipanov, xqueralt, yeylon, yrabl |
Target Milestone: | --- | Flags: | yrabl:
internal-review?
|
Target Release: | 4.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-29 08:10:51 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: |
Description
Yogev Rabl
2013-10-09 08:25:23 UTC
netstat: tcp 0 0 0.0.0.0:8775 0.0.0.0:* LISTEN 32327/python As stated on upstream bug, the metadata-api should be already spawned by nova-api if specified in nova.conf:enabled_apis (which is the default when installing with packstack) and that's why you can't start it on a separate process if already running nova-api. The question is, did packstack start nova-api-metadata? If so it's a problem with packstack that should be fixed. Having said that, I couldn't reproduce this with the latest puddle (i.e. nova-api-metadata was not started after the deploy). Closing as it doesn't look like a bug. Feel free to reopen if you thing there is something we should solve. |