f5os_tenant module creates tenants with 0 GB disk size and prevents you from suspending the tenant due to an error complaining about 0 GB storage

[davkwong]

COMPONENT NAME

f5os_tenant

Environment

ANSIBLE VERSION

ansible [core 2.17.4]
  config file = /opt/webex/NETSEC_LB_ANSIBLE/ansible.cfg
  configured module search path = ['/home/davkwong/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/webex/.virtualenvs/ansible_latest/lib/python3.10/site-packages/ansible
  ansible collection location = /home/davkwong/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/webex/.virtualenvs/ansible_latest/bin/ansible
  python version = 3.10.12 (main, Jul 29 2024, 16:56:48) [GCC 11.4.0] (/opt/webex/.virtualenvs/ansible_latest/bin/python)
  jinja version = 3.1.4
  libyaml = True

F5OS VERSION

1.7.0-8741

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

The f5os_tenant module does not have a field for specifying disk size and when a tenant is deployed, it is provisioned with a 0 GB disk size. Even though the file storage on the tenant appears to be fine, F5OS thinks there's 0 GB allocated. When we try to suspend the tenant by changing its state from Running to Provision, we get an error "Storage size(0) must be greater than or equal to 82"

STEPS TO REPRODUCE

# Create and Deploy the Tenant
- name: Create and Deploy the Tenant
  tags: always
  when: config_operation == 'add'
  f5networks.f5os.f5os_tenant:
    state: present
    name: "{{ tenant_hostname }}"
    nodes: 1
    cpu_cores: "{{ cpu_cores }}"
    memory: "{{ memory }}"
    image_name: "{{ tenant_image_filename }}"
    mgmt_ip: "{{ lookup('dig', tenant_hostname) }}"
    mgmt_prefix: "{{ mgmt_pfx }}"
    mgmt_gateway: "{{ mgmt_gw }}"
    running_state: deployed
    vlans: "{{ vlan_ids }}"
  register: deploy_tenant_output

EXPECTED RESULTS

ACTUAL RESULTS

[pgouband]

Hi,

Thanks for reporting. Added to the backlog and internal tracking ID for this request is: INFRAANO-1661.

[urohit011]

Hello, the new param, virtual_disk_size has been added to the module and available in the daily builds.