Hi Austin, Could you check the pdb resources in openstack namespace when reapplying the opentack app? `$ Kubectl -n openstack get pdb` I suspect that neutron-server pdb is out of helm chart's control for some reason. And you could try to delete it only and re-apply the app again. Mingyuan -----Original Message----- From: Austin Gillmann <ji@sibyl.li> Sent: Sunday, February 9, 2020 2:00 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Openstack reapply failing Hi all, My earlier email was never replied to so I will try to re-word it: I recently deployed StarlingX 3.0 under a dedicated storage standard cluster (the storage servers running on dell r740xd's with HDD's and compute/controllers running on HP bl460c G8 blades with 2 SSD's) the stx-openstack application applies successfully on the first try, but will abort upon reapply for a config change or such. The errors armada puts out is details = "release osh-openstack-neutron failed: poddisruptionbudgets.policy "neutron-server" already exists" and "getting deployed release "osh-openstack-neutron": release: "osh-openstack-neutron" not found" Everything else in logs look normal to me, but let me know if you need any files attached! If anyone has any idea how to get past this please let me know! Best wishes, Austin Gillmann _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss