Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to influx pkg export with InfluxDB Cloud 2.0 (AWS US West 2) #16819

Closed
wojciechka opened this issue Feb 11, 2020 · 0 comments · Fixed by #16822
Closed

Unable to influx pkg export with InfluxDB Cloud 2.0 (AWS US West 2) #16819

wojciechka opened this issue Feb 11, 2020 · 0 comments · Fixed by #16822

Comments

@wojciechka
Copy link

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

  1. Create a new bucket and get its id
  2. Get an all access token to account in InfluxDB Cloud 2
  3. Run InfluxDB CLI (I have used the Linux x64 binary from 2.0.0 beta 2):
$ influx pkg export --buckets 99154ad5f0d4fa21 --host https://us-west-2-1.aws.cloud2.influxdata.com --token $(cat .token)

Expected behavior:
YAML file with the bucket exported

Actual behavior:
Error retrieved:

Error: Unexpected end of JSON input:.
See 'influx pkg export -h' for help

As a side note, trying to retrieve a label, a bucket or a variable results in same error.

Environment info:
Machine where I ran the client is Ubuntu 18.04 Linux, run as a VM.

I have tried creating a brand new bucket as wlel

The influx CLI from 2.0.0 beta 2 was used.

Metadata about the bucket I have tried to retrieve:

{
	"id": "99154ad5f0d4fa21",
	"orgID": "9301a68a67791071",
	"type": "user",
	"name": "test",
	"retentionRules": [],
	"createdAt": "2020-02-11T16:23:17.837060108Z",
	"updatedAt": "2020-02-11T16:23:17.837060209Z",
	"links": {
		"labels": "/api/v2/buckets/99154ad5f0d4fa21/labels",
		"logs": "/api/v2/buckets/99154ad5f0d4fa21/logs",
		"members": "/api/v2/buckets/99154ad5f0d4fa21/members",
		"org": "/api/v2/orgs/9301a68a67791071",
		"owners": "/api/v2/buckets/99154ad5f0d4fa21/owners",
		"self": "/api/v2/buckets/99154ad5f0d4fa21",
		"write": "/api/v2/write?org=9301a68a67791071\u0026bucket=99154ad5f0d4fa21"
	},
	"labels": []
}
jsteenb2 added a commit that referenced this issue Feb 11, 2020
2 issues from investigating this error. First is the status check func
did not identify it was a media unsupported issue adn tries to unmarshal
the empty response body. The 2nd, was the double content type headers were
causing an error. Locally this error does not surface, cannot repoduce on
macos, but in cloud it is persistent.

closes: #16819
jsteenb2 added a commit that referenced this issue Feb 11, 2020
2 issues from investigating this error. First is the status check func
did not identify it was a media unsupported issue adn tries to unmarshal
the empty response body. The 2nd, was the double content type headers were
causing an error. Locally this error does not surface, cannot repoduce on
macos, but in cloud it is persistent.

closes: #16819
jsteenb2 added a commit that referenced this issue Feb 11, 2020
2 issues from investigating this error. First is the status check func
did not identify it was a media unsupported issue adn tries to unmarshal
the empty response body. The 2nd, was the double content type headers were
causing an error. Locally this error does not surface, cannot repoduce on
macos, but in cloud it is persistent.

closes: #16819
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant