Back
system           

v22

Important notes

  1. The Oxide CLI, Go SDK, and Terraform Provider have been updated for API enhancements described under New features. Please be sure to upgrade.

System requirements

Please refer to v1.0.0 release notes.

Installation

Oxide Computer Model 0 must be installed and configured under the guidance of Oxide technicians. The requirement may change in future releases.

Upgrade compatibility

Upgrade from version 21 is supported. We recommend shutting down all running instances on the rack before software update commences. Any instances that aren’t stopped for software update are transitioned to the failed state when the control plane comes up. They can be configured to start automatically with auto-restart policy or they can be started manually by the user.

All existing setup and data (e.g., projects, users, instances) remain intact after the software update.

New features

OPTE metrics

Oxide Packet Transformation Engine (OPTE) is the software component on each compute sled that transforms packets flowing between guest instances and the physical network, providing firewalling, routing, NAT, and encapsulation. In this first release of OPTE metrics, Unified Flow Table (UFT) and route cache telemetry captured by the host OS is exposed through the timeseries API for packet flow monitoring. The new metrics are listed under opte_port in the Timeseries Schemas guide. See also opte#1032, omicron#10892, and omicron#11003.

Web console

This release includes minor fixes and UX improvements.

Full console changelog

Other enhancements and bug fixes

  • A flush for a read-only guest with one active downstairs no longer errors (crucible#1963)

  • Adjust RouteCache to mitigate contention (opte#998)

  • OPTE now produces 'fragmentation needed' ICMP(v6) hairpins (opte#999)

  • Improve local volume performance by not setting NVMe volatile write cache (propolis#1170, omicron#10932)

  • Detect exhaustive local storage allocation searches (omicron#10742)

  • Do not allocate local storage for deleted disks (omicron#10754)

  • Local disk allocation algorithm tuning (omicron#10877)

  • Allow target release to be set to the current release during sled addition (omicron#10921)

  • Exclude instance shutdown from monitoring of offline services (omicron#10946)

Firmware update

  • Western Digital SN655 30+ TB: from RC910900 to RC911002

  • Micron 7450: from E2MU200 to E2MU300

Patches

None

Known behavior and limitations

End-user features

Feature AreaKnown Issue/LimitationIssue Number

Disk/image management

Disks in importing_from_bulk_writes state cannot be deleted directly. The procedure for unsticking a canceled disk import can be used as a workaround.

omicron#2987

Disk/image management

Disk rejected by guest OS due to duplicate nvme device names. The issue is caused by a 20-character limit in applying the disk name to the device serial number. See the Troubleshooting guide for more information.

-

Disk/image management

The ability to modify image metadata is not available at this time.

omicron#2800

Instance networking

Instances can become inaccessible on a sled that loses communication with switches; a reboot is currently required to restore access.

-

Instance orchestration

Unable to start an instance that has a disk replica on a sled being updated.

crucible#1690

Instance orchestration

Instance start API frequently times out when attached to local disks.

omicron#9953

Instance orchestration

New instances cannot be created when the total number of NAT entries (private-to-external IP mappings) in the system exceeds 1024.

omicron#6939

Instance performance

The tsc clocksource is treated as unreliable by guest, resulting in its fallback to use substantially slower timestamp syscalls. A workaround for this issue can be found in the Troubleshooting guide.

omicron#8001

Instance performance

Linux guests unable to capture hardware events using perf record. A workaround for this issue can be found in the Troubleshooting guide.

propolis#894

VPC internet gateway

Changing a silo’s default IP pool causes some instances to lose their outbound internet access. This is due to a mismatch between the pool containing the instances' external IP (which are allocated from the new default pool) and the pool attached to the system-created internet gateways (which are linked to the old pool during creation time). Please see the Troubleshooting guide for some possible options for restoring instance outbound connectivity.

omicron#7297

VPC routing

Subnet update clears custom router ID when the field is left out of the request body.

omicron#6406

VPC routing

Network interface update clears transit ips when the field is left out of the request body.

-

Telemetry

VM instance memory utilization and VPC network/firewall metrics are unavailable at this time.

-

Operator features

Feature AreaKnown Issue/LimitationIssue Number

Reliability

Sled memory usage improvement required to prevent system services from restarting when under extreme memory pressure.

-

Silo management

The ability to modify silo and IDP metadata is not available at this time.

omicron#3400, omicron#3125

System management

Real-time availability status for sleds and physical storage is not yet shown in the inventory API or UI.

omicron#2035

System management

Operator-driven instance migration across sleds is currently unavailable.

-

System management

Some running instances transitioned to the "stopped" state after update.

omicron#9177

Related documentation