yahoo-eng-team team mailing list archive

[Arkady Shtempler <1800799@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

There are newline characters in JSON format output.

For example:

(openstack) catalog show ironic -f json
{
  "endpoints": "regionOne\n  public: https://10.9.95.41:13385\nregionOne\n  internal: http://192.168.24.3:6385\nregionOne\n  admin: http://192.168.24.3:6385\n";, 
  "type": "baremetal", 
  "id": "963ac717f6d24e67946b6cae5cdfba65", 
  "name": "ironic"
}


(openstack) catalog show swift -f json
{
  "endpoints": "regionOne\n  public: https://10.9.95.41:13808/v1/AUTH_c452477e871c4913affc606044919f67\nregionOne\n  admin: http://192.168.24.3:8080\nregionOne\n  internal: http://192.168.24.3:8080/v1/AUTH_c452477e871c4913affc606044919f67\n";, 
  "type": "object-store", 
  "id": "57fb19bc1ca44d23b66cad84858d4e72", 
  "name": "swift"

Such JSON is valid, but it's not clear why do we need them actually?

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1800799

Title:
  CLI catalog command - '\n' character in JSON format output

Status in neutron:
  New

Bug description:
  There are newline characters in JSON format output.

  For example:

  (openstack) catalog show ironic -f json
  {
    "endpoints": "regionOne\n  public: https://10.9.95.41:13385\nregionOne\n  internal: http://192.168.24.3:6385\nregionOne\n  admin: http://192.168.24.3:6385\n";, 
    "type": "baremetal", 
    "id": "963ac717f6d24e67946b6cae5cdfba65", 
    "name": "ironic"
  }

  
  (openstack) catalog show swift -f json
  {
    "endpoints": "regionOne\n  public: https://10.9.95.41:13808/v1/AUTH_c452477e871c4913affc606044919f67\nregionOne\n  admin: http://192.168.24.3:8080\nregionOne\n  internal: http://192.168.24.3:8080/v1/AUTH_c452477e871c4913affc606044919f67\n";, 
    "type": "object-store", 
    "id": "57fb19bc1ca44d23b66cad84858d4e72", 
    "name": "swift"

  Such JSON is valid, but it's not clear why do we need them actually?

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1800799/+subscriptions