Bug 1746357 - ship ioprocess in the host channel for 4.3
Summary: ship ioprocess in the host channel for 4.3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ioprocess
Version: 4.3.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.3.6
: ---
Assignee: Eyal Shenitzky
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-28 09:19 UTC by Sandro Bonazzola
Modified: 2019-10-10 15:39 UTC (History)
4 users (show)

Fixed In Version: ioprocess-1.2.1-1.el7ev
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-10 15:39:30 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3028 0 None None None 2019-10-10 15:39:31 UTC

Description Sandro Bonazzola 2019-08-28 09:19:24 UTC 
In 4.3.5 we shipped ioprocess to RHV-M channel, we need it in RHV Host channel.
Comment 1 Avihai 2019-09-01 14:57:09 UTC 
I do see ioprocess-1.1.2-1.el7ev.x86_64 on rhv-release-4.3.6-6 hosts.

Is this enough to verify this bug?

Also please move to ON_QA if this is indeed merged to 4.3.6-6.
Comment 2 Eyal Shenitzky 2019-09-02 05:31:58 UTC 
(In reply to Avihai from comment #1)
> I do see ioprocess-1.1.2-1.el7ev.x86_64 on rhv-release-4.3.6-6 hosts.
> 
> Is this enough to verify this bug?
> 
> Also please move to ON_QA if this is indeed merged to 4.3.6-6.

This bug is created for the errata
Comment 3 Avihai 2019-09-02 07:54:13 UTC 
(In reply to Eyal Shenitzky from comment #2)
> (In reply to Avihai from comment #1)
> > I do see ioprocess-1.1.2-1.el7ev.x86_64 on rhv-release-4.3.6-6 hosts.
> > 
> > Is this enough to verify this bug?
> > 
> > Also please move to ON_QA if this is indeed merged to 4.3.6-6.
> 
> This bug is created for the errata

Meaning what? How can I verify this bug?

I do see ioprocess-1.1.2-1.el7ev.x86_64 on rhv-release-4.3.6-6 hosts.
Is this enough to verify this bug?

Why is this bug in MODIFIED ?  
Please move to ON_QA if this is indeed merged to 4.3.6-6.
Comment 4 Eyal Shenitzky 2019-09-02 08:01:14 UTC 
It means that you should ignore this bug, this is for errata porpuses only.
Comment 8 errata-xmlrpc 2019-10-10 15:39:30 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2019:3028
Note You need to log in before you can comment on or make changes to this bug.