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

Can't create resources and command transports which require a port #2998

Closed
mwaldmueller opened this issue Oct 6, 2017 · 3 comments · Fixed by #3010
Closed

Can't create resources and command transports which require a port #2998

mwaldmueller opened this issue Oct 6, 2017 · 3 comments · Fixed by #3010
Assignees
Labels
bug Something isn't working queue/important Blocks a release or needs immediate attention
Milestone

Comments

@mwaldmueller
Copy link

It's not possible to create a new Command Transport for the monitoring module using the Icinga 2 API via GUI:

bildschirmfoto 2017-10-06 um 15 39 16

bildschirmfoto 2017-10-06 um 11 27 02

Environment

  • Icinga Web 2 version and modules (System - About): 2.4.2
  • Version used (icinga2 --version): r2.7.1-1
  • Operating System and version: CentOS Linux release 7.4.1708 (Core)
@nbuchwitz
Copy link
Contributor

Same error (port) here while adding a new ressource.

Environment

Icinga Web 2 version and modules (System - About): 2.4.2
Version used (icinga2 --version): r2.7.1-1
Operating System and version: CentOS Linux release 7.4.1708 (Core)

@lippserd lippserd changed the title New Command Transport doesn't recognize port setting Can't create resources and command transports which require a port Oct 9, 2017
@lippserd
Copy link
Member

lippserd commented Oct 9, 2017

Hi,

I included eb34300 in v2.4.2 and didn't recognize this issue in our final tests. Will be fixed asap.

@nilmerg Please take care of this issue.

Cheers,
Eric

@lippserd lippserd added bug Something isn't working queue/important Blocks a release or needs immediate attention labels Oct 9, 2017
@lippserd lippserd added this to the 2.5.0 milestone Oct 9, 2017
nilmerg added a commit that referenced this issue Oct 10, 2017
We can't do such things at the moment if it's a subform.

refs #2998
@dnsmichi
Copy link
Contributor

nilmerg added a commit that referenced this issue Oct 23, 2017
nilmerg added a commit that referenced this issue Oct 23, 2017
We don't care anymore about the BC in Zend version 1.12.7.
Hence we'll happily override setDefaults now. Yay!

refs #2998
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working queue/important Blocks a release or needs immediate attention
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants