influxdata / influxdata/influxdb
OSS 2.7.1: Possible issue when creating alerts with Operator permissions
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. Install OSS 2.7.1, and setup with org, owner, and token
2. Install telegraf with inputs.ping plugin (see config below)
3. Create account with operator access
```
influx user create -n cozmo -p starwars -o lab --token $OWNER_TOKEN
influx auth create --operator -u cozmo -o lab --host http://oss:8086 -t $OWNER_TOKEN
```
4. As the owner create a basic deadman alert using the UI (see attached video)
5. As the operator create the same basic deadman alert using the UI (see attached video)
https://github.com/influxdata/influxdb/assets/86253101/c4b57402-dd33-43f9-824e-67a727e342b1
__Expected behavior:__
As the operator, creating the same alert as the owner shouldn't result in a failure
__Actual behavior:__
(see attached video)
__Environment info:__
* System info: Run `uname -srm` and copy the output here `Linux 4.18.0-348.7.1.el8_5.x86_64 x86_64`
* InfluxDB version: Run `influxd version` and copy the output here `InfluxDB v2.7.1 (git: 407fa622e9) build_date: 2023-04-28T13:24:27Z`
* Other relevant environment details: Container runtime, disk info, etc `Using Vagrant CentOS 8 VM`
__Config:__
Telegraf
```
[[inputs.cpu]]
percpu = false
totalcpu = true
fieldpass = ["usage_idle", "usage_user", "usage_system", "usage_steal"]
[[inputs.mem]]
[[inputs.net]]
[[inputs.netstat]]
[[inputs.diskio]]
[[inputs.processes]]
[[inputs.swap]]
[[inputs.system]]
[[inputs.disk]]
[[outputs.influxdb_v2]]
urls = ["http://oss:8086"]
## API token for authentication.
token = "$OWNER_TOKEN"
## Organization is the name of the organization you wish to write to; must exist.
organization = "lab"
## Destination bucket to write into.
bucket = "telegraf"
[[inputs.ping]]
urls = ["oss"]
```
Contributor guide
Research direction
Reproduce the alert-creation flow in OSS 2.7.1 using the owner and operator accounts described in the issue, starting with the UI steps and provided video. Capture the operator failure details and compare both requests or responses. Done means an operator can create the same basic deadman alert as an owner without failure.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, backend-api-design
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100