-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.14
-
None
-
Moderate
-
No
-
False
-
-
Fixed a problem with `microshift show-config` that prevented it from reporting the correct memory limit for etcd.
-
Bug Fix
Description of problem:
sudo /usr/bin/microshift show-config --mode effective doesn't show the correct memoryLimitMB value. It always shows zero even after modifying the value of memoryLimitMB in config.yaml.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1.edit the memoryLimitMB field to 128 in config.yaml file 2.systemctl status microshift 3.Once its successfully restarted, sudo /usr/bin/microshift show-config --mode effective apiServer: subjectAltNames: - dhcp-1-235-17.arm.eng.rdu2.redhat.com - localhost.localdomain debugging: logLevel: Normal dns: baseDomain: example.com etcd: memoryLimitMB: 0 network: clusterNetwork: - cidr: 10.42.0.0/16 serviceNetwork: - 10.43.0.0/16 serviceNodePortRange: 30000-32767 node: hostnameOverride: dhcp-1-235-17.arm.eng.rdu2.redhat.com nodeIP: 10.1.235.17
Actual results:
memoryLimitMB always shows 0
Expected results:
sudo /usr/bin/microshift show-config --mode effective should show the current value of memoryLimitMB
Additional info:
[redhat@dhcp-1-235-17 microshift]$ microshift version MicroShift Version: 4.13.0_0.nightly_2023_04_10_162321_20230411082419_373392ce Base OCP Version: 4.13.0-0.nightly-2023-04-10-162321 [redhat@dhcp-1-235-17 microshift]$ microshift-etcd version MicroShift-etcd Version: 4.13.0_0.nightly_2023_04_10_162321_20230411082419_373392ce
- is depended on by
-
OCPBUGS-11660 sudo /usr/bin/microshift show-config --mode effective doesn't show the correct memoryLimitMB value
- Closed
- links to
-
RHSA-2023:5008 OpenShift Container Platform 4.14.z security update