[ovirt-devel] Iscsi and other BAD buggy

[Yaniv Kaul]

On Tue, Mar 1, 2016 at 4:56 PM, Вячеслав Бадалян <v.badalyan at open-bs.ru> wrote:
> Hello.

Hi - please join the devel or users mailing list.

>
> ZERO) https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt
> Sorry, entering a bug into the product oVirt has been disabled

We were promoted to a classification. Please try
https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt

>
> And lets go.

It may be more efficient to send an email per issue - especially if
they are separate issues (storage, networking, etc.)
Y.

>
> A) If host with ovirt have iscsi target we will have bug troubles.
>
> Its looks like
> 1. Create targetcli from LVM
> 2. All ok
> 3. Reboot
> 4/ LVM found oVIrt partitions and connect it.
> 5. targetcli can't get device. It's allready busy.
>
> If you add some filter to don's search iscsi devices then ovirt does not
> work correctly.
>
> B) Some throuble with glusterD. VSDM do mount of hosted engine volume and
> this host is aslo GluserD Server. Bug troubles.
>
> C) If i reboot 1 of 3 gluster servers then hosted engine will very slowly.
> Have many errors in dmes, Agent-ha reboot VM. Vm can't conect to don't full
> cluster and stuck in Paused mode. Realy...
>
> Its all look so bad... i mirgrate to NFS :(
>
> D) Network conffugurate realy bad. If i need to change network i can't do
> it. oVirt save posted from web settings. Bug vsdm-networking MUST fallback
> to previos setup if i mistake or SERVIS does not start.
>
> E). Ovirt reports does not install.
>
>      [java] org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'actionModelService' defined in file
> [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext.xml]:
> Invocation of init method failed; nested exception is
> java.lang.ExceptionInInitializerError
>
> 2016-02-28 09:20:59 DEBUG
> otopi.plugins.ovirt_engine_setup.ovirt_engine_reports.jasper.deploy
> plugin.execute:941 execute-output: ('./js-ant',
> '-DmasterPropsSource=/tmp/tmp3paFhC/config', 'import-minimal-ce') stderr:
> OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support
> was removed in 8.0
>
> BUILD FAILED
> /usr/share/jasperreports-server/buildomatic/bin/import-export.xml:263: The
> following error occurred while executing this line:
> /usr/share/jasperreports-server/buildomatic/bin/import-export.xml:142: Java
> returned: 255
>
> Total time: 24 seconds
>
> 2016-02-28 09:20:59 DEBUG otopi.context context._executeMethod:156 method
> exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 146, in
> _executeMethod
>     method['method']()
>   File
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-reports/jasper/deploy.py",
> line 656, in _deploy
>     self._buildJs(config=config, cmd=cmd)
>   File
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-reports/jasper/deploy.py",
> line 215, in _buildJs
>     'buildomatic',
>   File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 946, in
> execute
>     command=args[0],
> RuntimeError: Command './js-ant' failed to execute
> 2016-02-28 09:20:59 ERROR otopi.context context._executeMethod:165 Failed to
> execute stage 'Misc configuration': Command './js-ant' failed to execute
> 2016-02-28 09:20:59 DEBUG otopi.transaction transaction.abort:134 aborting
> 'Yum Transaction'
> 2016-02-28 09:20:59 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:95 Yum Performing yum transaction rollback
> Загружены модули: fastestmirror, versionlock
>
>
>
>
>
> --
>
> --
> С уважением,
> Бадалян Вячеслав Борисович
>
> ООО "Открытые бизнес-решения"
> Технический директор
> +7 (495) 666-0-111
> http://www.open-bs.ru
>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel