Description of problem: Following bz 961677 the REST API should be accessed using /ovirt-engine/api and not /api. Version-Release number of selected component (if applicable): 3.4 How reproducible: Always Steps to Reproduce: 1. engine-log-collector collect 2. 3. Actual results: Fails connecting to the engine with: ERROR: Unable to connect to REST API. Reason: Bad Request Expected results: Should not fail Additional info:
but we do support both /api and /ovirt-engine/api if there is a problem we need to know what it is. anyway, stupid question... why is log collector using the api?
(In reply to Alon Bar-Lev from comment #1) > but we do support both /api and /ovirt-engine/api if there is a problem we > need to know what it is. Right, sorry. There is no problem. Still we might want to change it to use /ovirt-engine/api, but it currently fails for me for some other reason. I'll check and might open another bug. > > anyway, stupid question... why is log collector using the api? To get a list of the hosts to collect logs from.
(In reply to Yedidyah Bar David from comment #2) > > > > anyway, stupid question... why is log collector using the api? > > To get a list of the hosts to collect logs from. hmmm.... won't it easier to access the database directly? then it can run if engine is down and no need for application admin password...
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
merged on upstream master and 3.4.0 branch.
Basic sanity test. Verified engine-log-collector collect works in ovirt-log-collector-3.4.0-0.5.beta3.el6.noarch.
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released