yahoo-eng-team team mailing list archive

[Narender <narender.soorineeda@xxxxxxxxx>]

Public bug reported:

When i try to ssh to my new VM it is showing me the error message "No
route to host"

ssh: connect to host 10.0.0.13 port 22: No route to host

I have already set the security rules:
nova secgroup-add-rule default tcp 22 22 0.0.0.0/0
ERROR (BadRequest): This rule already exists in group 02dc84cc-808f-49ff-bbf2-e1b34d4b3c01 (HTTP 400) (Request-ID: req-024eb93f-b0b7-42e7-afce-b4fc034e33c4)

below is the output for netns:
deadman@ubuntu:~$ sudo ip netns exec $PRIVATE_NETNS_ID ip a
[sudo] password for deadman: 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ns-1fa432f7-1c@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether fa:16:3e:a7:ff:f8 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.10/29 brd 10.0.0.15 scope global ns-1fa432f7-1c
       valid_lft forever preferred_lft forever
    inet 169.254.169.254/16 brd 169.254.255.255 scope global ns-1fa432f7-1c
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fea7:fff8/64 scope link 
       valid_lft forever preferred_lft forever
deadman@ubuntu:~$

** 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/1563603

Title:
  Unable to login to a newly instantiated VM

Status in neutron:
  New

Bug description:
  When i try to ssh to my new VM it is showing me the error message "No
  route to host"

  ssh: connect to host 10.0.0.13 port 22: No route to host

  I have already set the security rules:
  nova secgroup-add-rule default tcp 22 22 0.0.0.0/0
  ERROR (BadRequest): This rule already exists in group 02dc84cc-808f-49ff-bbf2-e1b34d4b3c01 (HTTP 400) (Request-ID: req-024eb93f-b0b7-42e7-afce-b4fc034e33c4)

  below is the output for netns:
  deadman@ubuntu:~$ sudo ip netns exec $PRIVATE_NETNS_ID ip a
  [sudo] password for deadman: 
  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host 
         valid_lft forever preferred_lft forever
  2: ns-1fa432f7-1c@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
      link/ether fa:16:3e:a7:ff:f8 brd ff:ff:ff:ff:ff:ff
      inet 10.0.0.10/29 brd 10.0.0.15 scope global ns-1fa432f7-1c
         valid_lft forever preferred_lft forever
      inet 169.254.169.254/16 brd 169.254.255.255 scope global ns-1fa432f7-1c
         valid_lft forever preferred_lft forever
      inet6 fe80::f816:3eff:fea7:fff8/64 scope link 
         valid_lft forever preferred_lft forever
  deadman@ubuntu:~$

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