Description of problem: During installation of spoke cluster via assisted operator, the cluster deployment shows "The cluster cannot begin the installation because it has already started" and agent shows "The agent cannot begin the installation because it has already started", although installation proceeds and completes. Although not necessarily impacting install, causing end user confusion. Version-Release number of selected component (if applicable): hub cluster - quay.io/openshift-release-dev/ocp-release:4.8.0-fc.2-x86_64 Latest assisted operator - image: quay.io/ocpmetal/assisted-service-operator-bundle:latest imageID: quay.io/ocpmetal/assisted-service-operator-bundle@sha256:f4a1203e202ed60b8c8a2e6877b478fd83f22aac9474ea09126bc9b5e596d6d3 How reproducible: 100% Steps to Reproduce: 1. Setup 4.8 hub cluster in an ipv4 connected env (libvirt in this case) 2. Deploy assisted service operator + operand 3. Create necessary CRs for sno spoke cluster deployment via assisted operator 4. Watch cd and agent conditions during spoke installation Actual results: The agent cannot begin the installation because it has already started The cluster cannot begin the installation because it has already started Expected results: Those messages do not occur Additional info: Specific condition info: Status: Conditions: Last Transition Time: 2021-05-06T17:43:04Z Message: The Spec has been successfully applied Reason: SyncOK Status: True Type: SpecSynced Last Transition Time: 2021-05-06T17:43:04Z Message: The agent's connection to the installation service is unimpaired Reason: AgentIsConnected Status: True Type: Connected Last Transition Time: 2021-05-06T17:43:20Z Message: The agent cannot begin the installation because it has already started Reason: AgentAlreadyInstalling Status: False Type: ReadyForInstallation Last Transition Time: 2021-05-06T17:43:12Z Message: The agent's validations are passing Reason: ValidationsPassing Status: True Type: Validated Last Transition Time: 2021-05-06T17:43:04Z Message: The installation is in progress: Installing Reason: InstallationInProgress Status: False Type: Installed Status: Cli Image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:9faa7de1a709e7376ce191986df1ce949513a10570108d773b142a26d5142e87 Conditions: Last Probe Time: 2021-05-06T17:41:16Z Last Transition Time: 2021-05-06T17:41:16Z Message: Condition Initialized Reason: Initialized Status: Unknown Type: Hibernating Last Probe Time: 2021-05-06T17:41:17Z Last Transition Time: 2021-05-06T17:41:17Z Message: The Spec has been successfully applied Reason: SyncOK Status: True Type: SpecSynced Last Probe Time: 2021-05-06T17:43:14Z Last Transition Time: 2021-05-06T17:43:14Z Message: The cluster cannot begin the installation because it has already started Reason: ClusterAlreadyInstalling Status: False Type: ReadyForInstallation Last Probe Time: 2021-05-06T17:43:14Z Last Transition Time: 2021-05-06T17:43:14Z Message: The cluster's validations are passing Reason: ValidationsPassing Status: True Type: Validated Last Probe Time: 2021-05-06T17:44:34Z Last Transition Time: 2021-05-06T17:44:34Z Message: The installation is in progress: Installation in progress Reason: InstallationInProgress Status: False Type: Installed Install Strategy: Agent: Connectivity Majority Groups: {"192.168.125.0/24":[]} Install Version: 4.8.0-fc.1 Installer Image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0d4e2d3da3cda73ff683384b135926c4fcc8e5fd991d5867e9703d1c877ec2d2 Events: <none>
It looks like a duplication of MGMT-6469 cc: @frolland
Actually no, maybe it's just the content of the condition. @atraeger the condition is "ReadyForInstallation", the reason is "AgentAlreadyInstalling", do you think that the content should change to "The agent installation in progress"? The value is false because it's not longer ready for installation but seeing something as "cannot begin the installation" can be a bit intimidating. what do you think?
In case it's installed/error change to AgentInstallationStopped and ClusterInstallationStopped
https://github.com/openshift/assisted-service/pull/1802
This is validated on quay.io/ocpmetal/assisted-service-operator-bundle@sha256:79515efe3fb20e6bdf31a67db068cb076665fd9b9227c7c829bcca6c5d9b7994 I'm no longer getting the errors: The agent cannot begin the installation because it has already started The cluster cannot begin the installation because it has already started
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438