- 概述
- 要求
- 安装
- 安装后
- 集群管理
- 监控和警示
- 迁移和升级
- 特定于产品的配置
- 最佳实践和维护
- 故障排除
- 无法获取沙盒映像
- Pod 未显示在 ArgoCD 用户界面中
- Redis 探测器失败
- RKE2 服务器无法启动
- 在 UiPath 命名空间中找不到密码
- ArgoCD 在首次安装后进入“进行中”状态
- 意外不一致;手动运行 fsck
- MongoDB Pod 处于 CrashLoopBackOff 状态或在删除后处于“等待 PVC 配置”状态
- MongoDB Pod 从 4.4.4-ent 升级到 5.0.7-ent 失败
- 集群还原或回滚后服务运行状况不佳
- Pod 在 Init:0/X 中卡住
- Prometheus 处于 CrashLoopBackoff 状态,并出现内存不足 (OOM) 错误
- 监控仪表板中缺少 Ceph-rook 指标
- Pod 无法在代理环境中与 FQDN 通信
- 使用 Automation Suite 诊断工具
- 使用 Automation Suite 支持捆绑包
- 探索日志
手动:在线升级
准备
在第一个服务器节点上执行以下步骤,然后在集群中的所有其他节点(服务器和代理)上执行。
确保所有节点上的/opt/UiPathAutomationSuite文件夹中都有 10GiB 的可用空间。 如果空间不足,您可以增加此文件夹的容量,也可以删除除cluster_config.json之外的所有以前的安装程序文件。 您始终可以再次下载以前的安装程序。
要验证可用空间,请运行以下命令: df -h /opt/UiPathAutomationSuite 。
要准备升级,请执行以下步骤:
-
使用 SSH 登录到任何服务器计算机。 对于单节点评估配置文件,您只有一个服务器节点,请登录该节点。
-
成为根用户:
sudo su -sudo su - -
在
/opt/UiPathAutomationSuite目录下创建安装文件夹:# Please replace {version} with installer version mkdir -p /opt/UiPathAutomationSuite/{version}/installer# Please replace {version} with installer version mkdir -p /opt/UiPathAutomationSuite/{version}/installer -
Download
sf-installer.zipand copy it to/opt/UiPathAutomationSuite/{version}/installer. For download instructions, see sf-installer.zip.cp /path/to/sf-installer.zip /opt/UiPathAutomationSuite/{version}/installercp /path/to/sf-installer.zip /opt/UiPathAutomationSuite/{version}/installer -
解压缩
sf-installer.zip:cd /opt/UiPathAutomationSuite/{version}/installer unzip sf-installer.zip -d .cd /opt/UiPathAutomationSuite/{version}/installer unzip sf-installer.zip -d . -
向安装程序提供权限:
chmod 755 -R /opt/UiPathAutomationSuite/{version}/installerchmod 755 -R /opt/UiPathAutomationSuite/{version}/installer -
在第一个服务器节点上生成最新的
cluster_config.json文件,并将其复制到其余节点。备注:For details on how to configure the
cluster_config.jsonparameters, see Advanced installation experience.-
如果您有旧的
cluster_config.json,请从集群生成配置文件:cd /opt/UiPathAutomationSuite/{version}/installer ./configureUiPathAS.sh config get -i /path/to/old/cluster_config.json -o ./cluster_config.jsoncd /opt/UiPathAutomationSuite/{version}/installer ./configureUiPathAS.sh config get -i /path/to/old/cluster_config.json -o ./cluster_config.json -
如果您没有旧的
cluster_config.json文件,请生成任何默认值的覆盖,您可能在以前的版本安装时已完成此操作:cd /opt/UiPathAutomationSuite/{version}/installer ./configureUiPathAS.sh config get -o ./cluster_config.jsoncd /opt/UiPathAutomationSuite/{version}/installer ./configureUiPathAS.sh config get -o ./cluster_config.json -
If you are upgrading from a previous version of AI CenterTM standalone, and your 2022.10 version of AI Center needs to be connected to an external Orchestrator, copy the Orchestrator certificate to the virtual machine. After you copy the certificate, the following configuration details are needed in
cluster_config.json:"aicenter": { "enabled": true, "orchestrator_url": "https://orchestrator.example.com", //Specify the Orchestrator URL for AI Center "identity_server_url": "https://orchestrator.example.com/identity", //Specify the Identiy URL for AI Center "orchestrator_cert_file_path": "/opt/UiPathAutomationSuite/UiPath_Installer/orch.cer", //Specify the path to the Orchestrator certificate "identity_cert_file_path": "/opt/UiPathAutomationSuite/UiPath_Installer/orch.cer", //Specify the path to Identity certificate file "metering_api_key": "test" //Specify the metering API key }"aicenter": { "enabled": true, "orchestrator_url": "https://orchestrator.example.com", //Specify the Orchestrator URL for AI Center "identity_server_url": "https://orchestrator.example.com/identity", //Specify the Identiy URL for AI Center "orchestrator_cert_file_path": "/opt/UiPathAutomationSuite/UiPath_Installer/orch.cer", //Specify the path to the Orchestrator certificate "identity_cert_file_path": "/opt/UiPathAutomationSuite/UiPath_Installer/orch.cer", //Specify the path to Identity certificate file "metering_api_key": "test" //Specify the metering API key }备注:If AI Center requires an external Orchestrator, add
sql_connection_string_templateandsql_connection_string_template_odbcin thecluster_config.jsonfile.After upgrading to AI Center 2022.10 and moving to external storage, making a skill created in 2022.4 public will fail. To fix this, run the script from here.
-
如果您要从以前的版本升级 Automation Suite,并且现在还要启用Process Mining ,则必须更新
sql_connection_string_template_sqlalchemy_pyodbc。 下面是一个示例。"sql_connection_string_template_sqlalchemy_pyodbc": "mssql+pyodbc://testadmin@sfmfup20211043125452-8926d153-sql.database.windows.net:sgTQrg%40R%40dvoYddYBoKn045ncoC9WhWU@sfmfup20211043125452-8926d153-sql.database.windows.net:1433/DB_NAME_PLACEHOLDER?driver=ODBC+Driver+17+for+SQL+Server""sql_connection_string_template_sqlalchemy_pyodbc": "mssql+pyodbc://testadmin@sfmfup20211043125452-8926d153-sql.database.windows.net:sgTQrg%40R%40dvoYddYBoKn045ncoC9WhWU@sfmfup20211043125452-8926d153-sql.database.windows.net:1433/DB_NAME_PLACEHOLDER?driver=ODBC+Driver+17+for+SQL+Server"See also Manual: Advanced installation experience.
-
-
(可选)如果您仍使用安装程序生成的自签名证书,请运行以下命令。 在第一个服务器节点上需要执行此步骤,您将在其中执行 UiPath 产品的升级。
### Please replace /path/to/cert with path to location where you want to store certificates. ./configureUiPathAS.sh tls-cert get --outpath /path/to/cert ### Now copy the ca.crt file generated in above location to trust store location sudo cp --remove-destination /part/to/cert/ca.crt /etc/pki/ca-trust/source/anchors/ ### Update the trust store sudo update-ca-trust### Please replace /path/to/cert with path to location where you want to store certificates. ./configureUiPathAS.sh tls-cert get --outpath /path/to/cert ### Now copy the ca.crt file generated in above location to trust store location sudo cp --remove-destination /part/to/cert/ca.crt /etc/pki/ca-trust/source/anchors/ ### Update the trust store sudo update-ca-trust
执行
If any errors or issues occur during or following the upgrade, you can rollback to the previous version, provided that you previously configured a backup. For instructions, see Rollback on error.
配置备份
要配置备份,请执行以下步骤:
-
Make sure you have enabled the backup on the cluster. You must create the backup using the same version of the installer as the one you used for the current deployment. For instructions, see the backup and restore documentation corresponding to the Automation Suite version from which you plan to upgrade. For instance, if you plan to upgrade from Automation Suite 2021.10, follow the instructions in the 2021.10 guide.
-
通过 SSH 连接到其中一个服务器节点。
-
要验证集群中是否所有所需的卷都有备份,请运行:
/path/to/old-installer/configureUiPathAS.sh verify-volumes-backup/path/to/old-installer/configureUiPathAS.sh verify-volumes-backup备注:备份可能需要一些时间,因此请等待大约 15 至 20 分钟,然后再次验证卷备份。
创建备份后,请继续执行以下步骤。
将集群置于维护模式
将集群置于维护模式将关闭入口控制器和所有 UiPath 服务,并阻止进入 Automation Suite 集群的所有传入流量。
此操作将导致停机,并且您的业务自动化将在整个升级过程中暂停。
-
要将集群置于维护模式,请运行:
cd /opt/UiPathAutomationSuite/{version}/installer ./configureUiPathAS.sh enable-maintenance-modecd /opt/UiPathAutomationSuite/{version}/installer ./configureUiPathAS.sh enable-maintenance-mode -
要验证集群是否处于维护模式,请运行:
./configureUiPathAS.sh is-maintenance-enabled./configureUiPathAS.sh is-maintenance-enabled重要提示:启用维护模式后,创建 SQL Server 的备份,以便 SQL 数据库中不再记录任何事务。
更新 Kubernetes 和其他基础架构组件
您必须在集群中的所有节点上执行基础架构升级。
您不能同时在多个节点上执行此步骤;您必须等待每个节点上的升级完成,然后才能移动到另一个节点。
-
登录到要执行基础架构升级的每个节点。
-
通过运行
sudo su -成为根用户。 -
确保在服务器和代理节点上启用
rke service。如果该服务已禁用,请通过运行以下命令启用该服务:
-
对于服务器节点:
[[ $(systemctl is-enabled rke2-server.service) != "enabled" ]] && systemctl enable rke2-server.service[[ $(systemctl is-enabled rke2-server.service) != "enabled" ]] && systemctl enable rke2-server.service -
对于代理节点:
[[ $(systemctl is-enabled rke2-agent.service) != "enabled" ]] && systemctl enable rke2-agent.service[[ $(systemctl is-enabled rke2-agent.service) != "enabled" ]] && systemctl enable rke2-agent.service
-
-
要开始升级,请运行以下命令:
重要提示:确保已按照准备步骤中的说明更新生成的
cluster_config.json。# replace {version} with the version you are upgrading to cd /opt/UiPathAutomationSuite/{version}/installer ./install-uipath.sh --upgrade -k -i ./cluster_config.json -o ./output.json --accept-license-agreement# replace {version} with the version you are upgrading to cd /opt/UiPathAutomationSuite/{version}/installer ./install-uipath.sh --upgrade -k -i ./cluster_config.json -o ./output.json --accept-license-agreement重要提示:If you get the following error, follow the instructions in Downgrading Ceph from 16.2.6 to 15.2.9.
Ceph cluster is running on version: 16.2.6 with known bug(https://docs.ceph.com/en/quincy/releases/pacific/#v16-2-6-pacific). Please provide temporary backup directory (via environment variable 'TMP_CEPH_BACKUP_PATH') to downgrade ceph
更新共享组件和 UiPath 产品服务
If you previously deployed your single-node installation using any Azure template version prior to 2022.10.3, and you now want to upgrade to a newer Automation Suite version, you must set the zone_resilience flag to false in the cluster_config.json file in /opt/UiPathAutomationSuite/Installer.
此步骤将升级与集群一起运行的结构和服务组件。 您只能从任何服务器节点执行此步骤一次。
-
连接到任何服务器节点。
-
通过运行
sudo su -成为根用户。 -
运行以下命令:
# replace {version} with the version you are upgrading to cd /opt/UiPathAutomationSuite/{version}/installer ./install-uipath.sh --upgrade -f -s -i ./cluster_config.json --accept-license-agreement -o ./output.json# replace {version} with the version you are upgrading to cd /opt/UiPathAutomationSuite/{version}/installer ./install-uipath.sh --upgrade -f -s -i ./cluster_config.json --accept-license-agreement -o ./output.json重要提示:升级完成后,维护模式将自动禁用。
After manually upgrading from Automation Suite 2021.10, you must also migrate to Cilium CNI. For instructions, see Migrating from Canal to Cilium CNI.
执行升级后,您可以执行以下附加步骤:
-
要验证 Automation Suite 是否运行正常,请运行:
kubectl get applications -n argocdkubectl get applications -n argocd -
If you experience issues with image vulnerabilities or storage consumption after performing an upgrade, delete the images from the old installer. For details, see the Troubleshooting section.
启用升级后备份
升级并执行清理和迁移操作后,您必须继续备份。
在继续以下步骤之前,请确保 Automation Suite 已启动并正在运行,并且您的自动化按预期继续进行。
To enable the backup, follow the instructions in described in the Backing up and restoring the cluster documentation.
使用部署模板完成升级
After performing an Automation Suite cluster upgrade, Azure and AWS template deployments require some changes to ensure a new node joins the cluster correctly through scale-out operations. To automate the changes, we recommend using the dedicated scripts. For instructions, see the Azure deployment template docs and the AWS deployment template docs.
特别注意事项
对使用 Azure 模板部署的集群执行升级时,可能会出现类似于下图所示的错误:
这是由Azure 负载均衡器的工作方式所造成。要解决此问题,请修改cluster_config.json文件中的fixed_rke_address字段。在运行升级命令之前,您必须将此字段的值更改为第一个服务器实例的 IP 地址。由于节点运行状况不佳,上传到密钥保管库的cluster_config.json应继续具有 ILB 的 IP 地址,并且不会平衡到该节点的流量。