[FuelUpgrade] Can't reset/delete previously deployed cluster after upgrade

[Andrey Sledzinskiy]

{
    "build_id": "2014-06-17_03-01-15",
    "mirantis": "yes",
    "build_number": "59",
    "ostf_sha": "a8b7660082a6f152794c610d6abe30d360fd577d",
    "nailgun_sha": "d55caa28311ff3fb9dbbfece5f58cd9eb71da47d",
    "production": "docker",
    "api": "1.0",
    "fuelmain_sha": "7859b40aaaf57b701dca7c19ce83cec3a9d2f1a3",
    "astute_sha": "a7eac46348dc77fc2723c6fcc3dbc66cc1a83152",
    "release": "5.0",
    "fuellib_sha": "294bfd2a534f54169346ac28ad901af377f1c15f"
}
uprrade script - fuel-5.1-upgrade-6-2014-06-17_22-23-28.tar

Steps:
1. Install fuel master
2. Deploy cluster - Ubuntu, simple, all other default values
3. Run upgrade script from /var directory
4. After successful upgrade try to reset environment

Expected - environment was successfully reseted and user can re-deploy cluster
Actual - reset is going infinitily on ui, progress of reset task is 0 and it doesn't change

The same behaviour if delete environment

Logs are attached

[Evgeniy L (rustyrobot)]

Cannot reproduce, I looked at the logs and in node's mcollective logs I see the next messages

2014-06-25T12:22:38.406066+01:00 debug: I, [2014-06-25T11:22:33.781968 #1123] INFO -- : rabbitmq.rb:10:in `on_connecting' TCP Connection attempt 298 to stomp://mcollective@10.108.0.2:61613
2014-06-25T12:22:38.406066+01:00 debug: I, [2014-06-25T11:22:33.782973 #1123] INFO -- : rabbitmq.rb:25:in `on_connectfail' TCP Connection to stomp://mcollective@10.108.0.2:61613 failed on attempt 298

Andrey, if you see it again, give me please this environment.

Vladimir Sharshov, do you have any idea why it happened? Do we still have some issues with rabbitmq reconnection?

[Andrey Danin (gcon-monolake)]

It seems rabbit is not started, or missed IP connectivity. I need an live environment to address the problem.

[Vladimir Sharshov (vsharshov)]

+1 for real env. Log dump contain to little information and most interest folder docker-logs is empty.

[Andrey Sledzinskiy (asledzinskiy)]

bug isn't reproduced on fuel-5.0-upgrade-125-2014-07-15_09-57-01.tar

[Andrey Kirilochkin (andreika-mail)]

The same on 6.1 build 385

iptables-save from working 6.0
http://paste.openstack.org/show/216502/

from 6.1
http://paste.openstack.org/show/216503/

It seems that iptables configuration - wrong.