register-nodes default output is not sufficient to tell what the tool is doing

Bug #1382309 reported by James Polley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-cloud-config
Confirmed
Medium
Unassigned

Bug Description

Output from a recent run:

stack@bastion:/home/shared$ register-nodes -n nodes.json
2014-10-17 01:37:07 - requests.packages.urllib3.connectionpool - INFO - Starting new HTTP connection (1): 15.126.48.4
2014-10-17 01:37:07 - requests.packages.urllib3.connectionpool - INFO - Starting new HTTP connection (1): 15.126.48.4
2014-10-17 01:37:07 - requests.packages.urllib3.connectionpool - INFO - Starting new HTTP connection (1): 15.126.48.4
2014-10-17 01:37:07 - os_cloud_config.nodes - WARNING - Creating keystone client inline is deprecated, please pass the client as parameter.
2014-10-17 01:37:07 - requests.packages.urllib3.connectionpool - INFO - Starting new HTTP connection (1): 15.126.48.4
2014-10-17 01:37:07 - requests.packages.urllib3.connectionpool - INFO - Starting new HTTP connection (1): 15.126.48.4

... so something happened. Perhaps one or more nodes were processed, I can't tell.

At a minimum I'd expect output showing number of nodes processed and maybe even something to indicate which nodes were (un)successfully processed.

Changed in os-cloud-config:
importance: Undecided → Medium
status: New → Confirmed
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.