As Tee says, if the application is re-applied, it is expected that the "status" becomes "apply-failed". However, the "active" property should always be "True" unless the application is removed.
So... is the originator complaining that the "active" property is becoming "False" after a re-apply fails? If so, that is a bug.
The application has the following state info:
[root@controller-0 ~(keystone_admin)]# system application-show stx-openstack ------- --+---- ------- ------- ------- ------- --+ ------- --+---- ------- ------- ------- ------- --+ 16T13:55: 07.849046+ 00:00 | 16T15:50: 09.556192+ 00:00 | ------- --+---- ------- ------- ------- ------- --+
+------
| Property | Value |
+------
| active | True |
| app_version | 1.0-17 |
| created_at | 2019-07-
| manifest_file | stx-openstack.yaml |
| manifest_name | armada-manifest |
| name | stx-openstack |
| progress | completed |
| status | applied |
| updated_at | 2019-07-
+------
As Tee says, if the application is re-applied, it is expected that the "status" becomes "apply-failed". However, the "active" property should always be "True" unless the application is removed.
So... is the originator complaining that the "active" property is becoming "False" after a re-apply fails? If so, that is a bug.