Bug 1448100
| Summary: | [OVN] - oVirt OVN provider password can't be empty | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> |
| Component: | BLL.Network | Assignee: | Marcin Mirecki <mmirecki> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mor <mkalfon> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.0 | CC: | bugs, mkalfon |
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The password for ovirt-provider-ovn during engine-setup can not be empty now.
Note that during engine installation, we will first be asked to use default credentials, and if so, the prompt for a password will never show.
It will be visible if the provider is installed during an engine-setup update run, or if use of default credentials is not chosen.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-20 11:30:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1457925 | ||
|
Description
Michael Burman
2017-05-04 14:18:18 UTC
There should be no default, then. During fresh install, we intended to take the password of admin@internal as the default password for ovirt-provider-ovn. But if too complex, we can avoid this, and force the user to retype the password on upgrade and on fresh install. Password is not mandatory. note that we do not ask for it if using default credentials Verified on 4.2.0-0.0.master.20170612192318.gitf773263.el7.centos 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. |