Description of problem: On this patch https://review.gluster.org/#/c/glusterfs/+/23783/ one of the test is getting crash so I want to reproduce the issue on softserve vm. I am not ableto create a vm on softserve infrastructure. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What issue you're facing? I 'm able to create a machine on softserve.
After creating the VM VM is not showing on the dashboard.
Same here, Creation of says successful but won't appear in dashboard
Deepshikha, the login/user you tried for the reproducer - is that an elevated privileges or, similar to user logins from Mohit and Kotresh? Screengrabs of the dashboard might be good to have attached with this report.
Machine did create for me but did not delete after an hour. There's an issue with the psycopg2 package in python. Looking more into it.
From the celery logs: Feb 10 06:25:04 softserve.int.rht.gluster.org celery[16460]: "Can't reconnect until invalid " Feb 10 06:25:04 softserve.int.rht.gluster.org celery[16460]: StatementError: (sqlalchemy.exc.InvalidRequestError) Can't reconnect until invalid transaction is rolled back [SQL: u'SELECT vm.id AS vm_id, vm.ip_address AS vm_ip_address, vm.vm_name AS vm_vm_name, vm.details_id AS vm_details_id, vm.created_at AS vm_created_at, vm.deleted_at AS vm_deleted_at, vm.state AS vm_state \nFROM vm \nWHERE vm.vm_name = %(vm_name_1)s AND vm.state = %(state_1)s \n LIMIT %(param_1)s'] [parameters: [{}]] Need to rollback the last commit.
It seems to be fixed. Please check and confirm.
I am not able to see VM on dashboard.
I see that error in the log: févr. 10 12:42:59 softserve.int.rht.gluster.org celery[30617]: <Response><Errors><Error><Code>InvalidKeyPair.Duplicate</Code><Message>The keypair 'moagrawa_test' already exists.</Message></Error></Errors><Reques And I can't find it in the interface for some reasons.
Michael, I fixed it. The deletion process did not happen because of sudden disconnect from db server. We can close the bug now.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days