Back to bug 2059669
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Matthias Muench | 2022-03-02 09:26:46 UTC | CC | mmuench | |
| Pratik Surve | 2022-03-03 12:20:18 UTC | CC | prsurve | |
| Shyamsundar | 2022-03-08 15:38:33 UTC | Status | NEW | ASSIGNED |
| CC | jpacker | |||
| Flags | needinfo?(jpacker) | |||
| Joshua Packer | 2022-03-22 13:05:25 UTC | Flags | needinfo?(jpacker) | needinfo?(srangana) |
| CC | srangana | |||
| Mudit Agarwal | 2022-03-22 13:26:42 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Mudit Agarwal | 2022-03-22 13:27:17 UTC | Blocks | 2056571 | |
| Shyamsundar | 2022-03-28 15:12:15 UTC | Flags | needinfo?(srangana) | |
| Mudit Agarwal | 2022-03-31 15:05:07 UTC | Flags | needinfo?(srangana) | |
| Shyamsundar | 2022-04-05 16:29:58 UTC | Doc Text | Cause: Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster Consequence: If an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster Workaround (if any): openshift-dr maintains a namespace manifestWork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application resources are deleted. e.g oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-<managedCluster name>-ns-mw Result: The namespace can be deleted at the managed cluster and will not reappear | |
| Flags | needinfo?(srangana) | |||
| Shilpi Sharma | 2022-04-06 08:48:58 UTC | Doc Text | Cause: Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster Consequence: If an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster Workaround (if any): openshift-dr maintains a namespace manifestWork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application resources are deleted. e.g oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-<managedCluster name>-ns-mw Result: The namespace can be deleted at the managed cluster and will not reappear | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestWork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application resources are deleted. For example, oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-<managedCluster name>-ns-mw |
| CC | shilpsha | |||
| Shilpi Sharma | 2022-04-06 08:52:42 UTC | Doc Text | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestWork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application resources are deleted. For example, oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-<managedCluster name>-ns-mw | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestwork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application resources are deleted. For example, oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-<managedCluster name>-ns-mw |
| Shilpi Sharma | 2022-04-06 11:06:41 UTC | Doc Text | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestwork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application resources are deleted. For example, oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-<managedCluster name>-ns-mw | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestwork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application deletion. For example, as cluster administrator execute the following command on the AC hub cluster, “oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-<managedCluster name>-ns-mw”. |
| Sidhant Agrawal | 2022-04-07 12:06:22 UTC | Doc Text | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestwork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application deletion. For example, as cluster administrator execute the following command on the AC hub cluster, “oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-<managedCluster name>-ns-mw”. | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestwork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application deletion. For example, as cluster administrator execute the following command on the ACM hub cluster, “oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-ns-mw”. |
| Shilpi Sharma | 2022-04-10 17:27:37 UTC | Doc Text | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestwork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application deletion. For example, as cluster administrator execute the following command on the ACM hub cluster, “oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-ns-mw”. | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestwork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application deletion. For example, as cluster administrator execute the following command on the ACM hub cluster, “oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-ns-mw”. |
| Red Hat Bugzilla | 2022-07-08 19:05:57 UTC | CC | shilpsha | |
| Shyamsundar | 2022-07-19 13:26:28 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2022-07-19 13:26:28 UTC | |||
| Olive Lakra | 2022-08-23 08:28:47 UTC | CC | olakra | |
| Doc Text | .Creating application namespace for managed clusters Application namespace needs to exist on managed clusters for DR related pre-deployment actions and hence is pre-created when an application is deployed at the ACM hub cluster. However, if an application is deleted at the ACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace manifestwork resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application deletion. For example, as cluster administrator execute the following command on the ACM hub cluster, “oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-ns-mw”. | .Creating an application namespace for the managed clusters Application namespace needs to exist on Red Hat Advanced Cluster Management (RHACM) managed clusters for disaster recovery related pre-deployment actions and hence is pre-created when an application is deployed at the RHACM hub cluster. However, if an application is deleted at the RHACM hub cluster and its corresponding namespace is deleted on the managed clusters, they reappear on the managed cluster. Workaround: `openshift-dr` maintains a namespace `manifestwork` resource in the managed cluster namespace at the ACM hub, these resources need to be deleted post the application deletion. For example, as cluster administrator execute the following command on the RHACM hub cluster, `oc delete manifestwork -n <managedCluster namespace> <drPlacementControl name>-<namespace>-ns-mw`. |
||
| Elad | 2023-08-09 17:00:43 UTC | CC | odf-bz-bot |
Back to bug 2059669