{"push_id":1310993938,"size":2,"distinct_size":2,"ref":"refs/heads/stable/newton","head":"e22aa84d6a21a0059e804ab8b683974c0746014e","before":"d93f1e4de36fb94f2c6711ee68951cb3624656a2","commits":[{"sha":"313b7301a00dfce6c0078d2eb604e5c6c59c9edd","author":{"name":"Julie Pichon","email":"58bdd3f1ec705288ef5358b12269798c0bd347e1@redhat.com"},"message":"Remove excessive output when configuring nodes\n\nThe legacy 'baremetal configure boot' command calls the 'configure'\nworkflow individually for each node, causing a success/failure message\nto be printed each time. The configured node UUID(s) are included in\nthe execution output, so printing a specific message for each node is\npossible. However, considering that with many nodes this would make it\neasy for failure messages to go unnoticed, and that the command prior\nto the Mistral migration had no output, this patch removes the message\nwhen nothing went wrong instead.\n\nChange-Id: I3f1df8046ad92328fe0ee47fa073c58ca9ad5f20\nCloses-Bug: #1619717\n(cherry picked from commit 824620cc8b82c02409f9aafc68e8fdd2d8016970)","distinct":true,"url":"https://api.github.com/repos/openstack/python-tripleoclient/commits/313b7301a00dfce6c0078d2eb604e5c6c59c9edd"},{"sha":"e22aa84d6a21a0059e804ab8b683974c0746014e","author":{"name":"Jenkins","email":"61eb39d4445155efb6068840385577c11776cd20@review.openstack.org"},"message":"Merge \"Remove excessive output when configuring nodes\" into stable/newton","distinct":true,"url":"https://api.github.com/repos/openstack/python-tripleoclient/commits/e22aa84d6a21a0059e804ab8b683974c0746014e"}]}
{"actor":{"display_login":"openstack-gerrit"}}