ID-related errors in v1 auth commands are confusing

[yangvipguang]

Version: 2.0.1
Deployement: Helm Install
I am so confused.
I have configured admin user with random password。And, I can login the ui with admin user, But it does't work in the telegraf agent .

[yangvipguang]

and I set up a different password with flux command 。But the result is same

[su600]

用InfluxDB生成的Token连接试试

[danxmoran]

Hi @yangvipguang, apologies for the confusion, we have an open issue to clarify our docs around V1 auth. You'll need to create a V1 compatibility token to use with the V1 influxdb telegraf output. The command you want is influx v1 auth create, you can see reference docs here.

[yangvipguang]

@danxmoran But I do't know what‘s wrong with this

[danxmoran]

@yangvipguang the read-bucket and write-bucket args should also be IDs, not names. influx bucket list will show you the ID for your monitoring bucket.

I have an open task to improve our validation errors so it's clear which arg is the problem, I'll add this case to the list.

[danxmoran]

@yangvipguang I've updated the title of this issue to reflect the problem with the latest error message you posted

[yangvipguang]

@danxmoran thanks it works。 But，the error message is indeed confusing for anyone not familiar with influxdb。one more question ：
Is the bucket the same as the database?

[yangvipguang]

@danxmoran But I have a new qustion:

[danxmoran]

You're receiving 404 responses from the server (not a connection refused error), so I think the k8s networking is set up properly. Have you created a DBRP mapping for your target bucket? If not, you'll need to:

1. Use influx v1 dbrp create to init a new DBRP mapping, pointing at your target bucket
2. Configure telegraf to use the DB/RP pair you used in step 1

[danxmoran]

I've merged a change that will (hopefully) make the error messages easier to understand in the future.

@yangvipguang I'm happy to keep helping, but for our tracking purposes I'm going to close this issue. For general questions, you can use one/both of:

• Our community Slack space
• Our community forum

Feel free to open more issues for specific bugs / feature requests as they come up.