Is that a space before snapshot (right where it says “Task” in the JSON request)? Was that part of the request or did you insert that by mistake when you copied it into the email?

- Rilindo

On Jan 21, 2024, at 9:13 PM, Prady A <[email protected]> wrote:


Hi,

Thank you both of you for your kind suggestions.
We are using leap-upgrade tool to upgrade. In upgrade there is no issue. We have a health checkup also post upgrade.

The issue is in VMware but not sure when creating manually the “Snapshot the virtual machine memory” is set to Yes but when I am creating the snapshot through ansible automatically it is setting as No. This is something with VMware maybe.. 

- Name: Create VM snapshot
   Uri: 
      User: “ {{ snapshot_user }}”
      Password: “{{ snapshot_Password }}“
      force_basic_auth: true
      Method: post 
      Body_format: json
      Body: |-
          {
             “Hostname”: “{{ vm_hostname }}”,
             “Task”: “ create”,
              “Snapshot_name”: “upgrade-{{vm_hostname}} “
           }
      Status code: 202
   Register: snapshot_result


Regards 
PD

   

On Sun, 21 Jan 2024 at 07:15, Nico Kadel-Garcia <[email protected]> wrote:
On Thu, Jan 18, 2024 at 8:16 PM Prady A <[email protected]> wrote:
>
> Hi experts,
>
> We are doing automation to update RHEL7-> RHEL8 .
> Before we upgrade we take the snapshot.
> The issue is whenever there is an upgrade failure we revert the server to its previous state. But it seems when we revert it the machine is in power off state..
> it seems when we take automatic snapshot it happens like that.. Any pointers pls
>
> Regards
> PD

That's a RHEL problem. It's not an operation supported by RHEL.
Updating the critical system libraries, such as glibc and the python
on which RPM is based, and RPM itself, is likely to trip over a *lot*
of problems without quite a lot of research and debugging. From
decades of experience with Red Hat based operating systems, I
recommend very strongly against this approach.

If I may suggest, take a disk image of the old system and build a new
system, with content copied as needed to configure the new system.

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAOCN9ry6d0wKwzJutwXDJSMH3X9vD51hLVqqtbJd9rHzRfkEKQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEuB3AoFvdepBuNSvKHQ%3Dc_TYpwUUjrF8QYdgMd_MKb22-8v8A%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5C29FCDA-9E8E-43D0-B343-46D172B5EF4F%40gmail.com.

Reply via email to