[Yahoo-eng-team] [Bug 1774363] [NEW] Instance is of no use during "shelve-offloading" operation, when nova-conductor is stopped

2018-05-31 Thread Swati Bansal
Public bug reported: During shelve-offloading operation if nova-conductor is stopped, the instance stuck forever in "SHELVED" state and task state of instance stuck in "SHELVING_OFFLOADING" state. After restarting the nova-conductor service, the state of instance does not change to "SHELVE_OFF

[Yahoo-eng-team] [Bug 1772371] [NEW] The parameters "transport-url" and "database_connection" are to be treated positional.

2018-05-21 Thread Swati Bansal
Public bug reported: While creating a new cell_v2 using command "nova-manage cell_v2 create_cell", if no parameter ie. "transport-url" and "database_connection" are given then the values of "transport-url" and "database_connection" of default cell are picked from nova.conf which are already mapped

[Yahoo-eng-team] [Bug 1770341] [NEW] Wrong value is accepted in transport_url parameter of nova cell create command

2018-05-10 Thread Swati Bansal
Public bug reported: Cell create command accepts value of transport_url parameter which are not in specified format. transport_url is a URL used for messaging transport. It has a defined format i.e. "transport://user:pass@host:port[,userN:passN@hostN:portN]/virtual_host?query ". However, if we

[Yahoo-eng-team] [Bug 1770343] [NEW] transport-url and database_connection parameter must be positional in nova-manage cell_v2 create_cell command

2018-05-10 Thread Swati Bansal
Public bug reported: In "nova-manage cell_v2 create_cell" CLI command the optional parameter ie. "transport-url" and "database_connection" are treated as positional arguments and CLI throws an error "The specified transport_url and/or database_connection combination already exists for another

[Yahoo-eng-team] [Bug 1761419] Re: Network Latency delay due to multiple calls at database for getting user list

2018-04-05 Thread Swati Bansal
** Changed in: keystone Status: Invalid => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1761419 Title: Network Latency delay due to multiple calls at d

[Yahoo-eng-team] [Bug 1761419] Re: Network Latency delay due to multiple calls at database for getting user list

2018-04-05 Thread Swati Bansal
** Changed in: keystone Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1761419 Title: Network Latency delay due to multiple calls at d

[Yahoo-eng-team] [Bug 1761419] [NEW] Network Latency delay due to multiple calls at database for getting user list

2018-04-05 Thread Swati Bansal
Public bug reported: If we create a project/user with the name that already exists, the request goes to database and database returns an Integrity Error for that. If the database server is present at some other location, it may increase the execution time of the use case due to network latency. Mo

[Yahoo-eng-team] [Bug 1697673] [NEW] Wrong error messege in CreateInstance

2017-06-13 Thread Swati Bansal
Public bug reported: In createInstance usecase execution, when we stop mysqld service and try to create an instance using command "nova boot --flavor --image --nic net-id= --security-group --key-name ". The instance is not created and generates an "InternalServerError". User must be informed a

[Yahoo-eng-team] [Bug 1693727] [NEW] Nova evacuate instance is not working

2017-05-26 Thread Swati Bansal
Public bug reported: in controller+2 Compute node instance is not getting evacuated from one compute node to other compute node. On evacuation it gets stuck with state as rebuilding on the source node. Below was logged in the destination compute node (/var/log/nova/nova-compute.log): 2017-04-1