Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create fsx lustre file system is not working #8654

Closed
banson-aiq opened this issue Apr 30, 2024 · 4 comments
Closed

create fsx lustre file system is not working #8654

banson-aiq opened this issue Apr 30, 2024 · 4 comments
Assignees
Labels
bug This issue is a bug. closing-soon This issue will automatically close in 4 days unless further comments are made. fsx p2 This is a standard priority issue

Comments

@banson-aiq
Copy link

Describe the bug

Run a command to create a lustre file system like so...

aws fsx create-file-system --region us-west-2 --file-system-type LUSTRE --storage-capacity 1200 --storage-type SSD --subnet-ids subnet-zzzzzzzz --security-group-ids sg-xxxxxxx --tags Key=env,Value=x Key=Name,Value=yyyyy --lustre-configuration 'WeeklyMaintenanceStartTime=6:18:00,DeploymentType=PERSISTENT_2,PerUnitStorageThroughput=125,DailyAutomaticBackupStartTime=18:00,AutomaticBackupRetentionDays=30,CopyTagsToBackups=true,DataCompressionType=NONE,RootSquashConfiguration={RootSquash=0:0,NoSquashNids=[]}' --version 2.15 --debug

The following output is shown, and there is no new fsx filesystem in the aws console

2024-04-30 23:14:08,707 - MainThread - awscli.clidriver - DEBUG - CLI version: aws-cli/2.15.42 Python/3.11.8 Linux/6.5.0-28-generic exe/x86_64.ubuntu.22
2024-04-30 23:14:08,707 - MainThread - awscli.clidriver - DEBUG - Arguments entered to CLI: ['fsx', 'create-file-system', '--region', 'us-west-2', '--file-system-type', 'LUSTRE', '--storage-capacity', '1200', '--storage-type', 'SSD', '--subnet-ids', 'subnet-zzzzzzzz', '--security-group-ids', 'sg-xxxxxxx', '--tags', 'Key=env,Value=x', 'Key=Name,Value=yyyyy', '--lustre-configuration', 'WeeklyMaintenanceStartTime=6:18:00,DeploymentType=PERSISTENT_2,PerUnitStorageThroughput=125,DailyAutomaticBackupStartTime=18:00,AutomaticBackupRetentionDays=30,CopyTagsToBackups=true,DataCompressionType=NONE,RootSquashConfiguration={RootSquash=0:0,NoSquashNids=[]}', '--version', '2.15', '--debug']
2024-04-30 23:14:08,720 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_s3 at 0x7d6c5fd179c0>
2024-04-30 23:14:08,720 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_ddb at 0x7d6c607472e0>
2024-04-30 23:14:08,720 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <bound method BasicCommand.add_command of <class 'awscli.customizations.configure.configure.ConfigureCommand'>>
2024-04-30 23:14:08,720 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function change_name at 0x7d6c60bc4fe0>
2024-04-30 23:14:08,720 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function change_name at 0x7d6c60bc6660>
2024-04-30 23:14:08,720 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function alias_opsworks_cm at 0x7d6c5fd223e0>
2024-04-30 23:14:08,720 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_history_commands at 0x7d6c60791d00>
2024-04-30 23:14:08,720 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <bound method BasicCommand.add_command of <class 'awscli.customizations.devcommands.CLIDevCommand'>>
2024-04-30 23:14:08,721 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_waiters at 0x7d6c5fd222a0>
2024-04-30 23:14:08,721 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <bound method AliasSubCommandInjector.on_building_command_table of <awscli.alias.AliasSubCommandInjector object at 0x7d6c5fdcf390>>
2024-04-30 23:14:08,721 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /usr/local/aws-cli/v2/2.15.42/dist/awscli/data/cli.json
aws-cli/2.15.42 Python/3.11.8 Linux/6.5.0-28-generic exe/x86_64.ubuntu.22 prompt/off

Expected Behavior

FSX Lustre filesystem should be created

Current Behavior

FSX Lustre filesystem is not created

Reproduction Steps

See aws cli command above

Possible Solution

No response

Additional Information/Context

No response

CLI version used

aws-cli/2.15.42 Python/3.11.8

Environment details (OS name and version, etc.)

Linux/6.5.0-28-generic exe/x86_64.ubuntu.22

@banson-aiq banson-aiq added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Apr 30, 2024
@tim-finnigan tim-finnigan self-assigned this Apr 30, 2024
@tim-finnigan
Copy link
Contributor

Hi @banson-aiq thanks for reaching out. I'll link the create-file-system for reference. It looks like the logs that you provided are not complete. Was an error returned or did the command run successfully? Can you also check that you are using the correct region/account in the console? Or you should also be able to run describe-file-systems to verify that the file system was created.

@tim-finnigan tim-finnigan added fsx response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Apr 30, 2024
@banson-aiq
Copy link
Author

@tim-finnigan hi, the logs shown are all that were returned. After the final log line the command ceased to run and the shell prompt was shown. There were no error messages, and no success messages.
I checked the console, and also ran describe-file-systems, I could not see any new FSX filesystem. I also checked the other US regions and I could not see any FSX filesystems.
It appears the command ran and ceased after printing the logs above. Nothing was provisioned

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label May 1, 2024
@tim-finnigan tim-finnigan added the investigating This issue is being investigated and/or work is in progress to resolve the issue. label May 3, 2024
@tim-finnigan
Copy link
Contributor

Thanks @banson-aiq for following up — upon revisiting this, I think the issue here is that your command is using the --version parameter, which is a global parameter for checking your CLI version (aws --version). It looks like you were intending to use --file-system-type-version.

@tim-finnigan tim-finnigan added closing-soon This issue will automatically close in 4 days unless further comments are made. and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. labels May 3, 2024
Copy link

github-actions bot commented May 6, 2024

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. closing-soon This issue will automatically close in 4 days unless further comments are made. fsx p2 This is a standard priority issue
Projects
None yet
Development

No branches or pull requests

2 participants