Heat from liberty-proposed fixes the issue

Evidence:

$ heat stack-create -f minimal_portneutron.yaml minimal_portneutron
+--------------------------------------+---------------------+--------------------+---------------------+--------------+
| id                                   | stack_name          | stack_status     
  | creation_time       | updated_time |
+--------------------------------------+---------------------+--------------------+---------------------+--------------+
| 40315bc4-6c8b-41b4-a53e-ec8e3ec18ae4 | minimal_portneutron | 
CREATE_IN_PROGRESS | 2016-05-17T21:25:58 | None         |
+--------------------------------------+---------------------+--------------------+---------------------+--------------+
$ heat stack-list
+--------------------------------------+---------------------+-----------------+---------------------+--------------+
| id                                   | stack_name          | stack_status    
| creation_time       | updated_time |
+--------------------------------------+---------------------+-----------------+---------------------+--------------+
| 40315bc4-6c8b-41b4-a53e-ec8e3ec18ae4 | minimal_portneutron | CREATE_COMPLETE 
| 2016-05-17T21:25:58 | None         |
+--------------------------------------+---------------------+-----------------+---------------------+--------------+
$ heat stack-create -f minimal_portnested.yaml minimal_portnested
heatclient.exc.HTTPBadRequest: ERROR: Failed to validate: : resources.port: : 
At least one of the following properties must be specified: network, network_id

# upgrade from cloud-archive:liberty-proposed

$ heat -d  stack-create -f minimal_portnested.yaml minimal_portnested
+--------------------------------------+---------------------+--------------------+---------------------+--------------+
| id                                   | stack_name          | stack_status     
  | creation_time       | updated_time |
+--------------------------------------+---------------------+--------------------+---------------------+--------------+
| 40315bc4-6c8b-41b4-a53e-ec8e3ec18ae4 | minimal_portneutron | CREATE_COMPLETE  
  | 2016-05-17T21:25:58 | None         |
| 1ac7b1c8-4053-4eda-b2ce-8a34d0691254 | minimal_portnested  | 
CREATE_IN_PROGRESS | 2016-05-17T21:29:45 | None         |
+--------------------------------------+---------------------+--------------------+---------------------+--------------+
$ heat stack-list
+--------------------------------------+---------------------+-----------------+---------------------+--------------+
| id                                   | stack_name          | stack_status    
| creation_time       | updated_time |
+--------------------------------------+---------------------+-----------------+---------------------+--------------+
| 40315bc4-6c8b-41b4-a53e-ec8e3ec18ae4 | minimal_portneutron | CREATE_COMPLETE 
| 2016-05-17T21:25:58 | None         |
| 1ac7b1c8-4053-4eda-b2ce-8a34d0691254 | minimal_portnested  | CREATE_COMPLETE 
| 2016-05-17T21:29:45 | None         |
+--------------------------------------+---------------------+-----------------+---------------------+--------------+


** Tags removed: verification-liberty-needed
** Tags added: verification-liberty-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579891

Title:
  [SRU] Validating a stack fails as one nested stack can't find an id
  from another

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1579891/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to