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.

Sign up for GitHub

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

Jump to bottom

Not all Associated Groups are displayed on Inventory / Hosts / Groups page #6549

Closed
unlikelyzero opened this issue Apr 2, 2020 · 3 comments
Closed

Not all Associated Groups are displayed on Inventory / Hosts / Groups page #6549

unlikelyzero opened this issue Apr 2, 2020 · 3 comments
Assignees
@unlikelyzero @akus062381
Labels
component:ui type:bug

Comments

@unlikelyzero
Copy link

ISSUE TYPE
  • Bug Report
SUMMARY

Not all Associated Groups are displayed on Inventory / Hosts / Groups page

ENVIRONMENT
  • AWX version: 10.0
STEPS TO REPRODUCE

TBD

EXPECTED RESULTS
ACTUAL RESULTS
ADDITIONAL INFORMATION

Screen Shot 2020-04-02 at 12 51 33 PM
@unlikelyzero unlikelyzero mentioned this issue Apr 3, 2020
Merged
@unlikelyzero
Copy link
Author

retest in devel

@unlikelyzero unlikelyzero removed their assignment Dec 13, 2020
@unlikelyzero
Copy link
Author

Needs retesting and a functional test for the scenario above

@tiagodread
Copy link
Contributor

Verified manually importing groups from inventory source and the groups are displayed on the group tab for a particular host:

image

image

AlanCoding pushed a commit to AlanCoding/awx that referenced this issue Jan 22, 2024
@TheRealHaoLiu
[4.5][backport] Recover rsyslog after receiving 4xx from external log…
7ffe374 
… aggregator (ansible#6549)

* Remove superwatcher from docker-compose dev (ansible#14708)

When making changes to the application sometime you can accidentally cause FATAL state and cause the dev container to crash which will remove any ephemeral changes that you have made and is ANNOYING!

* Recover rsyslog from 4xx error

Due to ansible#7560

'omhttp' module for rsyslog will completely stop forwarding message to external log aggregator after receiving a 4xx error from the external log aggregator

This PR is an "workaround" for this problem by restarting rsyslogd after detecting that rsyslog received a 4xx error

* Correct misuse of stdxxx_event_enabled

Not every log messages need to be emitted as a event!

* Send SIGKILL to rsyslog if hard cancellation is needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@unlikelyzero unlikelyzero

@akus062381 akus062381

Labels
component:ui type:bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ryanpetrello @unlikelyzero @tiagodread @akus062381