Bug 1477768
Summary: | OSP11 -> OSP12 upgrade: nova-compute binaries listed by nova service-list are disabled with reason: AUTO: Failed to connect to libvirt: Failed to find user record for uid '162' | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
Component: | openstack-tripleo-heat-templates | Assignee: | Emilien Macchi <emacchi> |
Status: | CLOSED ERRATA | QA Contact: | Marius Cornea <mcornea> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 12.0 (Pike) | CC: | dbecker, mandreou, mbultel, mburns, morazi, rhel-osp-director-maint, sathlang, tvignaud |
Target Milestone: | beta | Keywords: | Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-7.0.0-0.20170805163046.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-13 21:48:30 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: | 1399762 |
Description
Marius Cornea
2017-08-02 21:28:12 UTC
After stopping and disabling the openstack-nova-compute service on the host and starting the nova-compute container the service comes back ok: [root@compute-0 heat-admin]# systemctl stop openstack-nova-compute [root@compute-0 heat-admin]# systemctl disable openstack-nova-compute Removed symlink /etc/systemd/system/multi-user.target.wants/openstack-nova-compute.service. [root@compute-0 heat-admin]# docker stop nova_compute docker start nova_compute nova_compute [root@compute-0 heat-admin]# docker start nova_compute nova_compute Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462 |