-
Notifications
You must be signed in to change notification settings - Fork 257
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
Can't start latest/9.0.9 version #660
Closed
Comments
@jmeixensperger it is still reproducible Linking the same issue - #667 |
@jmeixensperger any ETA for fixing this? |
@vtsvetkov-splunk Sorry I did not mean to close this--it should be fixed once the next release goes out. |
It works fine with 9.1 and 9.2. The |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use
latest
tag for running in our CI pipelines. It started failing recently. I realized that latest tag points to 9.0.9 instead of 9.2.1Then I tried to spin up the version 9.0.9 and got the same error as on CI:
Errors during Splunk initialization
failed: [localhost] (item={'key': '/servicesNS/nobody/splunk_instrumentation/admin/telemetry/general', 'value': 'showOptInModal=0&optInVersionAcknowledged=4'}) => {
"ansible_loop_var": "item",
"changed": false,
"item": {
"key": "/servicesNS/nobody/splunk_instrumentation/admin/telemetry/general",
"value": "showOptInModal=0&optInVersionAcknowledged=4"
}
}
MSG:
POST/servicesNS/nobody/splunk_instrumentation/admin/telemetry/generaladmin********8089{'showOptInModal': '0&optInVersionAcknowledged=4'}NoneNone[200, 201, 409];;; AND excep_str: URL: https://127.0.0.1:8089/servicesNS/nobody/splunk_instrumentation/admin/telemetry/general; data: {"showOptInModal": "0&optInVersionAcknowledged=4"}, exception: API call for https://127.0.0.1:8089/servicesNS/nobody/splunk_instrumentation/admin/telemetry/general and data as {'showOptInModal': '0&optInVersionAcknowledged=4'} failed with status code 400:
Argument "{"showOptInModal": "0" is not supported by this handler.
, failed with status code 400:
Argument "{"showOptInModal": "0" is not supported by this handler.
failed: [localhost] (item={'key': '/servicesNS/admin/search/data/ui/ui-tour/search-tour', 'value': 'tourPage=search&viewed=1'}) => {
"ansible_loop_var": "item",
"changed": false,
"item": {
"key": "/servicesNS/admin/search/data/ui/ui-tour/search-tour",
"value": "tourPage=search&viewed=1"
}
}
MSG:
POST/servicesNS/admin/search/data/ui/ui-tour/search-touradmin********8089{'tourPage': 'search&viewed=1'}NoneNone[200, 201, 409];;; AND excep_str: URL: https://127.0.0.1:8089/servicesNS/admin/search/data/ui/ui-tour/search-tour; data: {"tourPage": "search&viewed=1"}, exception: API call for https://127.0.0.1:8089/servicesNS/admin/search/data/ui/ui-tour/search-tour and data as {'tourPage': 'search&viewed=1'} failed with status code 400:
Argument "{"tourPage": "search" is not supported by this handler.
, failed with status code 400:
Argument "{"tourPage": "search" is not supported by this handler.
Reproduction:
https://github.com/vtsvetkov-splunk/crispy-fishstick/actions/runs/8484825990/job/23248480607#step:2:578
The workflow:
https://github.com/vtsvetkov-splunk/crispy-fishstick/actions/runs/8484825990/workflow
The text was updated successfully, but these errors were encountered: