Bug #10039

puppet-dashboard/bin/external_node fails with Cloud provisionner generated certnames

Added by Alexandre Fouche 7 months ago. Updated 6 months ago.

Status:Rejected Start date:10/12/2011
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Keywords:dashboard cloud provisioner certname yaml enc Affected URL:
Branch: Affected Dashboard version:
Votes: 1

Description

Puppet-dashboard external_node tool returns an empty yaml when querying with a node name generated by the cloud provisionner (eg: 9a4c1004-a6d0-98f2-e003-f13848b3de11 ). It works fine when using a more normal name such as hostname.mycompany.com. Note: When using the tool without parameters, it does print the correct and full yaml for the generated node name.

# /usr/share/puppet-dashboard/bin/external_node 9a4c1004-a6d0-98f2-e003-f13848b3de11
--- 
name: d34d36a9-9ddb-400d-32ea-5dbfb85f32d7
parameters: {}

classes: []


# /usr/share/puppet-dashboard/bin/external_node 
--- 
- name: 9a4c1004-a6d0-98f2-e003-f13848b3de11
  parameters: 
    redis_datadir: /opt/redis
  classes: 
  - lsof
  - redis::server
  - sudo
- name: hostname.mycompany.com
  parameters: 
    var1: content_var1
  classes: 
  - lsof


# /usr/share/puppet-dashboard/bin/external_node hostname.mycompany.com
--- 
name: hostname.mycompany.com
parameters: 
  var1: content_var1
classes: 
- lsof



# rpm -qi puppet-dashboard
Name        : puppet-dashboard             Relocations: (not relocatable)
Version     : 1.2.2                             Vendor: (none)
Release     : 1.el6                         Build Date: Mon 10 Oct 2011 05:50:09 PM UTC
Install Date: Tue 11 Oct 2011 01:22:15 PM UTC      Build Host: rpm-builder.puppetlabs.lan
Group       : Applications/System           Source RPM: puppet-dashboard-1.2.2-1.el6.src.rpm
Size        : 86225692                         License: ASL 2.0
Signature   : RSA/SHA1, Mon 10 Oct 2011 05:53:48 PM UTC, Key ID 1054b7a24bd6ec30
URL         : http://www.puppetlabs.com
Summary     : Systems Management web application

Puppet_Node_Manager-1.png - Dashbord browser url node query -> got replied wrong node (134.2 kB) Alexandre Fouche, 10/12/2011 07:30 am

History

#1
Updated by Alexandre Fouche 7 months ago

Attached is a screenshot. I see that when i query the node 9a4c1004-a6d0-98f2-e003-f13848b3de11, Dashboard replied with node d34d36a9-9ddb-400d-32ea-5dbfb85f32d7 ! I can see it now also in my previous cli output.

Once i deleted the node d34d36a9-9ddb-400d-32ea-5dbfb85f32d7, then Dashboard was able to reply with my correct node 9a4c1004-a6d0-98f2-e003-f13848b3de11

#2
Updated by Daniel Sauble 6 months ago

  • Affected Dashboard version deleted (1.2.2rc2)

I wonder if this could be a cloud provisioner issue. When I enter the above data into dashboard manually, I’m unable to reproduce the issue (external_node receives valid, non-empty, yaml for 9a4c1004-a6d0-98f2-e003-f13848b3de11 and d34d36a9-9ddb-400d-32ea-5dbfb85f32d7)

#3
Updated by Alexandre Fouche 6 months ago

I do not have evidence data anymore. i can’t say if the root cause is the cloud provisionner. It was kind of an early release at this time. I suppose we can close this bug then. If there is really a problem due to Dashboard, someone else will surely also experience it

#4
Updated by Max Martin 6 months ago

  • Status changed from Unreviewed to Rejected

Since this doesn’t seem to be reproducible and the problem seems to have gone away for you/was tied to an early version of cloud provisioner, I’m going to go ahead and close the ticket. Feel free to reopen if you experience a similar problem again.

Also available in: Atom PDF