Bug 1542879

Summary:	rubygem(json) < 2 is not available on Fedora >= 27
Product:	[oVirt] ovirt-engine-sdk-ruby	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	Packaging.rpm	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Radim Hrazdil <rhrazdil>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.1	CC:	bugs, lveyde, mperina, omachace
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2+
Target Release:	4.2.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-ovirt-engine-sdk4-4.2.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:14:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1460625

Description Sandro Bonazzola 2018-02-07 09:15:47 UTC

Error: 
 Problem 1: conflicting requests
  - nothing provides rubygem(json) < 2 needed by rubygem-ovirt-engine-sdk4-4.2.2-1.20180207git5c1f05e.fc27.x86_64
 Problem 2: package rubygem-ovirt-engine-sdk4-doc-4.2.2-1.20180207git5c1f05e.fc27.x86_64 requires rubygem-ovirt-engine-sdk4 = 4.2.2-1.20180207git5c1f05e.fc27, but none of the providers can be installed
  - conflicting requests
  - nothing provides rubygem(json) < 2 needed by rubygem-ovirt-engine-sdk4-4.2.2-1.20180207git5c1f05e.fc27.x86_64

Comment 1 Sandro Bonazzola 2018-02-20 10:50:45 UTC

Hi, can you please check that a build including this has been done and added to release conf file? Can't see it in 4.2.2 conf files.

Comment 2 Ondra Machacek 2018-02-20 11:15:56 UTC

It's not, I will be doing release of SDK today.

Comment 3 Radim Hrazdil 2018-02-23 11:38:40 UTC

Verified on Fedora 27 that ovirt-engine-sdk gem version 4.2.3 installs successfully with ruby json dependency version 2.1.0.

Comment 4 Sandro Bonazzola 2018-03-29 11:14:06 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.