Update¶

For updating SEAL Operator/Print Client follow the steps below:

Check Preconditions and Requirements.
Execute the version-specific steps for the respective update. The sections below describe them. If a section lists no steps, continue with the next step.
Execute version-specific steps needed to be done after the update as described in the sections below.

Hint - logon data

You receive the logon data for the SEAL Systems delivery platform from your Technical Project Manager at SEAL Systems.

Hint - configuration

Among other things, updating does not overwrite the configuration in Consul, the customer certificates, and the Filebeat configuration filebeat-operator.yml.

Update to 1.10.0¶

Before the Update (1.10.0)¶

As of SEAL Operator 1.10.0, Elastic Stack 7 is no longer supported. If you use Elastic Stack 7, update Elastic Stack to a newer version. For more information, refer to Requirements.

When connected to a PLOSSYS 4 system, update the node-p4rest service to version 6.28.0 or higher. Refer to Update the node-p4rest Service.

After the Update (1.10.0)¶

As of SEAL Operator 1.10.0, every update saves a reference copy of the delivered Filebeat configuration in addition to your active configuration file. The version number is part of the file name, for example:

/opt/seal/etc/filebeat-operator.yml.1.10.0.delivery

Compare it with your active configuration file to find new default options.

Caution - manual merge

Automatic merging of customer-specific changes, for example the Elastic server connection data in output.elasticsearch, is not supported. Merge such changes manually and restart seal-operator-filebeat.

Update to 1.9.0¶

After the Update (1.9.0)¶

If you were already using SEAL Elastic Stack prior to updating to SEAL Operator 1.9.0, merge the old configuration file with the new one as follows.

As of SEAL Operator 1.9.0, the delivery includes Filebeat. The name of the new Filebeat service is seal-operator-filebeat. As of Filebeat 8.0.0, Elastic changed the names of Filebeat log files. Filebeat uses the name specified in the configuration file as base name and appends a timestamp and a rotation ID. Instead of /var/log/seal/seal-filebeat.log, the current log file is now, for example, /var/log/seal/seal-operator-filebeat.log-20260625-3.ndjson. Because of the rotation ID, the name of the most recent log file changes with each rotation. The default rotation is 7.

After the update, you have to merge the old Filebeat configuration file with the new one.

Open the new configuration file.
```
/opt/seal/etc/filebeat-operator.yml
```
Open the old configuration file.
```
/opt/seal/etc/filebeat.yml.install-bak
```
Replace the complete output section of the new configuration file with the one from the old one.
Save the new configuration file.
Restart seal-operator-filebeat.

Update to 1.6.0¶

MongoDB 4.4.4 has reached the end of its lifecycle. Update your MongoDB to version 7.0.0. As of SEAL Operator 1.5.1, configure a replica set in MongoDB. Refer to Configuring SEAL MongoDB.

seal-logrotate to clean up outdated log files is no longer included in the installation of SEAL Operator. Download and install SEAL Logrotate separately, refer to the SEAL Logrotate documentation.

When connected to a PLOSSYS 4 system, update the node-p4rest service to version 6.4.6 or higher. Refer to Update the node-p4rest Service.

Update to 1.5.1¶

As of SEAL Operator 1.5.1, SEAL Operator no longer supports MongoDB 3.6.x. Additionally, configure a replica set in MongoDB. Refer to Configuring SEAL MongoDB.

Update to 1.5.0¶

Before the Update (1.5.0)¶

Version 1.5.0 of SEAL Operator is a breaking change to previous versions. It introduces the SEAL NATS message broker to improve the message handling. Install SEAL NATS before updating to SEAL Operator 1.5.0. For more information about the SEAL NATS installation, refer to the SEAL NATS documentation.

In addition, when connected to a PLOSSYS 4 system, update the node-p4rest service to version 6.0.0 or higher. Refer to Update the node-p4rest Service.

Update to 1.4.0¶

After the Update (1.4.0)¶

As of SEAL Operator 1.4.0, the install scripts no longer start the services. Start the services manually after the update, refer to Administrate Services.

As of SEAL Operator 1.4.0, the user interface is also available in French. If French does not show up in the selection dialog, add fr to the system key AVAILABLE_LANGUAGES.

For creating Web Portal shares via script, update SEAL OP-CLI to version 1.2.0.

Update to 1.3.1¶

After the Update (1.3.1)¶

As of SEAL Operator 1.3.1, the installation no longer opens the firewall ports. To open them, use the firewall.sh script contained in the delivery. For how to call it, refer to Install SEAL Operator.

Update to 1.3.0¶

Before the Update (1.3.0)¶

SEAL Operator 1.3.0 replaces the MongoDB service with a newer, incompatible version. Therefore, export the data stored in MongoDB before the update. Import it again after the update. For how to do this, refer to the SEAL-specific MongoDB documentation.

After the Update (1.3.0)¶

SEAL Operator 1.3.0 replaces the MongoDB service with a newer, incompatible version. Therefore, re-import the MongoDB data exported before updating. For how to do this, refer to the SEAL-specific MongoDB documentation.

Update to 1.2.0¶

Before the Update (1.2.0)¶

SEAL Operator 1.2.0 increases the version of seal-consul-agent from 0.9.3 to 1.7.4. The new version has an incompatible database structure. Therefore, export the data stored in Consul before the update. Import it again after the update.

Before updating SEAL Operator, export the Consul data. For more information about exporting the data, refer to Administrate the System Configuration.
Remove all files from the /opt/seal/data/seal-consul-agent directory.

After the Update (1.2.0)¶

After the update, start seal-consul-agent, refer to Administrate Services.
Import the data exported before the update, refer to Administrate the System Configuration.

Update SEAL Operator¶

Execute the following steps on the SEAL Operator server:

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the Operator - 1.10.0.1112 - rpm folder. The downloaded file has the name Operator - 1.10.0.1112 - rpm.zip.
Extract Operator - 1.10.0.1112 - rpm.zip.
Change to the Operator - 1.10.0.1112 - rpm directory and start the installation of the packages:
```
cd "Operator - 1.10.0.1112 - rpm"
```
```
sudo sh install.sh
```
Start SEAL Operator:
```
operator service start
```
Check the status of the SEAL Operator services.
```
operator service status
```

Hint - no automatic start

After an installation or update, you need to start the operator service yourself. It does not start automatically.

Update the `node-p4rest` Service¶

The following steps are only required if your installation uses the PLOSSYS 4 connector. You can update the node-p4rest service either before or after the operator update.

Execute the following steps on the PLOSSYS 4 server:

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the node-p4rest-6.28.0-990.x86_64.rpm file from the SEAL Systems delivery platform. The downloaded file has the name node-p4rest-6.28.0-990.x86_64.rpm.

Install node-p4rest-6.28.0-990.x86_64.rpm.

RHEL:

sudo yum install node-p4rest-6.28.0-990.x86_64.rpm

SUSE:

sudo zypper install node-p4rest-6.28.0-990.x86_64.rpm

Start the node-p4rest service:
```
sudo systemctl start node-p4rest
```