Bug 1490383
| Summary: | Auth plugin stopped working on Wildfly 11 | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Roy Golan <rgolan> |
| Component: | Backend.Core | Assignee: | Roy Golan <rgolan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Lukas Svaty <lsvaty> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.0 | CC: | bugs, lsvaty, mperina, rgolan, vtunka |
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Wildfly auth plugins code is initiating the ovirt plugin with a null parameter
Consequence: ovirt auth plugins fails to load - login into the wildfly management console fails constantly.
Fix: ignore the passed parameter, it is not needed for ovirt auth plugin anyway.
Result: ovirt auth plugin is loaded and access to the management console with proper admin credentials is working.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-12 10:12:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Roy Golan
2017-09-11 12:48:13 UTC
This is only failsafe to not block whole oVirt startup, but this issue needs to be fixed in WildFly Patch is merged already - anything needed here or can it move to MODIFIED? to verify run:
/usr/share/ovirt-engine-wildfly/bin/jboss-cli.sh \
--controller=remote+http://127.0.0.1:8706 \
--connect --user=admin@internal
you should see the prompt:
[standalone.0.1:8706 /]
verified in ovirt-engine-4.2.1.4-0.1.el7.noarch This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |