Red Hat Bugzilla – Bug 1322065
rhel-osp-director: After completing the upgrade from 7.3 ->8.0, unable to launch an overcloud instance.
Last modified: 2016-04-26 18:55:01 EDT
rhel-osp-director: After completing the upgrade from 7.3 ->8.0, unable to launch an overcloud instance. Environment: openstack-tripleo-heat-templates-kilo-0.8.14-1.el7ost.noarch openstack-nova-scheduler-12.0.2-4.el7ost.noarch openstack-nova-conductor-12.0.2-4.el7ost.noarch openstack-nova-compute-12.0.2-4.el7ost.noarch openstack-tripleo-heat-templates-0.8.14-1.el7ost.noarch python-novaclient-3.1.0-2.el7ost.noarch openstack-nova-common-12.0.2-4.el7ost.noarch openstack-nova-novncproxy-12.0.2-4.el7ost.noarch python-nova-12.0.2-4.el7ost.noarch openstack-nova-cert-12.0.2-4.el7ost.noarch openstack-nova-console-12.0.2-4.el7ost.noarch instack-undercloud-2.2.7-1.el7ost.noarch openstack-nova-api-12.0.2-4.el7ost.noarch Steps to reproduce: 1. Deploy overcloud 7.3 HA + 1 compute + 1 ceph. 2. Populate the overcloud with instance. 3. Upgrade the setup to 8.0 4. Attempt to launch another instance. Result: The instance ends up with status error: Checking the instance itself: {"message": "No valid host was found. There are not enough hosts available. nova-compute appears down in "nova service-list". On compute, the openstack-nova-compute.service is ActiveState=active Expected result: The instance should be launched with no issues after the upgrade.
Created attachment 1141351 [details] nova-compute log crom a compute
The issue talking to Neutron looks like https://bugs.launchpad.net/neutron/+bug/1509312
Launching an instance without attaching it to networks works.
Created attachment 1141441 [details] Patch for liberty backport Joining a patch doing backport of https://review.openstack.org/294132/ for liberty
sasha did you include/try the latest fix from emilien to restart openstack-neutron-agent on the compute node? I see in your attached nova-compute logs there is also this: 2016-03-29 16:54:45.226 19103 ERROR oslo.messaging._drivers.impl_rabbit [req-8ba77eba-915f-4d42-92dc-70b6fc4207fc - - - - -] AMQP server on 192.168.100.15:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 32 seconds. (the agent didn't restart and so didn't get the new password it now has in /etc/neutron/neutron.conf ) I was able to run the tripleo-ci pingtest locally after upgrade ok
Mario, I think you confuse issues. It's not related to any config changes.
(In reply to Ihar Hrachyshka from comment #6) > Mario, I think you confuse issues. It's not related to any config changes. thanks ihar I was wondering if it was related to the (puppet-neutron) workaround we carry for the neutron-openvswitch-agent restart on config change at https://review.openstack.org/#/c/298946/ but after the call just now it seems not
Verified: Environment: openstack-neutron-7.0.1-15.el7ost.noarch Was able to launch an instance with network connectivity post upgrade.
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://rhn.redhat.com/errata/RHEA-2016-0603.html