Bug 1136423
| Summary: | Creating iSCSI or NFS Storage domains when master domain already exists adds these domains in maintenance mode | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Gilad Lazarovich <glazarov> | ||||||
| Component: | ovirt-engine-webadmin | Assignee: | Tal Nisan <tnisan> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Aharon Canan <acanan> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.5 | CC: | acanan, amureini, bugs, ecohen, gklein, mgoldboi, rbalakri, sbonazzo, yeylon, ylavi | ||||||
| Target Milestone: | m1 | Keywords: | UserExperience | ||||||
| Target Release: | 3.6.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | storage | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-07-22 08:17:57 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 933967 [details]
Logs from oVirt and 2 hosts, relevant timestamp around 18:30 on 2014-09-02
Re-targeting to 3.5.3 since this bug has not been marked as blocker for 3.5.2 and we have already released 3.5.2 Release Candidate. This has been the behavior since forever - do we want to change this? (In reply to Allon Mureinik from comment #3) > This has been the behavior since forever - do we want to change this? Adding a SD is not a common task. Is there any value to not activate it? Any tasks a user might want to do prior to activate? (In reply to Yaniv Dary from comment #4) > (In reply to Allon Mureinik from comment #3) > > This has been the behavior since forever - do we want to change this? > > Adding a SD is not a common task. Is there any value to not activate it? Any > tasks a user might want to do prior to activate? Yes, e.g., configure credentials as per bug 1239266. If we do change this, we should at the very least have a checkbox to allow choosing the non-default behavior. (In reply to Allon Mureinik from comment #5) > (In reply to Yaniv Dary from comment #4) > > (In reply to Allon Mureinik from comment #3) > > > This has been the behavior since forever - do we want to change this? > > > > Adding a SD is not a common task. Is there any value to not activate it? Any > > tasks a user might want to do prior to activate? > Yes, e.g., configure credentials as per bug 1239266. > If we do change this, we should at the very least have a checkbox to allow > choosing the non-default behavior. Closing as won't fix. We don't have a good reason to change the default here. |
Created attachment 933808 [details] After master domain exists, subsequent iSCSI and Data domains come up in Maintenance mode Description of problem: Creating iSCSI or NFS Storage domains when master domain already exists adds these domains in maintenance mode Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Add a master iSCSI domain 2. Add another iSCSI domain or an NFS Data domain Actual results: The second domain added it placed into Maintenance mode Expected results: The Storage data domain should become active and usable after their addition Additional info: See attached screenshot