question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to instantiate provider

See original GitHub issue

Informations

  • Qiskit version: 0.16.4
  • Python version: Python 3.8.6
  • Operating system: Mac OS Catalina

What is the current behavior?

I’m working at CQC. I am trying to connect to

{'hub': 'partner-cqc', 'group': 'internal', 'project': 'default'}

IBMQ webpage has instructions on how to do this:

image

but if I run this IBMQ would say no such provider, and fall back to the default hub and group.

Steps to reproduce the problem

from qiskit import IBMQ
IBMQ.load_account()

IBMQ.providers()
ibmqfactory._initialize_providers:WARNING:2021-02-19 18:43:24,359: Unable to instantiate provider for {'hub': 'partner-cqc', 'group': 'internal', 'project': 'default'}: string indices must be integers

>>> IBMQ.providers()
[<AccountProvider for IBMQ(hub='ibm-q', group='open', project='main')>]

As you can see, there is only one provider, but the warning suggests it knows about the other provider, as I have not given them this information.

What is the expected behavior?

Suggested solutions

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7

github_iconTop GitHub Comments

1reaction
jyu00commented, Feb 22, 2021

@y-richie-y You’ll have to ask your admin to work with IBM Quantum to resolve this issue.

0reactions
y-richie-ycommented, Feb 22, 2021

Thank you @jyu00 ! I know know that this is the source of error:

RequestsApiError: '403 Client Error: Forbidden for url: https://api-qcon.quantum-computing.ibm.com/api/Network/partner-cqc/Groups/internal/Projects/chessington/devices/v/1Forbidden country. {"error":"Forbidden country"}'

Is this something that can be fixed by work admin?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Terraform v0.13 "Failed to instantiate provider" for every project
Terraform automatically discovers provider requirements from your configuration, including providers used in child modules.
Read more >
Ask Question - Stack Overflow
upgrade from 0.12 to 0.13: Failed to instantiate provider "registry.terraform.io/-/aws" to obtain · Ask Question. Asked 1 year, 11 months ago.
Read more >
v0.13 - "Failed to instantiate provider xxxx to obtain schema
The solution was to remove the bad provider path (ex: "registry.terraform.io/-/aws") and replace it with the good one (ex: "registry.terraform. ...
Read more >
Failed to instantiate provider "aws" to obtain schema: fork/exec ...
Terraform has been successfully initialized!....etc``` ```$ terrafrm plan -out=plan.out Error: Failed to instantiate provider "aws" to ...
Read more >
upgrading terraform v0.13 to v1.0.0 “Failed to instantiate ...
You want to upgrade terraform from v0.13 to v1.0.0. Made changes to versions.tf. Also, you use different workspaces for storing state files.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found