| 2023-11-29 08:07:51 |
gulsum atici |
bug |
|
|
added bug |
| 2023-11-29 08:09:51 |
gulsum atici |
description |
Hello,
We decided to remove and redeploy an application which is stuck at waiting status.
Unfortunately, the charm could not be removed. How to remove the application which are not in active status ?
We run following commands in order after waiting reasonable period of time.
- remove-application (no effect)
- remove-application --force (no effect)
- remove-application --force no-wait (removed but left the resources in K8s namespace)
- Clean the Kubernetes environment manually
How to reproduce the issue ?
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
juju remove-application sdcore-upf --force
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ kubectl get all -A | grep -i upf
core service/sdcore-upf-external LoadBalancer 10.152.183.205 10.0.0.4 8805:31218/UDP 12h
juju debug log:
unit-sdcore-upf-0: 10:56:11 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-nrf-0: 10:56:11 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-mongodb-k8s-0: 10:56:11 ERROR unit.mongodb-k8s/0.juju-log Failed to get pbm status.
unit-mongodb-k8s-0: 10:56:11 WARNING unit.mongodb-k8s/0.juju-log No relation: certificates
unit-mongodb-k8s-0: 10:56:12 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-sdcore-upf-0: 10:56:13 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:14 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:16 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:17 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:19 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:20 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:22 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:23 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:25 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:26 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:28 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:29 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf removing dead unit sdcore-upf/0
controller-0: 10:56:34 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:38 INFO juju.worker.caasapplicationprovisioner.runner stopped "sdcore-upf", err: <nil> |
Hello,
We decided to remove and redeploy an application which is stuck at waiting status.
Unfortunately, the charm could not be removed. How to remove the application which are not in active status ?
We run following commands in order after waiting reasonable period of time.
- remove-application (no effect)
- remove-application --force (no effect)
- remove-application --force no-wait (removed but left the resources in K8s namespace)
- Clean the Kubernetes environment manually
How to reproduce the issue ?
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf --force
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ kubectl get all -A | grep -i upf
core service/sdcore-upf-external LoadBalancer 10.152.183.205 10.0.0.4 8805:31218/UDP 12h
juju debug log:
unit-sdcore-upf-0: 10:56:11 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-nrf-0: 10:56:11 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-mongodb-k8s-0: 10:56:11 ERROR unit.mongodb-k8s/0.juju-log Failed to get pbm status.
unit-mongodb-k8s-0: 10:56:11 WARNING unit.mongodb-k8s/0.juju-log No relation: certificates
unit-mongodb-k8s-0: 10:56:12 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-sdcore-upf-0: 10:56:13 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:14 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:16 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:17 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:19 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:20 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:22 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:23 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:25 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:26 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:28 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:29 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf removing dead unit sdcore-upf/0
controller-0: 10:56:34 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:38 INFO juju.worker.caasapplicationprovisioner.runner stopped "sdcore-upf", err: <nil> |
|
| 2023-11-29 08:12:22 |
gulsum atici |
description |
Hello,
We decided to remove and redeploy an application which is stuck at waiting status.
Unfortunately, the charm could not be removed. How to remove the application which are not in active status ?
We run following commands in order after waiting reasonable period of time.
- remove-application (no effect)
- remove-application --force (no effect)
- remove-application --force no-wait (removed but left the resources in K8s namespace)
- Clean the Kubernetes environment manually
How to reproduce the issue ?
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf --force
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ kubectl get all -A | grep -i upf
core service/sdcore-upf-external LoadBalancer 10.152.183.205 10.0.0.4 8805:31218/UDP 12h
juju debug log:
unit-sdcore-upf-0: 10:56:11 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-nrf-0: 10:56:11 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-mongodb-k8s-0: 10:56:11 ERROR unit.mongodb-k8s/0.juju-log Failed to get pbm status.
unit-mongodb-k8s-0: 10:56:11 WARNING unit.mongodb-k8s/0.juju-log No relation: certificates
unit-mongodb-k8s-0: 10:56:12 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-sdcore-upf-0: 10:56:13 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:14 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:16 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:17 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:19 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:20 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:22 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:23 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:25 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:26 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:28 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:29 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf removing dead unit sdcore-upf/0
controller-0: 10:56:34 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:38 INFO juju.worker.caasapplicationprovisioner.runner stopped "sdcore-upf", err: <nil> |
Hello,
We decided to remove and redeploy an application which is stuck at waiting status.
Unfortunately, the charm could not be removed. How to remove the application which are not in active status ?
We run following commands in order after waiting reasonable period of time.
- remove-application (no effect)
- remove-application --force (no effect)
- remove-application --force no-wait (removed but left the resources in K8s namespace)
- Clean the Kubernetes environment manually
How to reproduce the issue ?
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf --force
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf --force --no-wait
$ kubectl get all -A | grep -i upf
core service/sdcore-upf-external LoadBalancer 10.152.183.205 10.0.0.4 8805:31218/UDP 12h
juju debug log:
unit-sdcore-upf-0: 10:56:11 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-nrf-0: 10:56:11 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-mongodb-k8s-0: 10:56:11 ERROR unit.mongodb-k8s/0.juju-log Failed to get pbm status.
unit-mongodb-k8s-0: 10:56:11 WARNING unit.mongodb-k8s/0.juju-log No relation: certificates
unit-mongodb-k8s-0: 10:56:12 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-sdcore-upf-0: 10:56:13 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:14 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:16 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:17 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:19 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:20 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:22 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:23 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:25 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:26 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:28 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:29 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf removing dead unit sdcore-upf/0
controller-0: 10:56:34 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:38 INFO juju.worker.caasapplicationprovisioner.runner stopped "sdcore-upf", err: <nil> |
|
| 2023-11-29 09:00:57 |
gulsum atici |
description |
Hello,
We decided to remove and redeploy an application which is stuck at waiting status.
Unfortunately, the charm could not be removed. How to remove the application which are not in active status ?
We run following commands in order after waiting reasonable period of time.
- remove-application (no effect)
- remove-application --force (no effect)
- remove-application --force no-wait (removed but left the resources in K8s namespace)
- Clean the Kubernetes environment manually
How to reproduce the issue ?
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf --force
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf --force --no-wait
$ kubectl get all -A | grep -i upf
core service/sdcore-upf-external LoadBalancer 10.152.183.205 10.0.0.4 8805:31218/UDP 12h
juju debug log:
unit-sdcore-upf-0: 10:56:11 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-nrf-0: 10:56:11 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-mongodb-k8s-0: 10:56:11 ERROR unit.mongodb-k8s/0.juju-log Failed to get pbm status.
unit-mongodb-k8s-0: 10:56:11 WARNING unit.mongodb-k8s/0.juju-log No relation: certificates
unit-mongodb-k8s-0: 10:56:12 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-sdcore-upf-0: 10:56:13 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:14 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:16 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:17 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:19 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:20 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:22 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:23 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:25 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:26 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:28 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:29 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf removing dead unit sdcore-upf/0
controller-0: 10:56:34 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:38 INFO juju.worker.caasapplicationprovisioner.runner stopped "sdcore-upf", err: <nil> |
Hello,
We decided to remove and redeploy an application which is stuck at waiting status.
Unfortunately, the charm could not be removed. How to remove the application which are not in active status ?
We run following commands in order after waiting reasonable period of time.
- remove-application (no effect)
- remove-application --force (no effect)
- remove-application --force no-wait (removed but left the resources in K8s namespace)
- Clean the Kubernetes environment manually
How to reproduce the issue ?
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf --force
will remove application sdcore-upf
- will remove unit sdcore-upf/0
- will detach storage config/33
- will detach storage shared-app/34
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
core microk8s-localhost microk8s/localhost 3.1.6 unsupported 10:44:09+03:00
App Version Status Scale Charm Channel Rev Address Exposed Message
sdcore-upf waiting 1/0 sdcore-upf 6 10.152.183.75 no installing agent
Unit Workload Agent Address Ports Message
sdcore-upf/0* waiting executing 10.1.146.14 (config-changed) Waiting for bessd service to run
$ juju remove-application sdcore-upf --force --no-wait
$ kubectl get all -A | grep -i upf
core service/sdcore-upf-external LoadBalancer 10.152.183.205 10.0.0.4 8805:31218/UDP 12h
juju debug log during removal process:
unit-sdcore-upf-0: 10:56:11 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-nrf-0: 10:56:11 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-mongodb-k8s-0: 10:56:11 ERROR unit.mongodb-k8s/0.juju-log Failed to get pbm status.
unit-mongodb-k8s-0: 10:56:11 WARNING unit.mongodb-k8s/0.juju-log No relation: certificates
unit-mongodb-k8s-0: 10:56:12 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-sdcore-upf-0: 10:56:13 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:14 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:14 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:16 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:17 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:17 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:19 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:20 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:20 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:22 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:23 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:23 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:25 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:26 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:26 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
unit-sdcore-upf-0: 10:56:28 INFO unit.sdcore-upf/0.juju-log Starting configuration of the `bessd` service
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log *** Error: BESS daemon not connected
unit-sdcore-upf-0: 10:56:29 ERROR unit.sdcore-upf/0.juju-log Command failed: run /opt/bess/bessctl/conf/up4
unit-sdcore-upf-0: 10:56:29 INFO unit.sdcore-upf/0.juju-log Failed running configuration for bess
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:29 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:33 INFO juju.worker.caasapplicationprovisioner.sdcore-upf removing dead unit sdcore-upf/0
controller-0: 10:56:34 INFO juju.worker.caasapplicationprovisioner.sdcore-upf scaling application "sdcore-upf" to desired scale 0
controller-0: 10:56:38 INFO juju.worker.caasapplicationprovisioner.runner stopped "sdcore-upf", err: <nil> |
|
| 2023-11-30 04:05:27 |
Harry Pidcock |
juju: status |
New |
Incomplete |
|
| 2024-01-31 04:17:10 |
Launchpad Janitor |
juju: status |
Incomplete |
Expired |
|
| 2024-06-13 11:13:57 |
gulsum atici |
juju: status |
Expired |
Incomplete |
|
| 2024-06-13 11:14:05 |
gulsum atici |
juju: status |
Incomplete |
In Progress |
|
| 2024-06-13 11:14:19 |
gulsum atici |
juju: status |
In Progress |
Confirmed |
|
