Like EC2, foreman should display serial console from GCE for instances created using Google CR.
Created from redmine issue https://projects.theforeman.org/issues/26787
Upstream bug assigned to kgaikwad
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26787 has been resolved.
Verified! @ Satellite 6.5.0 snap 10 Scenario 1: ======================== Steps: --------------- 1. Create and integrate GCE Compute resource. Observation: ---------------- 1. The console output is shown for provisioned VM under CR -> VMs -> VM -> Console, which is similar to the serial console logs in GCE VM. Scenario 2: ======================== Steps: ---------------- 1. Provision a VM from Satellite to GCE Observation: ---------------- 1. The console output is shown for provisioned host under Hosts -> Host -> Console, which is similar to the serial console logs in GCE VM. Scenario 3: ======================== Steps: ---------------- 1. Disassociate provisioned VM from host profile. Observation: ---------------- 1. The console output is shown for disassociated VM under CR -> VMs -> VM -> Console, which is similar to the serial console logs in GCE VM. Scenario 4: ======================== Steps: ----------------- 1. Import GCE VM as unmanaged host. Observation: ------------------ 1. The console output is shown for import as unmanaged host under Hosts -> Host -> Console, which is similar to the serial console logs in GCE VM. Scenario 5: ======================== Steps: ------------ 1. Create a VM in GCE. 2. Wait for VM to be listed under CR -> VMs as not assiciated or managed. Observation: -------------- 1. The console output is shown for not managed and not associated new VM created directly in GCE, under CR -> VMs -> VM -> Console, which is similar to the serial console logs in GCE VM. General Observation: ======================== Live console logs for any VM are not shown, revisiting page shows the new logs in console. (Expected)
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, 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-2019:3172