Hello @Jane. As we have discussed numerous times the process has not changed. Email your ticket and I will have it made public. They key is emailing the ticket. Based on ZenMaster feedback I raised and continue to voice the need for these to be visible to the person that logged the ticket. But I have not received any JIRA ticket numbers from you or others in a while. So please leverage the process for new issues moving forward.
As you already know...Zenoss Community Edition (Core) is the freemium version of Zenoss. Zenoss Support comes with Enterprise but we look at all JIRA issues since Core is release with and is a subset of the Enterprise feature set.
Hello @Nick! Open your ticket and shoot the JIRA number to me. Agreed these should be accessible to you and I voice this often internally. Key is to send me the link. This has not changed. Additionally I can track it them and review in the weekly meetings. My email is firstname.lastname@example.org. Always reach out to me with any questions.
Thanks @Nick. I updated the ticket and added a question for you. Please make sure you can access the ticket ok.
Dear All,I currently have exactly same issue as Nick. I've migrated system from Zenoss Core 5.3.3 to Zenoss Core 6.1.2. I tried to re-index device directory however without success:
serviced service attach zope su - zenosszencatalog run --createcatalog --forceindexAfter successful re-index run, the search has been checked. Unfortunately nothing has changed. I'm still getting errors when I'm trying to search devices. When I enter full name in device search (top right corner) it works, but when device name is not completed error is displayed (similar to poskey errors - yellow bar). It looks to me that that issue concerns solr. I checked jira and issue is still open. Maybe I should remove solr database and try to recreate it. I will be grateful for help,Thanks in advanceBest RegardsJ.K
Dear All,From what I was able to notice above problem is focused on codding inside following ZenPacks.zenoss.DeviceSearch. Is there anyone who fixed this issue since now? I tried to solve issue without reprogram Zenpack like using such as tools: zodbscan,zenrelactionscan,findposkeyerror,zencatalogscan, reindex solr and zenoss catalog, but my story did not end well. Have any of you tried the earlier version DeviceSearch?Thank you!
serviced service attach zope su - zenoss
zencatalog run --createcatalog --forceindex