Bug 1527313

Summary: Docs: document the limitation of 256 hosts per DC
Product: [oVirt] ovirt-engine Reporter: eberman
Component: DocumentationAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: adahms, dagur, rgolan
Target Milestone: ---Keywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-03 07:13:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description eberman 2017-12-19 08:00:57 UTC
Description of problem:
when trying to create more then 256 host getting UI notification on maximum Host limitation reached is this and official requirement ?

please add /refer to the it otherwise please explain why is it relevant since we are able to add much more

Version-Release number of selected component (if applicable):
[root@leopard03 ~]# rpm -qa libvirt*
libvirt-daemon-driver-storage-gluster-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-qemu-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-config-nwfilter-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-storage-core-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-storage-3.2.0-14.el7_4.4.x86_64
libvirt-libs-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-nodedev-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-storage-rbd-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-storage-iscsi-3.2.0-14.el7_4.4.x86_64
libvirt-python-3.2.0-3.el7_4.1.x86_64
libvirt-daemon-driver-secret-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-storage-disk-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-storage-logical-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-network-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-config-network-3.2.0-14.el7_4.4.x86_64
libvirt-client-3.2.0-14.el7_4.4.x86_64
libvirt-lock-sanlock-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-storage-mpath-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-interface-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-storage-scsi-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-kvm-3.2.0-14.el7_4.4.x86_64
libvirt-daemon-driver-nwfilter-3.2.0-14.el7_4.4.x86_64


Software Version:4.2.1-0.0.master.20171206161426.git88e9120.el7.centos


How reproducible:

100%
Steps to Reproduce:
1.add over 256 hosts
2.
3.

Actual results:

not possible unless changing default configuration file 
Expected results:

allow user to define per scale recommendation / add relevant requirement per actual topology 

Additional info:

Comment 1 Daniel Gur 2017-12-19 08:11:09 UTC
There are 3 ways to handle such limitation bugs:

1. The limitation should be fixed
QE will validate the fix and close the bug.

2. The limitation should be officially  documented - the bug  transferred to documentation team to document it
QE will validate the documentation and close the bug. 

3. If such documentation  already exist and public(we didn't find it) please  point us to it - QE will cancel the bug.

Comment 2 Yaniv Kaul 2017-12-19 11:06:06 UTC
(In reply to Daniel Gur from comment #1)
> There are 3 ways to handle such limitation bugs:
> 
> 1. The limitation should be fixed
> QE will validate the fix and close the bug.
> 
> 2. The limitation should be officially  documented - the bug  transferred to
> documentation team to document it
> QE will validate the documentation and close the bug. 

Done. This should be somewhere in https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/technical_reference/data_center_limitations

> 
> 3. If such documentation  already exist and public(we didn't find it) please
> point us to it - QE will cancel the bug.

Comment 3 Roy Golan 2018-01-15 13:28:39 UTC
Just adding how to technically allow more hosts in a single DC:

$ engine-config -s MaxNumberOfHostsInStoragePool=400

Comment 4 Casper (RHV QE bot) 2022-09-06 12:31:53 UTC
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).

Comment 5 Sandro Bonazzola 2023-08-03 07:13:40 UTC
No updates in the last 5 years, closing as won't fix.
If still relevant please open an issue on https://github.com/oVirt/ovirt-site/issues