The new Runtime Fabric Installer version 2.0.1683838781-797f198 enables you to log in correctly into Ops center.
| Issue Resolution | ID |
|---|---|
The new Runtime Fabric Installer version 2.0.1683838781-797f198 enables you to log in correctly into Ops center. |
W-13191265 |
| Issue Resolution | ID |
|---|---|
Latest installer is based on gravity 5.5.77, which switches from Docker to containerd as the container manager. |
W-12353489 |
Ops center now displays medium or long term data for memory related metrics. |
W-12549948 |
Performance issues no longer occur when operating appliance clusters with high utilization or many apps after they are upgraded. |
W-11781677, W-12353489 |
| Known Issue | Workaround | ID |
|---|---|---|
When you log into the Ops Center using the |
To access Ops Center, use the |
W-13191265 |
Log format changed starting with Runtime Fabric installer version 2.0.1682628878-0253858. The log output scrambles information and affects multiline logging. |
|
W-13504485 |
| Issue Resolution | ID |
|---|---|
Runtime Fabric appliance upgrades no longer fail due to a long running |
W-11585892 |
This release upgrades Helm3 to v3.10.0. |
W-11820302 |
The Telegraf monitoring app no longer issues false alerts for node uptime. |
W-11740287 |
| Known Issue | Workaround | ID |
|---|---|---|
Starting with release 2.0.1661808686-2ff0e92, you might experience performance issues operating appliance clusters with high utilization or many apps, after they are upgraded. Usually during node maintenance. After the nodes are brought back into operation, they might show signs of increased CPU usage and fail to start deployed applications. |
W-11781677 |
| Issue Resolution | ID |
|---|---|
This release includes fixes for security vulnerabilities. |
W-11585892 |
| Known Issue | Workaround | ID |
|---|---|---|
Starting with release 2.0.1661808686-2ff0e92, you might experience performance issues operating appliance clusters with high utilization or many apps, after they are upgraded. Usually during node maintenance. After the nodes are brought back into operation, they might show signs of increased CPU usage and fail to start deployed applications. |
W-11781677 |
| Description | Issue |
|---|---|
When starting an upgrade, the installer now performs an InfluxDB size check. |
W-10606099 |
The etcd.tick Kapacitor alert no longer re-appears if you delete it. |
W-10760515 |
The systemd Kapacitor task is now works as expected. |
W-10833331 |
The |
W-10946440 |
The Ops Center Individual Node Memory Usage graph now shows the correct legend. |
W-10961514 |
The RTF readiness probe no longer fails with a |
W-10647444 |
| Description | Issue |
|---|---|
Runtime Fabric might issue false alerts about uptime. |
W-10819071 |
| Known Issue | Workaround | ID |
|---|---|---|
For RHEL/CentOS 8.4, the install scripts disable the Network Mangager Cloud Setup ( |
If you’re upgrading your node operating systems from RHEL/CentOS 8.3 to 8.4, you must disable the cat > disable_nm_cloud.sh << 'EOF'
#!/bin/bash
function perform_os_specific_operations() {
set +e
if [[ "$ID_LIKE" == *"fedora"* ]] && [[ $VERSION_ID == 8.4 ]]; then
echo "Disabling nm-cloud-setup service on RHEL 8.4"
systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
systemctl stop nm-cloud-setup.service nm-cloud-setup.timer
echo "Removing ip rule prio 30400 on RHEL 8.4"
ip rule del prio 30400
if [[ -d "/etc/systemd/system/nm-cloud-setup.service.d" ]]; then
rm -rf /etc/systemd/system/nm-cloud-setup.service.d
fi
echo "Restarting NetworkManager.service on RHEL 8.4"
systemctl restart NetworkManager.service
fi
set -e
}
source /etc/os-release
perform_os_specific_operations
EOF
sudo chmod +x ./disable_nm_cloud.sh
sudo ./disable_nm_cloud.sh
|
N/A |