confusing logs in NSX puppet manifests

Bug #1380991 reported by Andrey Danin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Igor Zinovik

Bug Description

ISO 5.1

The following string appears in Puppet logs:
Mon Oct 06 15:23:12 +0000 2014 Puppet (debug): NSX controller endpoint is '@resource[:nsx_endpoint].split(',')[0]'
An endpoint should be substituted by real value.

Also, this [0] log string should start with the 'RRPM' word not 'RDPKG'.

[0] https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/plugin_neutronnsx/lib/puppet/provider/package/rrpm.rb#L50

Tags: nsx partner
Igor Zinovik (izinovik)
Changed in fuel:
assignee: Fuel Partner Integration Team (fuel-partner) → Igor Zinovik (izinovik)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/128237

Changed in fuel:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/128237
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=23284d3b99ddfeac5eebe7fcfbc7b3a352b23d71
Submitter: Jenkins
Branch: master

commit 23284d3b99ddfeac5eebe7fcfbc7b3a352b23d71
Author: Igor Zinovik <email address hidden>
Date: Tue Oct 14 14:49:28 2014 +0400

    fix variable substitution when reporting NSX controller endpoint

    - correctly substitute variable which contain NSX controller endpoint
      value
    - report correct provider name in debug message of `rrpm' package
      provider, right now it misleads reader

    Change-Id: I325ba8ef271cc54ed9a48d6fb0b3b1afcbd98c10
    Closes-bug: #1380991

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
okosse (okosse) wrote :

I checked it on fuel-6.0-56-2014-12-18_01-32-01.iso

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.