Virtual baremetal instance isn't pinged by floating ip

Bug #1558558 reported by Tatyana Kuterina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
MOS Ironic

Bug Description

Detailed bug description:
Virtual baremetal instance isn't pinged by floating ip from the server or from the controller node. Also it is impossible to login on this instance through ssh:
$ ssh ubuntu@10.109.4.132
ssh: connect to host 10.109.4.132 port 22: Connection timed out

Steps to reproduce:
1. Boot instance with baremetal flavor, etc:
nova boot \
--flavor <flavor_name> \
--image <image_name> \
--key-name <keyname> \
--nic net-id=<baremetal_network_id> \
--user-data ./user-data.sh \
<vm_name>
2. Ensure ironic node goes through correct sequence of provision states
3. Assign floating IP to the instance
4. Ping the instance by floating ip from the server or from the controller node
5. Login to the instance through ssh

Expected results:
1. Instance is created
2. Instances status is ACTIVE
3. Floating Ip is assigned to the instance
4. Ping to the instance is correct
5. It is possible to login to the instance through ssh
Actual result:
1-3. Results are the same
4. Instance isn't pinged by floating ip
5. it is impossible to login on this instance through ssh:
$ ssh ubuntu@10.109.4.132
ssh: connect to host 10.109.4.132 port 22: Connection timed out

Reproducibility:
always

Workaround:
 no

Description of the environment:
MOS 8.0
1 controller node
1 compute node
1 ironic node
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "570"
  build_id: "570"
  fuel-nailgun_sha: "558ca91a854cf29e395940c232911ffb851899c1"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "658be72c4b42d3e1436b86ac4567ab914bfb451b"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "c2a335b5b725f1b994f78d4c78723d29fa44685a"
  fuel-ostf_sha: "3bc76a63a9e7d195ff34eadc29552f4235fa6c52"
  fuel-mirror_sha: "fb45b80d7bee5899d931f926e5c9512e2b442749"
  fuelmenu_sha: "78ffc73065a9674b707c081d128cb7eea611474f"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "a43cf96cd9532f10794dce736350bf5bed350e9d"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "d605bcbabf315382d56d0ce8143458be67c53434"

Diagnostic Snapshot: https://drive.google.com/a/mirantis.com/file/d/0Bz15vbpS5ZPNcFNIWVljcUlXZnc/view?usp=sharing

Tags: area-ironic
Changed in fuel:
milestone: none → 9.0
assignee: nobody → MOS Ironic (mos-ironic)
importance: Undecided → High
tags: added: area-ironic
Dina Belova (dbelova)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

Ubuntu instance from Ubuntu Cloud Image should not be accessed via SSH with login/password, it should be accessed with key-pair.
But nevertheless it must be pinged successfully.

Revision history for this message
Georgy Dyuldin (g-dyuldin) wrote :

I have created new security group with rules for PING and SSH and added this group to instance. Then assign Floating IP and check steps 4-5. Both are OK, as expected.

Revision history for this message
Serge Kovaleff (serge-kovaleff) wrote :

Thanks a lot! When and where can we test this?

Changed in fuel:
milestone: 9.0 → 10.0
Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

Rechecked it on current ISO. Did not reproduced.
Steps:
http://paste.openstack.org/show/496912/
There was no explicit change of security group or security rules.
Used virtual node via fuel_ssh driver.

Env:
Controller 1
Compute 1
Cinder 1
Ironic 1
Neutron VLAN network.

# shotgun2 short-report
cat /etc/fuel_build_id:
 313
cat /etc/fuel_build_number:
 313
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6344.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-mirror-9.0.0-1.mos135.noarch
 fuel-openstack-metadata-9.0.0-1.mos8681.noarch
 fuel-notify-9.0.0-1.mos8338.noarch
 fuel-ostf-9.0.0-1.mos934.noarch
 python-fuelclient-9.0.0-1.mos313.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-9.0.0-1.mos6344.noarch
 fuel-utils-9.0.0-1.mos8338.noarch
 fuel-nailgun-9.0.0-1.mos8681.noarch
 rubygem-astute-9.0.0-1.mos742.noarch
 fuel-misc-9.0.0-1.mos8338.noarch
 fuel-library9.0-9.0.0-1.mos8338.noarch
 shotgun-9.0.0-1.mos88.noarch
 fuel-agent-9.0.0-1.mos276.noarch
 fuel-ui-9.0.0-1.mos2678.noarch
 fuel-setup-9.0.0-1.mos6344.noarch
 nailgun-mcagents-9.0.0-1.mos742.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8681.noarch
 python-packetary-9.0.0-1.mos135.noarch
 fuel-bootstrap-cli-9.0.0-1.mos276.noarch
 fuel-migrate-9.0.0-1.mos8338.noarch

Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

Got same result using virtual node with fuel_libvirt driver.

Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

Rechecked on iso 353. Remove this bug from 9.0 since we have no reproduction on it.

[root@nailgun ~]# shotgun2 short-report
cat /etc/fuel_build_id:
 353
cat /etc/fuel_build_number:
 353
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6345.noarch
 fuel-misc-9.0.0-1.mos8340.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-mirror-9.0.0-1.mos135.noarch
 fuel-openstack-metadata-9.0.0-1.mos8679.noarch
 fuel-notify-9.0.0-1.mos8340.noarch
 fuel-ostf-9.0.0-1.mos934.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8679.noarch
 python-fuelclient-9.0.0-1.mos314.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-9.0.0-1.mos6345.noarch
 fuel-utils-9.0.0-1.mos8340.noarch
 fuel-nailgun-9.0.0-1.mos8679.noarch
 rubygem-astute-9.0.0-1.mos742.noarch
 fuel-library9.0-9.0.0-1.mos8340.noarch
 shotgun-9.0.0-1.mos88.noarch
 fuel-agent-9.0.0-1.mos276.noarch
 fuel-ui-9.0.0-1.mos2681.noarch
 fuel-setup-9.0.0-1.mos6345.noarch
 nailgun-mcagents-9.0.0-1.mos742.noarch
 python-packetary-9.0.0-1.mos135.noarch
 fuel-bootstrap-cli-9.0.0-1.mos276.noarch
 fuel-migrate-9.0.0-1.mos8340.noarch

no longer affects: fuel/mitaka
Revision history for this message
Serge Kovaleff (serge-kovaleff) wrote :

Did not reproduce on 9.0. Nothing for 10.

Changed in fuel:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.