** Changed in: neutron Importance: Undecided => Medium ** Project changed: neutron => octavia
-- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1585250 Title: Statuses not shown for non-"loadbalancer" LBaaS objects on CLI Status in octavia: In Progress Bug description: There is no indication on the CLI when creating an LBaaSv2 object (other than a "loadbalancer") has failed... stack@openstack:~$ neutron lbaas-listener-create --name MyListener1 --loadbalancer MyLB1 --protocol HTTP --protocol-port 80 Created a new listener: +---------------------------+------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------+ | admin_state_up | True | | connection_limit | -1 | | default_pool_id | | | default_tls_container_ref | | | description | | | id | 5ca664d6-3a3a-4369-821d-e36c87ff5dc2 | | loadbalancers | {"id": "549982d9-7f52-48ac-a4fe-a905c872d71d"} | | name | MyListener1 | | protocol | HTTP | | protocol_port | 80 | | sni_container_refs | | | tenant_id | 22000d943c5341cd88d27bd39a4ee9cd | +---------------------------+------------------------------------------------+ There is no indication of any issue here, and lbaas-listener-show produces the same output. However, in reality, the listener is in an error state... mysql> select * from lbaas_listeners; +----------------------------------+--------------------------------------+-------------+-------------+----------+---------------+------------------+--------------------------------------+-----------------+----------------+---------------------+------------------+--------------------------+ | tenant_id | id | name | description | protocol | protocol_port | connection_limit | loadbalancer_id | default_pool_id | admin_state_up | provisioning_status | operating_status | default_tls_container_id | +----------------------------------+--------------------------------------+-------------+-------------+----------+---------------+------------------+--------------------------------------+-----------------+----------------+---------------------+------------------+--------------------------+ | 22000d943c5341cd88d27bd39a4ee9cd | 5ca664d6-3a3a-4369-821d-e36c87ff5dc2 | MyListener1 | | HTTP | 80 | -1 | 549982d9-7f52-48ac-a4fe-a905c872d71d | NULL | 1 | ERROR | OFFLINE | NULL | +----------------------------------+--------------------------------------+-------------+-------------+----------+---------------+------------------+--------------------------------------+-----------------+----------------+---------------------+------------------+--------------------------+ 1 row in set (0.00 sec) How is a CLI user who doesn't have access to the Neutron DB supposed to know an error has occurred (other than "it doesn't work", obviously)? To manage notifications about this bug go to: https://bugs.launchpad.net/octavia/+bug/1585250/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
