yahoo-eng-team team mailing list archive

[Liron Kuchlani <lkuchlan@xxxxxxxxxx>]

Public bug reported:

Description of problem:
I launched an instance based on image: rhel-guest-image-7.1-20150224.0.x86_64.qcow2 and there were not ping and ssh to it, although ssh and ping are enabled by default security. I then launched another instance and this time I could ping it and access it via ssh. Then I added rule "ALL TCP" which then enabled ping and ssh to the first instance (which previously failed).
Finally, I removed the rule and launch another instance and was able to access this new instance via ssh and ping.

Version-Release number of selected component (if applicable):
openstack-neutron-openvswitch-2014.2.2-5.el7ost.noarch
openstack-neutron-ml2-2014.2.2-5.el7ost.noarch
python-neutronclient-2.3.9-1.el7ost.noarch
openstack-neutron-2014.2.2-5.el7ost.noarch
python-neutron-2014.2.2-5.el7ost.noarch

How reproducible:


Steps to Reproduce:
1. Launch an instance and check if there are ping and ssh to it (In my case it failed)
2. Add rule "ALL TCP" and check if there are ping and ssh to the instance (Now it worked for me)
3. Remove the rule
4. Launch another instance and check both instances for access via ping and ssh (Both worked for me)

Actual results:
Ping and ssh failed with the first instance

Expected results:
Firstly, ping and ssh should worked with the first instance. Secondly, let's assume that ping and ssh was not enabled by default security, after I removed the rule "ALL TCP", instances should not have been accessible via ping and ssh, although those were in my case.

** Affects: neutron
     Importance: Undecided
         Status: New

** Attachment added: "logs"
   https://bugs.launchpad.net/bugs/1475985/+attachment/4431141/+files/logs.tar.gz

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

Title:
   Ping and ssh to instance fail, although access is enabled by default

Status in neutron:
  New

Bug description:
  Description of problem:
  I launched an instance based on image: rhel-guest-image-7.1-20150224.0.x86_64.qcow2 and there were not ping and ssh to it, although ssh and ping are enabled by default security. I then launched another instance and this time I could ping it and access it via ssh. Then I added rule "ALL TCP" which then enabled ping and ssh to the first instance (which previously failed).
  Finally, I removed the rule and launch another instance and was able to access this new instance via ssh and ping.

  Version-Release number of selected component (if applicable):
  openstack-neutron-openvswitch-2014.2.2-5.el7ost.noarch
  openstack-neutron-ml2-2014.2.2-5.el7ost.noarch
  python-neutronclient-2.3.9-1.el7ost.noarch
  openstack-neutron-2014.2.2-5.el7ost.noarch
  python-neutron-2014.2.2-5.el7ost.noarch

  How reproducible:

  
  Steps to Reproduce:
  1. Launch an instance and check if there are ping and ssh to it (In my case it failed)
  2. Add rule "ALL TCP" and check if there are ping and ssh to the instance (Now it worked for me)
  3. Remove the rule
  4. Launch another instance and check both instances for access via ping and ssh (Both worked for me)

  Actual results:
  Ping and ssh failed with the first instance

  Expected results:
  Firstly, ping and ssh should worked with the first instance. Secondly, let's assume that ping and ssh was not enabled by default security, after I removed the rule "ALL TCP", instances should not have been accessible via ping and ssh, although those were in my case.

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