Comment 16 for bug 1681769

May be this is something distribution-specific? I'm using Ubuntu and
their Openstack:

ii heat-api 1:8.0.0-0ubuntu1~cloud0 all
OpenStack orchestration service - ReST API
ii heat-api-cfn 1:8.0.0-0ubuntu1~cloud0 all
OpenStack orchestration service - CFN API
ii heat-common 1:8.0.0-0ubuntu1~cloud0 all
OpenStack orchestration service - common files
ii heat-engine 1:8.0.0-0ubuntu1~cloud0 all
OpenStack orchestration service - engine
ii python-heat 1:8.0.0-0ubuntu1~cloud0 all
OpenStack orchestration service - Python files
ii python-heatclient 1.8.0-0ubuntu2~cloud0 all
client library and CLI for OpenStack Heat - Python 2.7

Which one distro do you use to reproduce this issue? Again, I can
provide access to my lab in order to investigate it.

I installed Heat in full accordance to Ocata installation guide. To be
frank, these templates were working on Newton; problems appeared after
we reinstalled (from scratch) Ocata.

Another change is openvswitch instead of linux bridges and OVS's
firewall (we stopped using iptables). But AFAIU this change shouldn't
affect orchestration.

On 4/12/17 6:50 AM, Rabi Mishra wrote:
> Actually heat should not be calling update_security_group if there is
> nothing else changed other than the rules for SecurityGroup resource.
> The fact that it's calling it with None value for 'description' is
> absurd. I don't know why it's happening in your setup.
>

--
Volodymyr Litovka
   "Vision without Execution is Hallucination." -- Thomas Edison