Azure-docs: Trouble with the pull secret option

[dkypuros]

--pull-secret '$(< pull-secret.txt)'

The behavior of this command has been altered by the following extension: aro
Invalid --pull-secret.

Help and Man pages are sparse...

• az aro create --help
• man az aro create

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 93aa980e-1970-235c-228a-7b19880171b8
• Version Independent ID: 6f7937a4-12e0-d61c-3bd8-c6347ec48385
• Content: Tutorial - Create an Azure Red Hat OpenShift 4 cluster
• Content Source: articles/openshift/tutorial-create-cluster.md
• Service: container-service
• GitHub Login: @sakthi-vetrivel
• Microsoft Alias: suvetriv

[Karishma-Tiwari-MSFT]

Thanks for the feedback. To help me understand better, can you please elaborate on the issue you are seeing, for example at which step in the doc are you seeing issue, error message?

[dkypuros]

Under the section: Create the cluster.

az aro create \ --resource-group $RESOURCEGROUP \ --name $CLUSTER \ --vnet aro-vnet \ --master-subnet master-subnet \ --worker-subnet worker-subnet # --domain foo.example.com # [OPTIONAL] custom domain # --pull-secret '$(< pull-secret.txt)' # [OPTIONAL]

[lamek]

Really appreciate the feedback @dkypuros. I tried spinning up a few clusters this evening and had a similar issue with this command on both Linux and OSX, so I'll circle back with the team about updating this.

To help keep you moving, I was able to copy/paste the defaults with the following modifications:

• delete the line for using a custom domain (assuming you're not using one for your cluster)
• edit the pull secret line by deleting everything from the $ onwards. Then use the "Copy pull secret" button from your Red Hat cluster manager page. Paste in the copied secret, and don't forget to close with a single quote.

[Karishma-Tiwari-MSFT]

Thanks @lamek
Looks like this command was updated few days ago here: https://github.com/MicrosoftDocs/azure-docs/commit/8d07d97df51b01e01bc65bb9e1ed74439d506f6b
Before this update, it said

--pull-secret 'Pull secret from https://cloud.redhat.com/openshift/install/azure/installer-provisioned/' # [OPTIONAL]

[dkypuros]

Thanks @lamek
Looks like this command was updated few days ago here: 8d07d97
Before this update, it said

--pull-secret 'Pull secret from https://cloud.redhat.com/openshift/install/azure/installer-provisioned/' # [OPTIONAL]

Does the new command work? Has anyone tested it?

I'm referring to the command here: 8d07d97

# --pull-secret 'Pull secret from https://cloud.redhat.com/openshift/install/azure/installer-provisioned/'

[dkypuros]

Really appreciate the feedback @dkypuros. I tried spinning up a few clusters this evening and had a similar issue with this command on both Linux and OSX, so I'll circle back with the team about updating this.

To help keep you moving, I was able to copy/paste the defaults with the following modifications:

• delete the line for using a custom domain (assuming you're not using one for your cluster)
• edit the pull secret line by deleting everything from the $ onwards. Then use the "Copy pull secret" button from your Red Hat cluster manager page. Paste in the copied secret, and don't forget to close with a single quote.

@lamek I'll spin up a cluster tonight and test both methods mentioned in this thread.

[dkypuros]

First test - based on changes from: 8d07d97

```az aro create \
--resource-group $RESOURCEGROUP \
--name $CLUSTER \
--vnet aro-vnet \
--master-subnet master-subnet \
--worker-subnet worker-subnet \
--pull-secret 'Pull secret from https://cloud.redhat.com/openshift/install/azure/installer-provisioned/'

*Failed:* The update from 8d07d97 is not accurate from my test.
(followed the command "exactly as stated". I would not put any documentation instruction in an actual CLI command area.)

...CLI OUTPUT (Fedora 31)...
```The behavior of this command has been altered by the following extension: aro
No --pull-secret provided: cluster will not include samples or operators from Red Hat or from certified partners.
 - Running ..

Note: It looks like it's continuing to install the cluster despite the "--pull-secret" error.

PS. Curious what happens if I cancel the cluster creation while in "running" status. Will the "az openshift delete" command still work. Wondering if "az openshift delete" can handle partially created clusters. Mmm.

# az openshift delete --resource-group $CLUSTER_NAME --name $CLUSTER_NAME

Update: once the cluster create command starts "running", you can't stop the process until it finishes.

Request is not allowed in provisioningState 'Creating'.

[dkypuros]

SUCCESS!!=========================

Environment. Fresh install; Fedora 31. Latest version of ARO (as of today).

This command successfully works:

az aro create \
--resource-group $RESOURCEGROUP \
--name $CLUSTER \
--vnet aro-vnet-2 \
--master-subnet master-subnet-2 \
--worker-subnet worker-subnet-2 \
--pull-secret '0LXJc2-THIS-IS-A-FAKE-EXAMPLE-key-xUtZGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2RhdmlkaGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwdGV2K2Rhdmlka3lwd'

I recommend someone creates a pull request helping folks use this command, until the file version is repaired.

[dkypuros]

Let me know when you guys update the docs, or need help changing the docs.

[lamek]

Thanks @dkypuros. Draft commit is here if you'd like to check it out: https://github.com/lamek/azure-docs/commit/7b1d273f9529942cffe3c60eab9bdf6add4fd8c5#diff-cb96190a5610f6f3b9de7d9b7800a234R196

Some other changes need to be made as well, but for pull-secret specifically we're going to use the @pull-secret.txt format on the parameter.

Thanks again for all the feedback. The more the merrier.

[dkypuros]

Dumb question, but "--pull-secret @pull-secret.txt" works correctly?

[lamek]

Yes, we tested this morning. Be sure to execute az aro create from the same directory where you stored your pull-secret.txt, and watch out to add a trailing backslash to the command on the previous line.

More (doc) improvements to come as well.

Please let us know if you hit issues.

[dkypuros]

any need to update

az version
az extension list
az provider list

[lamek]

To be safe I'd make sure you meet the prereqs in the docs. If you've already me those then I don't think you need to update, but not entirely sure.

[dkypuros]

sounds good

On Mon, May 4, 2020 at 11:25 AM Kevin Lamenzo [e-mail]
wrote:

To be safe I'd make sure you meet the prereqs in the docs. If you've
already me those then I don't think you need to update, but not
entirely sure.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/53604#issuecomment-623565987,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACY2UHPVIG7P5YQLUF7M3LRP3UBJANCNFSM4MTX5WJQ
.

[thekad]

I believe the pull secret is a .docker/config.json style file, meaning your pull-secret.json file should look something like this:

{
  "auths": {
    "registry.connect.redhat.com": {
      "auth": "<really long key>"
    },
    "registry.redhat.io": {
      "auth": "<really long key>"
    }
  }
}

I formatted the above for clarity, but when passing the value to --pull-secret you should compact it, e.g. with --pull-secret "$(jq -c . pull-secret.json)"

[Karishma-Tiwari-MSFT]

The PR is merged now. Thanks @lamek.
@all, Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.