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

wrong error message for new bots with existing ID #152

Closed
ghost opened this issue Feb 6, 2018 · 1 comment · Fixed by #276
Closed

wrong error message for new bots with existing ID #152

ghost opened this issue Feb 6, 2018 · 1 comment · Fixed by #276

Comments

@ghost
Copy link

ghost commented Feb 6, 2018

  • configure a bot
  • configure another bot with the same bot ID
  • warning message/popup:

    When you edit an ID what you are doing in fact is to create a clone of the current bot. You will have to delete the old one manually. Proceed with the operation?

That's misleading

@ghost ghost added this to the Release 1.0 milestone Feb 6, 2018
@ghost ghost modified the milestones: Release 1.0, Release 1.1 Apr 23, 2018
@ghost ghost modified the milestones: 1.1, 1.0.2 May 7, 2018
@ghost
Copy link
Author

ghost commented Jun 27, 2018

I don't know how to fix this one

ghost pushed a commit that referenced this issue Sep 25, 2018
1.0.2 Bugfix release

 ### Backend
- Emit a more specific error message for cases like #160.
- The timeout for calls to `intelmqctl` has been raised to 20s (#164).

 ### Pages

 #### Configuration
- Underscore is now allowed for new parameter names (#153).

 #### Monitor
* Fix link to monitor page (#157).

 ### Documentation
- Add a FAQ and add a section about the docker issue (#160).
- Add instructions for Debian 9, Ubuntu 18.04, and openSUSE Leap 42.3, 15.0 (#168).

 ### Packaging
- Include a positions file matching the default configuration of intelmq (#171).

 ### Known issues
* Missing CSRF protection (#111).
* Missing copyright notices (#140).
* Graph jumps around on "Add edge" bug component (#148).
* new runtime parameters with _ not possible (#153).
* wrong error message for new bots with existing ID (#152).
* Queue size for deleted queue remains displayed (#158).
@ghost ghost modified the milestones: 1.0.2, 1.1.1 Nov 12, 2018
@ghost ghost modified the milestones: 1.1.1, 2.0.1 May 22, 2019
@ghost ghost modified the milestones: 2.0.1, 2.1.1 Feb 18, 2020
@ghost ghost modified the milestones: 2.1.1, 2.1.2 May 27, 2020
@ghost ghost modified the milestones: 2.1.2, 2.3.0, 2.2.1 Jun 23, 2020
CSIRT-CZ pushed a commit to CZ-NIC/intelmq-manager that referenced this issue Jun 24, 2020
2.2.0 Feature release

This IntelMQ Manager version requires IntelMQ >= 2.2.0.

 ### Backend
- `config`: Get file paths from `intelmctl debug --get-paths` if possible and fall back to hard-coded paths otherwise. Thereby environment variables influencing the paths are respected (certtools#193).

 ### Pages
 #### About
- Show output of `intelmqctl debug`.

 ### Documentation
- Update release from intelmq's release documentation.
- Update Installation documentation: Fix & update dependencies and supported operating systems.

 ### Packaging
- Update default `positions.conf` to the default runtime/pipeline configuration of intelmq >= 2.1.1.

 ### Known issues
* Missing CSRF protection (certtools#111).
* Graph jumps around on "Add edge" (certtools#148).
* wrong error message for new bots with existing ID (certtools#152).
* `ALLOWED_PATH=` violates CSP (certtools#183).
* Monitor page: Automatic log refresh reset log page to first one (certtools#190).
@ghost ghost modified the milestones: 2.2.1, 2.3.0, 2.2.2 Jul 30, 2020
@ghost ghost modified the milestones: 2.2.2, 2.3.0 Feb 26, 2021
@ghost ghost modified the milestones: 2.3.0, 2.3.1 Mar 8, 2021
@ghost ghost removed this from the 2.3.1 milestone Mar 25, 2021
@ghost ghost added the help wanted label Jun 28, 2021
@monoidic monoidic mentioned this issue Aug 23, 2021
@ghost ghost closed this as completed in #276 Aug 25, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants