Bug 1881828

Summary: [Assisted-4.6 ][Production]Private redhat account, with a non-redhat email account cannot install cluster
Product: OpenShift Container Platform Reporter: nshidlin <nshidlin>
Component: assisted-installerAssignee: Ronnie Lazar <alazar>
assisted-installer sub component: discovery-agent QA Contact: Yuri Obshansky <yobshans>
Status: CLOSED NOTABUG Docs Contact:
Severity: urgent    
Priority: urgent CC: aos-bugs, frolland
Version: 4.6Keywords: TestBlocker
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-23 10:04:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description nshidlin 2020-09-23 07:33:55 UTC
Description of problem:
When attempting to install a cluster with assisted installer using a personal redhat account with a gmail email address; the nodes are discovered successfully but the installation fails with the following error:

Sep 23 06:30:45 worker-0-0 agent[1856]: time="23-09-2020 06:30:45" level=info msg="Sending step <install-6de4a811> reply output <Logs were sent\n> error <Trying to pull registry.redhat.io/openshift4/assisted-installer-rhel8:v4.6.0-19...\n  unauthorized: Access to the requested resource is not authorized\nError: unable to pull registry.redhat.io/openshift4/assisted-installer-rhel8:v4.6.0-19: unable to pull image: Error determining manifest MIME type for docker://registry.redhat.io/openshift4/assisted-installer-rhel8:v4.6.0-19: Error reading manifest sha256:b31a13916dd4157e40d14d785131a48a0a6b9021a486ccd2f7493a24ff0a920b in registry.redhat.io/openshift4/assisted-installer-rhel8: unauthorized: Access to the requested resource is not authorized\n> exit-code <125>" file="step_processor.go:37" request_id=e8584696-6c09-4f00-b1fa-4cca36c2ae8d

Sep 23 06:30:47 worker-0-0 agent[1856]: time="23-09-2020 06:30:47" level=warning msg="Error processing posting step reply: Bad Request, Received step reply <install-6de4a811> from cluster <73f495b2-2e34-4209-b161-54437b0850bf> host <ea729c1e-3a6d-4628-a809-83c8b1c4da84>  exit-code <125> stdout <Logs were sent\n> stderr <Trying to pull registry.redhat.io/openshift4/assisted-installer-rhel8:v4.6.0-19...\n  unauthorized: Access to the requested resource is not authorized\nError: unable to pull registry.redhat.io/openshift4/assisted-installer-rhel8:v4.6.0-19: unable to pull image: Error determining manifest MIME type for docker://registry.redhat.io/openshift4/assisted-installer-rhel8:v4.6.0-19: Error reading manifest sha256:b31a13916dd4157e40d14d785131a48a0a6b9021a486ccd2f7493a24ff0a920b in registry.redhat.io/openshift4/assisted-installer-rhel8: unauthorized: Access to the requested resource is not authorized\n>" file="step_processor.go:59" request_id=e8584696-6c09-4f00-b1fa-4cca36c2ae8d

Version-Release number of selected component (if applicable):

Production:
{
    "release_tag": "v1.0.9.5-ds",
    "versions": {
        "assisted-ignition-generator": "quay.io/ocpmetal/assisted-ignition-generator:v1.0.9.5",
        "assisted-installer": "registry.redhat.io/openshift4/assisted-installer-rhel8:v4.6.0-19",
        "assisted-installer-controller": "registry.redhat.io/openshift4/assisted-installer-reporter-rhel8:v4.6.0-15",
        "assisted-installer-service": "quay.io/app-sre/assisted-service:27cfe0d",
        "discovery-agent": "registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-15",
        "image-builder": "quay.io/app-sre/assisted-iso-create:27cfe0d"
    }
}

How reproducible:


Steps to Reproduce:
1. Attempt to Install a cluster using a personal redhat account

Actual results:
Cluster installation fails

Expected results:
Cluster to install successfully 

Additional info:

Comment 1 Fred Rolland 2020-09-23 08:56:01 UTC
I suspect it was a temporary issue as the user was new.

Comment 2 nshidlin 2020-09-23 10:04:30 UTC
As Fred mentioned this was a temporary issue, that did not reproduce.