On the systems that I build, the /boot partition is simply an ext4 or xfs file system. I would not be trying to use logical volume manager to try to build /boot.
I would also look at using a kick-start method or similar to automate the build and get the file systems built there rather than with ansible. Anyway that is what I do, others may have a different method that may work better in your case. When in trouble, or in doubt Run in circles, scream and shout On 11 July 2022, 3:58 pm, at 3:58 pm, Ashok Reddy <[email protected]> wrote: >Can you please suggest me how to fix this issue? > >On Monday, July 11, 2022 at 11:45:25 AM UTC+5:30 [email protected] >wrote: > >> You appear to be trying to do something to the /boot partition. >> >> Perhaps you are referring to the wrong device? >> >> >> >> When in trouble, or in doubt >> Run in circles, scream and shout >> On 11 July 2022, at 3:40 pm, Ashok Reddy <[email protected]> wrote: >>> >>> lsblk >>> >>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >>> >>> vda 252:0 0 50G 0 disk >>> >>> ├─vda1 252:1 0 500M 0 part /boot >>> >>> ├─vda2 252:2 0 4G 0 part [SWAP] >>> >>> └─vda3 252:3 0 10.5G 0 part / >>> >>> --- >>> >>> - hosts: default >>> >>> become: true >>> >>> become_method: sudo >>> >>> tasks: >>> >>> - name: part1 >>> >>> parted: >>> >>> device: "/dev/vda1" >>> >>> number: 1 >>> >>> state: present >>> >>> - name: filesystem >>> >>> filesystem: >>> >>> fstype: ext4 >>> >>> dev: /dev/vda1 >>> >>> - name: mounted >>> >>> mount: >>> >>> path: /opt >>> >>> src: /dev/vda1 >>> >>> fstype: ext4 >>> >>> state: mounted >>> >>> >>> - name: partition >>> >>> lvg: >>> >>> vg: "datavg" >>> >>> pvs: "/dev/vda1" >>> >>> state: present >>> >>> - name: resize pv >>> >>> command: "pvresize /dev/vda1" >>> >>> >>> - name: activate vg >>> >>> command: "vgchange -a y datavg" >>> >>> >>> - name: Ensure >>> >>> lvol: >>> >>> vg: datavg >>> >>> lv: datalv >>> >>> size: "100%FREE" >>> >>> ignore_errors: true >>> >>> >>> - name: sql file >>> >>> filesystem: >>> >>> dev: "/dev/datavg >>> >>> >>> error: >>> >>> TASK [part1] >>> >********************************************************************************************************************************************************************************************** >>> >>> fatal: [localhost]: FAILED! => {"changed": false, "err": "Error: >>> Partition(s) on /dev/vda1 are being used.\n", "msg": "Error while >running >>> parted script: /sbin/parted -s -m -a optimal /dev/vda1 -- unit KiB >mklabel >>> msdos mkpart primary 0% 100%", "out": "", "rc": 1} >>> >>> >>> >>> On Monday, July 11, 2022 at 10:52:11 AM UTC+5:30 Ashok Reddy wrote: >>> >>>> Thanks for providing your input. >>>> >>>> On Friday, July 8, 2022 at 5:18:41 PM UTC+5:30 [email protected] >>>> <http://href> wrote: >>>> >>>>> >>>>> >>>>> On 2022-07-08 (Fri) 11:50, Ashok Reddy wrote: >>>>> > I am trying to create new partition. >>>>> > If that is not available, so that only need to create the >/dev/vdb >>>>> > partition. >>>>> >>>>> Your logic is flawed. >>>>> You cannot create devices. >>>>> You can only create partitions on existing devices. >>>>> >>>>> >>>>> >>>>> > >-- >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/376bc342-0b42-46c1-a664-d3977bf235a5n%40googlegroups.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/54e13f42-7926-44d1-a6f3-a2f0ae4830d9%40gmail.com.
