Bug 1581075 - Netwon update fails with "couldn't get the live value of the neutron agent"
Summary: Netwon update fails with "couldn't get the live value of the neutron agent"
Keywords:
Status: CLOSED DUPLICATE of bug 1579184
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-22 06:44 UTC by Robin Cernin
Modified: 2018-05-28 14:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-28 14:06:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1771324 0 None None None 2018-05-22 06:45:03 UTC
OpenStack gerrit 568552 0 None None None 2018-05-22 06:45:31 UTC
Red Hat Knowledge Base (Solution) 3451811 0 None None None 2018-05-22 06:44:46 UTC

Description Robin Cernin 2018-05-22 06:44:00 UTC
Description of problem:

Error: We couldn't get the live value of the neutron agent, please contact support. at /etc/puppet/modules/tripleo/manifests/profile/base/neutron.pp:77 on node compute-0.localdomain

Error: We couldn't get the live value of the neutron agent, please contact support. at /etc/puppet/modules/tripleo/manifests/profile/base/neutron.pp:77 on node compute-0.localdomain

https://bugs.launchpad.net/tripleo/+bug/1771324

Fixed in upstream May 15th 2018: https://review.openstack.org/#/c/568552/

Solution article: https://access.redhat.com/solutions/3451811

Version-Release number of selected component (if applicable):

OSP10 Newton

How reproducible:

Minor update

Actual results:

Error during deployment

Expected results:

Deployment successful.

Additional info:

Comment 1 Carlos Camacho 2018-05-28 14:06:04 UTC
Closing it as duplicated of: https://bugzilla.redhat.com/show_bug.cgi?id=1579184 which is already fixed.

*** This bug has been marked as a duplicate of bug 1579184 ***


Note You need to log in before you can comment on or make changes to this bug.