What do you mean by "launch the container from controller node" - are
you using the nova-docker virt driver and nova to create these docker
VMs via Nova?  Or something else?  The nova-docker driver isn't in the
nova project anymore, so if you're using that and have bugs, report them
against the nova-docker project in launchpad.

** Changed in: nova
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1499752

Title:
  reading a ospfd.vty file take time to read in docker container
  launched from openstack

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  1.  Openstack version 
  ii  nova-api                            1:2015.1.0-0ubuntu1.1~cloud0          
all          OpenStack Compute - API frontend
  ii  nova-cert                           1:2015.1.0-0ubuntu1.1~cloud0          
all          OpenStack Compute - certificate management
  ii  nova-common                         1:2015.1.0-0ubuntu1.1~cloud0          
all          OpenStack Compute - common files
  ii  nova-conductor                      1:2015.1.0-0ubuntu1.1~cloud0          
all          OpenStack Compute - conductor service
  ii  nova-consoleauth                    1:2015.1.0-0ubuntu1.1~cloud0          
all          OpenStack Compute - Console Authenticator
  ii  nova-novncproxy                     1:2015.1.0-0ubuntu1.1~cloud0          
all          OpenStack Compute - NoVNC proxy
  ii  nova-scheduler                      1:2015.1.0-0ubuntu1.1~cloud0          
all          OpenStack Compute - virtual machine scheduler
  ii  python-nova                         1:2015.1.0-0ubuntu1.1~cloud0          
all          OpenStack Compute Python libraries
  ii  python-novaclient                   1:2.22.0-0ubuntu1~cloud0              
all          client library for OpenStack Compute API

  
  3.  Reproduce steps

  * I made a docker container image which has control application like quagga 
(has zebra and ospf deamons).
  * then glanced it and launch the container from controller node.
  * when container is up , i launch zebra and ospf from container using 
following command from container terminal:
      for zebra:
     sudo /usr/local/quagga/sbin/zebra  -u root -g root -i 
/usr/local/quagga/etc/zebra.pid
      for ospf:
     /usr/local/quagga/sbin/ospfd -u root -g root -i 
/usr/loc/usr/local/quagga/etc/ospfd.pid
  * then if immediately i want to attach vtysh terminal to ospf deamon , it 
could not connect immediately it will take 3 mins. time to  attach.
  *then on debugging i found that a linux read() from file halts ospf deamon.

  
  Expected result:
  * vtysh should connect immediately to ospf 
  Actual result:
  * it takes around 3 mins. to connect.

  Remark:
  when i launch container from my VM and NOT via openstack i get the desired 
result, but not with container launched with openstack.( that's the reason i am 
reporting bug here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1499752/+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

Reply via email to