| 2023-08-11 02:01:29 |
Luan Nunes Utimura |
bug |
|
|
added bug |
| 2023-08-11 02:01:34 |
Luan Nunes Utimura |
starlingx: assignee |
|
Luan Nunes Utimura (lutimura) |
|
| 2023-08-11 02:01:48 |
Luan Nunes Utimura |
tags |
|
stx.9.0 stx.distro.openstack |
|
| 2023-08-11 11:08:25 |
Luan Nunes Utimura |
description |
Brief Description
-----------------
Recently, it has been observed that, on systems with multiple controller nodes, `clients` pods on stand-by controllers are failing to initialize due to the absence of their respective working directories.
Severity
--------
Major.
Steps to Reproduce
------------------
On a system with multiple controller nodes:
1) Upload/apply stx-openstack;
2) Verify that `clients` pods on stand-by controllers aren't initializing.
Expected Behavior
------------------
All `clients` pods should be running.
Actual Behavior
----------------
Only the `clients` pod running on the active controller is running.
Reproducibility
---------------
Reproducible.
System Configuration
--------------------
Two+ controllers system.
Branch/Pull Time/Commit
-----------------------
StarlingX (master)
StarlingX OpenStack (master)
Last Pass
---------
N/A.
Timestamp/Logs
--------------
```
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack get pods | grep clients
clients-clients-controller-0-937646f6-pnq6c 1/1 Running 0 9m34s
clients-clients-controller-1-cab72f56-tn252 0/1 Init:0/2 0 9m34s
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack describe pod/clients-clients-controller-1-cab72f56-tn252
Warning FailedMount 2m (x12 over 10m) kubelet MountVolume.SetUp failed for volume "clients-working-directory" : hostPath type check failed: /var/opt/openstack is not a directory
Warning FailedMount 83s (x3 over 8m11s) kubelet Unable to attach or mount volumes: unmounted volumes=[clients-working-directory], unattached volumes=[kube-api-access-kcr8l pod-tmp clients-bin clients-working-directory]: timed out waiting for the condition
```
Test Activity
-------------
Developer Testing.
Workaround
----------
Manually SSH to the stand-by controller(s) and create the expected working directory(ies). |
Brief Description
-----------------
Recently, it has been observed that, on systems with multiple controller nodes, `clients` pods are failing to initialize on stand-by controllers due to the absence of their respective working directories.
Severity
--------
Major.
Steps to Reproduce
------------------
On a system with multiple controller nodes:
1) Upload/apply stx-openstack;
2) Verify that `clients` pods on stand-by controllers aren't initializing.
Expected Behavior
------------------
All `clients` pods should be running.
Actual Behavior
----------------
Only the `clients` pod running on the active controller is running.
Reproducibility
---------------
Reproducible.
System Configuration
--------------------
Two+ controllers system.
Branch/Pull Time/Commit
-----------------------
StarlingX (master)
StarlingX OpenStack (master)
Last Pass
---------
N/A.
Timestamp/Logs
--------------
```
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack get pods | grep clients
clients-clients-controller-0-937646f6-pnq6c 1/1 Running 0 9m34s
clients-clients-controller-1-cab72f56-tn252 0/1 Init:0/2 0 9m34s
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack describe pod/clients-clients-controller-1-cab72f56-tn252
Warning FailedMount 2m (x12 over 10m) kubelet MountVolume.SetUp failed for volume "clients-working-directory" : hostPath type check failed: /var/opt/openstack is not a directory
Warning FailedMount 83s (x3 over 8m11s) kubelet Unable to attach or mount volumes: unmounted volumes=[clients-working-directory], unattached volumes=[kube-api-access-kcr8l pod-tmp clients-bin clients-working-directory]: timed out waiting for the condition
```
Test Activity
-------------
Developer Testing.
Workaround
----------
Manually SSH to the stand-by controller(s) and create the expected working directory(ies). |
|
| 2023-08-11 11:08:48 |
Luan Nunes Utimura |
description |
Brief Description
-----------------
Recently, it has been observed that, on systems with multiple controller nodes, `clients` pods are failing to initialize on stand-by controllers due to the absence of their respective working directories.
Severity
--------
Major.
Steps to Reproduce
------------------
On a system with multiple controller nodes:
1) Upload/apply stx-openstack;
2) Verify that `clients` pods on stand-by controllers aren't initializing.
Expected Behavior
------------------
All `clients` pods should be running.
Actual Behavior
----------------
Only the `clients` pod running on the active controller is running.
Reproducibility
---------------
Reproducible.
System Configuration
--------------------
Two+ controllers system.
Branch/Pull Time/Commit
-----------------------
StarlingX (master)
StarlingX OpenStack (master)
Last Pass
---------
N/A.
Timestamp/Logs
--------------
```
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack get pods | grep clients
clients-clients-controller-0-937646f6-pnq6c 1/1 Running 0 9m34s
clients-clients-controller-1-cab72f56-tn252 0/1 Init:0/2 0 9m34s
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack describe pod/clients-clients-controller-1-cab72f56-tn252
Warning FailedMount 2m (x12 over 10m) kubelet MountVolume.SetUp failed for volume "clients-working-directory" : hostPath type check failed: /var/opt/openstack is not a directory
Warning FailedMount 83s (x3 over 8m11s) kubelet Unable to attach or mount volumes: unmounted volumes=[clients-working-directory], unattached volumes=[kube-api-access-kcr8l pod-tmp clients-bin clients-working-directory]: timed out waiting for the condition
```
Test Activity
-------------
Developer Testing.
Workaround
----------
Manually SSH to the stand-by controller(s) and create the expected working directory(ies). |
Brief Description
-----------------
Recently, it has been observed that, on systems with multiple controller nodes, `clients` pods are failing to initialize on stand-by controllers due to the absence of their respective working directories.
Severity
--------
Major.
Steps to Reproduce
------------------
On a system with multiple controller nodes:
1) Upload/apply stx-openstack;
2) Verify that `clients` pods aren't initializing on stand-by controllers.
Expected Behavior
------------------
All `clients` pods should be running.
Actual Behavior
----------------
Only the `clients` pod running on the active controller is running.
Reproducibility
---------------
Reproducible.
System Configuration
--------------------
Two+ controllers system.
Branch/Pull Time/Commit
-----------------------
StarlingX (master)
StarlingX OpenStack (master)
Last Pass
---------
N/A.
Timestamp/Logs
--------------
```
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack get pods | grep clients
clients-clients-controller-0-937646f6-pnq6c 1/1 Running 0 9m34s
clients-clients-controller-1-cab72f56-tn252 0/1 Init:0/2 0 9m34s
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack describe pod/clients-clients-controller-1-cab72f56-tn252
Warning FailedMount 2m (x12 over 10m) kubelet MountVolume.SetUp failed for volume "clients-working-directory" : hostPath type check failed: /var/opt/openstack is not a directory
Warning FailedMount 83s (x3 over 8m11s) kubelet Unable to attach or mount volumes: unmounted volumes=[clients-working-directory], unattached volumes=[kube-api-access-kcr8l pod-tmp clients-bin clients-working-directory]: timed out waiting for the condition
```
Test Activity
-------------
Developer Testing.
Workaround
----------
Manually SSH to the stand-by controller(s) and create the expected working directory(ies). |
|
| 2023-08-11 11:09:08 |
Luan Nunes Utimura |
description |
Brief Description
-----------------
Recently, it has been observed that, on systems with multiple controller nodes, `clients` pods are failing to initialize on stand-by controllers due to the absence of their respective working directories.
Severity
--------
Major.
Steps to Reproduce
------------------
On a system with multiple controller nodes:
1) Upload/apply stx-openstack;
2) Verify that `clients` pods aren't initializing on stand-by controllers.
Expected Behavior
------------------
All `clients` pods should be running.
Actual Behavior
----------------
Only the `clients` pod running on the active controller is running.
Reproducibility
---------------
Reproducible.
System Configuration
--------------------
Two+ controllers system.
Branch/Pull Time/Commit
-----------------------
StarlingX (master)
StarlingX OpenStack (master)
Last Pass
---------
N/A.
Timestamp/Logs
--------------
```
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack get pods | grep clients
clients-clients-controller-0-937646f6-pnq6c 1/1 Running 0 9m34s
clients-clients-controller-1-cab72f56-tn252 0/1 Init:0/2 0 9m34s
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack describe pod/clients-clients-controller-1-cab72f56-tn252
Warning FailedMount 2m (x12 over 10m) kubelet MountVolume.SetUp failed for volume "clients-working-directory" : hostPath type check failed: /var/opt/openstack is not a directory
Warning FailedMount 83s (x3 over 8m11s) kubelet Unable to attach or mount volumes: unmounted volumes=[clients-working-directory], unattached volumes=[kube-api-access-kcr8l pod-tmp clients-bin clients-working-directory]: timed out waiting for the condition
```
Test Activity
-------------
Developer Testing.
Workaround
----------
Manually SSH to the stand-by controller(s) and create the expected working directory(ies). |
Brief Description
-----------------
Recently, it has been observed that, on systems with multiple controller nodes, `clients` pods are failing to initialize on stand-by controllers due to the absence of their respective working directories.
Severity
--------
Major.
Steps to Reproduce
------------------
On a system with multiple controller nodes:
1) Upload/apply stx-openstack;
2) Verify that `clients` pods aren't initializing on stand-by controllers.
Expected Behavior
------------------
All `clients` pods should be running.
Actual Behavior
----------------
Only the `clients` pod on the active controller is running.
Reproducibility
---------------
Reproducible.
System Configuration
--------------------
Two+ controllers system.
Branch/Pull Time/Commit
-----------------------
StarlingX (master)
StarlingX OpenStack (master)
Last Pass
---------
N/A.
Timestamp/Logs
--------------
```
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack get pods | grep clients
clients-clients-controller-0-937646f6-pnq6c 1/1 Running 0 9m34s
clients-clients-controller-1-cab72f56-tn252 0/1 Init:0/2 0 9m34s
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack describe pod/clients-clients-controller-1-cab72f56-tn252
Warning FailedMount 2m (x12 over 10m) kubelet MountVolume.SetUp failed for volume "clients-working-directory" : hostPath type check failed: /var/opt/openstack is not a directory
Warning FailedMount 83s (x3 over 8m11s) kubelet Unable to attach or mount volumes: unmounted volumes=[clients-working-directory], unattached volumes=[kube-api-access-kcr8l pod-tmp clients-bin clients-working-directory]: timed out waiting for the condition
```
Test Activity
-------------
Developer Testing.
Workaround
----------
Manually SSH to the stand-by controller(s) and create the expected working directory(ies). |
|
| 2023-08-11 13:02:39 |
OpenStack Infra |
starlingx: status |
New |
In Progress |
|
| 2023-08-11 20:13:52 |
OpenStack Infra |
starlingx: status |
In Progress |
Fix Released |
|
| 2023-09-26 13:22:59 |
OpenStack Infra |
tags |
stx.9.0 stx.distro.openstack |
in-f-antelope stx.9.0 stx.distro.openstack |
|
| 2024-04-10 13:49:46 |
Ghada Khalil |
starlingx: importance |
Undecided |
Medium |
|
