Security

 View Only
last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Back to discussions
Expand all | Collapse all

Clearpass Azure Image issues - 6.11.1.251304 vm morph Command failed with code -4

This thread has been viewed 10 times

  • 1.  Clearpass Azure Image issues - 6.11.1.251304 vm morph Command failed with code -4

    Posted Feb 15, 2024 01:24 PM

    Hi,

    We've been having significant issues with our Clearpass Azure deployment. We've had numerous TAC cases open without any resolution.

    Current system configuration:
    ----------------------------
    Number of CPUs = 4
    Total Memory = 18 GB
    Total Disk Size = 1568 GB
    Total Disk Write Throughput = 169 IOPS
    Total Disk Read Throughput = 492 IOPS
    ----------------------------

    Setup /dev/mapper/VolGroup00-image1 as luks device
    Command failed with code -4 (wrong device or file specified).
    Command failed with code -4 (wrong device or file specified).
    luks UUID:
    Opening device luks-
    Command failed with code -4 (wrong device or file specified).

    Stopping logging:                                          [  OK  ]
    Copying data. This may take a few minutes...
    Setting up boot targets...
    Filesystem setup is complete on the new disk at .
    Initiating reboot to complete this operation.

    This results in the VM Clearpass Server building - however the provisioned disk size doesn't match the orginal allocation.



  • 2.  RE: Clearpass Azure Image issues - 6.11.1.251304 vm morph Command failed with code -4

    Posted Feb 15, 2024 03:43 PM

    What exact issue are you trying to solve?


    Original Message


  • 3.  RE: Clearpass Azure Image issues - 6.11.1.251304 vm morph Command failed with code -4

    Posted Feb 15, 2024 04:36 PM

    this Azure Image needs to be pulled - it's a bad release. We now have to rebuild our entire cluster (again)

    Wish Aruba TAC had better bug scrub tools to let us know this ahead of time.


    Original Message