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

Unable to set states when adding new Icinga User template #1037

Closed
chrisg86 opened this Issue Jul 27, 2017 · 5 comments

Comments

Projects
None yet
4 participants
@chrisg86

chrisg86 commented Jul 27, 2017

I am trying to create a new Icinga User template via Users / Contacts. Whenever I select anything for fields State or Transition types, it will highlight it red and showing following error message (this message is dynamic, in this case I've chosen Up/Down for States):

Got invalid property "Hosts", allowed are: (Up, Down, OK, Warning, Critical, Unknown) (ExtensibleSet.php:472)

I expand State and transition type filters and try to select anything from the list for field States. What

Expected Behavior

It should let me select items from the lists.

Current Behavior

It show different values after I select an item from the list and highlights whatever I select in red. Besides I see an error message.

Possible Solution

The values of this select box might have gotten mixed up.

Steps to Reproduce (for bugs)

  1. Icinga Director -> Users / Contacts -> Tab Templates -> Add
  2. Expand State and transition type filters
  3. Select any value for State or Transition types
  4. See error message

Context

I was trying to add a new user template.

Your Environment

  • Director version (System - About): 1.3.1
  • Icinga Web 2 version and modules (System - About): 2.4.1
  • Icinga 2 version (icinga2 --version): r2.6.3-1
  • Operating System and version: Ubuntu 16.04.2 LTS
  • Webserver, PHP versions: nginx/1.10.3 PHP 7.0.18

@Thomas-Gelf Thomas-Gelf self-assigned this Jul 27, 2017

@Thomas-Gelf Thomas-Gelf added the bug label Jul 27, 2017

@Thomas-Gelf Thomas-Gelf added this to the 1.4.0 milestone Jul 27, 2017

@Thomas-Gelf

This comment has been minimized.

Show comment
Hide comment
@Thomas-Gelf

Thomas-Gelf Jul 27, 2017

Contributor

Oh, I see - thanks for reporting this. Will be fixed

Contributor

Thomas-Gelf commented Jul 27, 2017

Oh, I see - thanks for reporting this. Will be fixed

@vittel1

This comment has been minimized.

Show comment
Hide comment
@vittel1

vittel1 Jul 27, 2017

I guess when you fix the user state problem, this will be fixed as well?! (Notification States)

selection_172

vittel1 commented Jul 27, 2017

I guess when you fix the user state problem, this will be fixed as well?! (Notification States)

selection_172

@Thomas-Gelf

This comment has been minimized.

Show comment
Hide comment
@Thomas-Gelf

Thomas-Gelf Jul 27, 2017

Contributor

Yes, that's the same issue

Contributor

Thomas-Gelf commented Jul 27, 2017

Yes, that's the same issue

@chrisg86

This comment has been minimized.

Show comment
Hide comment
@chrisg86

chrisg86 commented Jul 27, 2017

@Thomas-Gelf Exactly

@lonelyadmin

This comment has been minimized.

Show comment
Hide comment
@lonelyadmin

lonelyadmin Nov 8, 2017

I still see this exact same thing in 1.4.1...should I be checking out a different revision?

lonelyadmin commented Nov 8, 2017

I still see this exact same thing in 1.4.1...should I be checking out a different revision?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment