Hi Gianluca,
please see my replies inline
On Tue, Oct 6, 2020 at 11:37 AM Gianluca Cecchi
wrote:
> On Tue, Oct 6, 2020 at 11:25 AM Martin Perina wrote:
>
>>
>>> You say to drive a command form the engine that is a VM that runs inside
>>> the host, but ask to shutdown VMs running on host
On Tue, Oct 6, 2020 at 11:25 AM Martin Perina wrote:
>
>> You say to drive a command form the engine that is a VM that runs inside
>> the host, but ask to shutdown VMs running on host before...
>> This is a self hosted engine composed by only one single host.
>> Normally I would use the
On Mon, Oct 5, 2020 at 3:25 PM Gianluca Cecchi
wrote:
>
>
> On Mon, Oct 5, 2020 at 3:13 PM Dana Elfassy wrote:
>
>> Can you shutdown the vms just for the upgrade process?
>>
>> On Mon, Oct 5, 2020 at 1:57 PM Gianluca Cecchi
>> wrote:
>>
>>> On Mon, Oct 5, 2020 at 12:52 PM Dana Elfassy
>>>
On Mon, Oct 5, 2020 at 3:13 PM Dana Elfassy wrote:
> Can you shutdown the vms just for the upgrade process?
>
> On Mon, Oct 5, 2020 at 1:57 PM Gianluca Cecchi
> wrote:
>
>> On Mon, Oct 5, 2020 at 12:52 PM Dana Elfassy wrote:
>>
>>> In order to run the playbooks you would also need the
Can you shutdown the vms just for the upgrade process?
On Mon, Oct 5, 2020 at 1:57 PM Gianluca Cecchi
wrote:
> On Mon, Oct 5, 2020 at 12:52 PM Dana Elfassy wrote:
>
>> In order to run the playbooks you would also need the parameters that
>> they use - some are set on the engine side
>> Why
On Mon, Oct 5, 2020 at 12:52 PM Dana Elfassy wrote:
> In order to run the playbooks you would also need the parameters that they
> use - some are set on the engine side
> Why can't you upgrade the host from the engine admin portal?
>
>
Because when you upgrade a host you put it into maintenance
In order to run the playbooks you would also need the parameters that they
use - some are set on the engine side
Why can't you upgrade the host from the engine admin portal?
On Mon, Oct 5, 2020 at 12:31 PM Gianluca Cecchi
wrote:
> On Mon, Oct 5, 2020 at 10:37 AM Dana Elfassy wrote:
>
>> Yes.
On Mon, Oct 5, 2020 at 9:06 AM Gianluca Cecchi
wrote:
>
> On Mon, Oct 5, 2020 at 2:19 AM Nir Soffer wrote:
>>
>> On Sun, Oct 4, 2020 at 6:09 PM Amit Bawer wrote:
>> >
>> >
>> >
>> > On Sun, Oct 4, 2020 at 5:28 PM Gianluca Cecchi
>> > wrote:
>> >>
>> >> On Sun, Oct 4, 2020 at 10:21 AM Amit
On Mon, Oct 5, 2020 at 10:37 AM Dana Elfassy wrote:
> Yes.
> The additional main tasks that we execute during host upgrade besides
> updating packages are certificates related (check for certificates
> validity, enroll certificates) , configuring advanced virtualization and
> lvm filter
> Dana
>
Yes.
The additional main tasks that we execute during host upgrade besides
updating packages are certificates related (check for certificates
validity, enroll certificates) , configuring advanced virtualization and
lvm filter
Dana
On Mon, Oct 5, 2020 at 9:31 AM Sandro Bonazzola wrote:
>
>
> Il
On Mon, Oct 5, 2020 at 8:31 AM Sandro Bonazzola wrote:
>
>> OK, so I tried on my single host HCI installed with ovirt-node-ng 4.4.0
>> and gluster wizard and never update until now.
>> Updated self hosted engine to 4.4.2 without problems.
>>
>> My host doesn't have any filter or global_filter
Il giorno sab 3 ott 2020 alle ore 14:16 Gianluca Cecchi <
gianluca.cec...@gmail.com> ha scritto:
> On Fri, Sep 25, 2020 at 4:06 PM Sandro Bonazzola
> wrote:
>
>>
>>
>> Il giorno ven 25 set 2020 alle ore 15:32 Gianluca Cecchi <
>> gianluca.cec...@gmail.com> ha scritto:
>>
>>>
>>>
>>> On Fri, Sep
On Mon, Oct 5, 2020 at 2:19 AM Nir Soffer wrote:
> On Sun, Oct 4, 2020 at 6:09 PM Amit Bawer wrote:
> >
> >
> >
> > On Sun, Oct 4, 2020 at 5:28 PM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
> >>
> >> On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer wrote:
> >>>
> >>>
> >>>
> >>> Since
On Sun, Oct 4, 2020 at 6:09 PM Amit Bawer wrote:
>
>
>
> On Sun, Oct 4, 2020 at 5:28 PM Gianluca Cecchi
> wrote:
>>
>> On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer wrote:
>>>
>>>
>>>
>>> Since there wasn't a filter set on the node, the 4.4.2 update added the
>>> default filter for the root-lv
On Sun, Oct 4, 2020 at 5:28 PM Gianluca Cecchi
wrote:
> On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer wrote:
>
>>
>>
>> Since there wasn't a filter set on the node, the 4.4.2 update added the
>> default filter for the root-lv pv
>> if there was some filter set before the upgrade, it would not have
On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer wrote:
>
>
> Since there wasn't a filter set on the node, the 4.4.2 update added the
> default filter for the root-lv pv
> if there was some filter set before the upgrade, it would not have been
> added by the 4.4.2 update.
>
>>
>>
Do you mean that I
On Sun, Oct 4, 2020 at 2:07 AM Gianluca Cecchi
wrote:
> On Sat, Oct 3, 2020 at 9:42 PM Amit Bawer wrote:
>
>>
>>
>> On Sat, Oct 3, 2020 at 10:24 PM Amit Bawer wrote:
>>
>>>
>>>
>>> For the gluster bricks being filtered out in 4.4.2, this seems like [1].
>>>
>>> [1]
On Sat, Oct 3, 2020 at 9:42 PM Amit Bawer wrote:
>
>
> On Sat, Oct 3, 2020 at 10:24 PM Amit Bawer wrote:
>
>>
>>
>> For the gluster bricks being filtered out in 4.4.2, this seems like [1].
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1883805
>>
>
> Maybe remove the lvm filter from
On Sat, Oct 3, 2020 at 10:24 PM Amit Bawer wrote:
>
>
> On Sat, Oct 3, 2020 at 7:26 PM Gianluca Cecchi
> wrote:
>
>> On Sat, Oct 3, 2020 at 4:06 PM Amit Bawer wrote:
>>
>>> From the info it seems that startup panics because gluster bricks cannot
>>> be mounted.
>>>
>>>
>> Yes, it is so
>> This
On Sat, Oct 3, 2020 at 7:26 PM Gianluca Cecchi
wrote:
> On Sat, Oct 3, 2020 at 4:06 PM Amit Bawer wrote:
>
>> From the info it seems that startup panics because gluster bricks cannot
>> be mounted.
>>
>>
> Yes, it is so
> This is a testbed NUC I use for testing.
> It has 2 disks, the one named
On Sat, Oct 3, 2020 at 6:33 PM Gianluca Cecchi
wrote:
> Sorry I see that there was an error in the lsinitrd command in 4.4.2,
> inerting the "-f" position.
> Here the screenshot that shows anyway no filter active:
>
>
Sorry I see that there was an error in the lsinitrd command in 4.4.2,
inerting the "-f" position.
Here the screenshot that shows anyway no filter active:
https://drive.google.com/file/d/19VmgvsHU2DhJCRzCbO9K_Xyr70x4BqXX/view?usp=sharing
Gianluca
On Sat, Oct 3, 2020 at 6:26 PM Gianluca Cecchi
On Sat, Oct 3, 2020 at 4:06 PM Amit Bawer wrote:
> From the info it seems that startup panics because gluster bricks cannot
> be mounted.
>
>
Yes, it is so
This is a testbed NUC I use for testing.
It has 2 disks, the one named sdb is where ovirt node has been installed.
The one named sda is
>From the info it seems that startup panics because gluster bricks cannot be
mounted.
The filter that you do have in the 4.4.2 screenshot should correspond to
your root pv,
you can confirm that by doing (replace the pv-uuid with the one from your
filter):
#udevadm info
Il giorno ven 25 set 2020 alle ore 15:32 Gianluca Cecchi <
gianluca.cec...@gmail.com> ha scritto:
>
>
> On Fri, Sep 25, 2020 at 1:57 PM Sandro Bonazzola
> wrote:
>
>> oVirt Node 4.4.2 is now generally available
>>
>> The oVirt project is pleased to announce the general availability of
>> oVirt
On Fri, Sep 25, 2020 at 1:57 PM Sandro Bonazzola
wrote:
> oVirt Node 4.4.2 is now generally available
>
> The oVirt project is pleased to announce the general availability of oVirt
> Node 4.4.2 , as of September 25th, 2020.
>
> This release completes the oVirt 4.4.2 release published on
26 matches
Mail list logo
