Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
External Participants:
Description
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
Activity
How are you able to use the scripts/CLI to create the instances in Fi-Lab?
You have also attached the output of nova list command ran with cli in the above comments. General users are not allowed to create instances in their account in Fi-Lab apart from cloud-portal !!!
You have also attached the output of nova list command ran with cli in the above comments. General users are not allowed to create instances in their account in Fi-Lab apart from cloud-portal !!!
Hello Fiware Lab Team,
Is there any written policy of fiware LAB that user could not use his/her tenant from CLI or API? As per my knowledge User is owner of that tenant and user have all the rights on his/her tenant. Because in Openstack, user can use his/her creds [auth_url (fiware lab url), username , tenant name and password] and make RC file. As fiware lab is Just openstack ,all openstack things are allowed within tenant by any mean GUI, CLI, API and lang SDK.
Please try to focus on solving problem or atleast provide logs of our instances as we have already mentioned 4-5 times in our previous mails. Only admin can access logs. So please try to find out all nova, neutron etc. logs , filter out them with our instance IDs. We will analyse logs and try to solve our problem.
Please take this on high priority as our worked is highly impacted. If any help required from our side we can try to help in user/tenant boundary.
Regards,
Mrinal Das & Ravinder Kumar
----Original Message----
From: Help-Desk jira-help-desk@jira.fiware.org
Sent: 26 November 2019 17:28
Cc: Mrinal Das <mrinal.das@india.nec.com>
Subject: [FIWARE-JIRA] (HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
Noida Node Helpdesk - Today 5:27 PM
------------------
How are you able to use the scripts/CLI to create the instances in Fi-Lab?
You have also attached the output of nova list command ran with cli in the above comments. General users are not allowed to create instances in their account in Fi-Lab apart from cloud-portal !!!
FW External User - Today 12:41 PM
------------------
Dear Noida Node Helpdesk,
Just to clarify, As discussed in last mail our script is launching instances one by one as we have set a parameter "wait: yes". But apart from this, there should be limit like 50 or 100 instances in parallel could not be launch, Not like only 2 instances. So please sound technically next time.
Please find below instance id & name:
Name: mrinal1
Id: eb2144eb-7472-4976-a894-a8e291db4f30
Name: mrinal2
Id: 7c00e28b-16b1-482a-abf2-0432c74b2cdb
Note: Please share logs related to below instance IDs. Let's find out root cause for Instance Error State.
Regards,
Mrinal Das
----Original Message----
From: Help-Desk jira-help-desk@jira.fiware.org
Sent: 26 November 2019 12:23
Cc: Mrinal Das <mrinal.das@india.nec.com>
Subject: [FIWARE-JIRA] (HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
Noida Node Helpdesk - Today 12:22 PM
------------------
Could you perform instantiation of instances with having gap of some time (e.g. of 5-10 seconds) between two instances, instead of launching instances in parallel.
FW External User - Today 11:28 AM
------------------
Adding Screenshots for further details.
From: Mrinal Das
Sent: 26 November 2019 11:08
To: 'jira-help-desk@jira.fiware.org' <jira-help-desk@jira.fiware.org>
Cc: Ajay Yadav <ajay.yadav@india.nec.com>; Anand Sahu <anand.sahu@india.nec.com>; Ravinder Kumar <ravinder.kumar@india.nec.com>
Subject: RE: [FIWARE-JIRA] (HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud
Dear fiware-helpdesk team,
As discussed with Aneel san we have perform the iteration again with higher timeout value of 6 minutes and wait = yes. But creation of one instance out of 2 is again in ERROR state .
So , we are sharing the process of sandbox code with fiware-helpdesk team for better understanding of our scenario.
Synopsis of os_server module in ansible: os_server is ansible module for Create/Delete Compute Instances from OpenStack
Script code:
os_server:
state: present # Should the resource be present or absent
name: "stuff.openstack.vm_name_prefix{{ item }}" #name of instance
key_name: "{{ stuff.openstack.key_name}}" #openstack key name
image: "{{ stuff.openstack.image}}" #openstack image name
wait: yes
timeout: 360
flavor: "{{ stuff.openstack.flavor}}" #openstack flavour
network: "{{ stuff.openstack.private_network}}"
security_groups: "{{ stuff.openstack.security_groups}}" #openstack security groups
boot_from_volume: yes # Should the instance boot from a persistent volume created based on the image given
meta:
hostname: "kube0{{ item }}"
register: openstackvmcreate
with_sequence:
count={{ stuff.openstack.count }}
please find the link for more details : https://docs.ansible.com/ansible/latest/modules/os_server_module.html
Please find the output of nova list
[root@infra-node tasks]# nova list
------------------------------------------------------------------------------------------------------+
------------------------------------------------------------------------------------------------------+
------------------------------------------------------------------------------------------------------+
Please find the cloud configuration settings :
openstack: # openstack group
vm_name_prefix: mrinal # prefix of VM name here (1,2,3... will be added to this based on count)
key_name: sandboxKey # security key-name same as in openstack
flavor: m1.medium # flavor name for instance as in openstack (Minimum ' m1.small ' is required)
private_network: node-int-net-01 # private network name as in openstack
external_network: public-ext-net-01 # external network name as in openstack
image: centos7.5 #supported Images versiona Centos7/ Ubuntu16 (name as your openstack image name)
security_groups: all # name of security group as in openstack
key_path: /tmp/sandbox.pem # path to security key file
count: 2 # number of VMs required
Our Script logs :
TASK [vm-deploy : Deploy an instance assuming image, network(public/private), flavor and key are already present in cloud.] ************
failed: [localhost] (item=1) => {"changed": false, "extra_data": {"server": {"OS-DCF:diskConfig": "MANUAL", "OS-EXT-AZ:availability_zone": "nova", "OS-EXT-SRV-ATTR:host": null, "OS-EXT-SRV-ATTR:hostname": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": null, "OS-EXT-SRV-ATTR:instance_name": null, "OS-EXT-SRV-ATTR:kernel_id": null, "OS-EXT-SRV-ATTR:launch_index": null, "OS-EXT-SRV-ATTR:ramdisk_id": null, "OS-EXT-SRV-ATTR:reservation_id": null, "OS-EXT-SRV-ATTR:root_device_name": null, "OS-EXT-SRV-ATTR:user_data": null, "OS-EXT-STS:power_state": 0, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "error", "OS-SCH-HNT:scheduler_hints": null, "OS-SRV-USG:launched_at": null, "OS-SRV-USG:terminated_at": null, "accessIPv4": "", "accessIPv6": "", "addresses": {}, "adminPass": null, "az": "nova", "block_device_mapping": null, "cloud": "envvars", "config_drive": "", "created": "2019-11-26T05:14:12Z", "created_at": "2019-11-26T05:14:12Z", "description": "mrinal1", "disk_config": "MANUAL", "flavor": {"disk": 40, "ephemeral": 0, "extra_specs": {}, "original_name": "m1.medium", "ram": 4096, "swap": 0, "vcpus": 2}, "has_config_drive": false, "host": null, "hostId": "", "host_id": "", "host_status": null, "hostname": null, "hypervisor_hostname": null, "id": "eb2144eb-7472-4976-a894-a8e291db4f30", "image":
{"id": null}, "instance_name": null, "interface_ip": "", "kernel_id": null, "key_name": "sandboxKey", "launch_index": null, "launched_at": null, "location": {"cloud": "envvars", "project":
{"domain_id": null, "domain_name": "Default", "id": "596cc0c1411e48479dfd54364a055f3c", "name": "mrinal.das@india.nec.com cloud<mailto:mrinal.das@india.nec.com%20cloud>"}, "region_name": "Noida", "zone": "nova"}, "locked": false, "metadata":
{"hostname": "kube01"}, "name": "mrinal1", "networks": {}, "os-extended-volumes:volumes_attached": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}], "personality": null, "power_state": 0, "private_v4": "", "progress": 0, "project_id": "596cc0c1411e48479dfd54364a055f3c", "properties": {"OS-DCF:diskConfig": "MANUAL", "OS-EXT-AZ:availability_zone": "nova", "OS-EXT-SRV-ATTR:host": null, "OS-EXT-SRV-ATTR:hostname": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": null, "OS-EXT-SRV-ATTR:instance_name": null, "OS-EXT-SRV-ATTR:kernel_id": null, "OS-EXT-SRV-ATTR:launch_index": null, "OS-EXT-SRV-ATTR:ramdisk_id": null, "OS-EXT-SRV-ATTR:reservation_id": null, "OS-EXT-SRV-ATTR:root_device_name": null, "OS-EXT-SRV-ATTR:user_data": null, "OS-EXT-STS:power_state": 0, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "error", "OS-SCH-HNT:scheduler_hints": null, "OS-SRV-USG:launched_at": null, "OS-SRV-USG:terminated_at": null, "host_status": null, "locked": false, "os-extended-volumes:volumes_attached": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}], "trusted_image_certificates": null}, "public_v4": "", "public_v6": "", "ramdisk_id": null, "region": "Noida", "reservation_id": null, "root_device_name": null, "scheduler_hints": null, "security_groups": [], "server_groups": null, "status": "ERROR", "tags": [], "task_state": null, "tenant_id": "596cc0c1411e48479dfd54364a055f3c", "terminated_at": null, "trusted_image_certificates": null, "updated": "2019-11-26T05:17:12Z", "user_data": null, "user_id": "1c98d6f5a1cb44efbf0d060ad7911639", "vm_state": "error", "volumes": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}]}}, "item": "1", "msg": "Error in creating the server (no further information available)"}
changed: [localhost] => (item=2)
----Original Message----
From: Help-Desk jira-help-desk@jira.fiware.org
Sent: 26 November 2019 09:25
Cc: Mrinal Das <mrinal.das@india.nec.com<mrinal.das@india.nec.com>>
Subject: [FIWARE-JIRA] (HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 4:54 AM
------------------
Dear Fiware help desk-Team,
We have few queries please find the below:-
1. Instance can't be disabled , only services can be disabled in fiware cloud ?
2. How can your team analyse the problem , please share the logs with us ?
3. What is the root cause of instance creation failure ?
We have occured the issue multiple times , requesting you to share the analysis with us .
Regards,
Mrinal Das
Noida Node Helpdesk - Yesterday 12:33 PM
------------------
The 2 instances were disabled. We have enabled both the instances and both are in active state now.
José Ignacio Carretero Guarde - Yesterday 11:20 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:20 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Your ticket has been assigned to Noida's Team so they can do work on your ticket.
Thank you and best regards,
José Ignacio.
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Today 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
FW External User - Yesterday 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Yesterday 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
FW External User - Today 11:09 AM
------------------
Dear fiware-helpdesk team,
As discussed with Aneel san we have perform the iteration again with higher timeout value of 6 minutes and wait = yes. But creation of one instance out of 2 is again in ERROR state .
So , we are sharing the process of sandbox code with fiware-helpdesk team for better understanding of our scenario.
Synopsis of os_server module in ansible: os_server is ansible module for Create/Delete Compute Instances from OpenStack
Script code:
os_server:
state: present # Should the resource be present or absent
name: "stuff.openstack.vm_name_prefix{{ item }}" #name of instance
key_name: "{{ stuff.openstack.key_name}}" #openstack key name
image: "{{ stuff.openstack.image}}" #openstack image name
wait: yes
timeout: 360
flavor: "{{ stuff.openstack.flavor}}" #openstack flavour
network: "{{ stuff.openstack.private_network}}"
security_groups: "{{ stuff.openstack.security_groups}}" #openstack security groups
boot_from_volume: yes # Should the instance boot from a persistent volume created based on the image given
meta:
hostname: "kube0{{ item }}"
register: openstackvmcreate
with_sequence:
count={{ stuff.openstack.count }}
please find the link for more details : https://docs.ansible.com/ansible/latest/modules/os_server_module.html
Please find the output of nova list
[root@infra-node tasks]# nova list
------------------------------------------------------------------------------------------------------+
------------------------------------------------------------------------------------------------------+
------------------------------------------------------------------------------------------------------+
Please find the cloud configuration settings :
openstack: # openstack group
vm_name_prefix: mrinal # prefix of VM name here (1,2,3... will be added to this based on count)
key_name: sandboxKey # security key-name same as in openstack
flavor: m1.medium # flavor name for instance as in openstack (Minimum ' m1.small ' is required)
private_network: node-int-net-01 # private network name as in openstack
external_network: public-ext-net-01 # external network name as in openstack
image: centos7.5 #supported Images versiona Centos7/ Ubuntu16 (name as your openstack image name)
security_groups: all # name of security group as in openstack
key_path: /tmp/sandbox.pem # path to security key file
count: 2 # number of VMs required
Our Script logs :
TASK [vm-deploy : Deploy an instance assuming image, network(public/private), flavor and key are already present in cloud.] ************
failed: [localhost] (item=1) => {"changed": false, "extra_data": {"server": {"OS-DCF:diskConfig": "MANUAL", "OS-EXT-AZ:availability_zone": "nova", "OS-EXT-SRV-ATTR:host": null, "OS-EXT-SRV-ATTR:hostname": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": null, "OS-EXT-SRV-ATTR:instance_name": null, "OS-EXT-SRV-ATTR:kernel_id": null, "OS-EXT-SRV-ATTR:launch_index": null, "OS-EXT-SRV-ATTR:ramdisk_id": null, "OS-EXT-SRV-ATTR:reservation_id": null, "OS-EXT-SRV-ATTR:root_device_name": null, "OS-EXT-SRV-ATTR:user_data": null, "OS-EXT-STS:power_state": 0, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "error", "OS-SCH-HNT:scheduler_hints": null, "OS-SRV-USG:launched_at": null, "OS-SRV-USG:terminated_at": null, "accessIPv4": "", "accessIPv6": "", "addresses": {}, "adminPass": null, "az": "nova", "block_device_mapping": null, "cloud": "envvars", "config_drive": "", "created": "2019-11-26T05:14:12Z", "created_at": "2019-11-26T05:14:12Z", "description": "mrinal1", "disk_config": "MANUAL", "flavor": {"disk": 40, "ephemeral": 0, "extra_specs": {}, "original_name": "m1.medium", "ram": 4096, "swap": 0, "vcpus": 2}, "has_config_drive": false, "host": null, "hostId": "", "host_id": "", "host_status": null, "hostname": null, "hypervisor_hostname": null, "id": "eb2144eb-7472-4976-a894-a8e291db4f30", "image":
{"id": null}, "instance_name": null, "interface_ip": "", "kernel_id": null, "key_name": "sandboxKey", "launch_index": null, "launched_at": null, "location": {"cloud": "envvars", "project":
{"domain_id": null, "domain_name": "Default", "id": "596cc0c1411e48479dfd54364a055f3c", "name": "mrinal.das@india.nec.com cloud"}, "region_name": "Noida", "zone": "nova"}, "locked": false, "metadata":
{"hostname": "kube01"}, "name": "mrinal1", "networks": {}, "os-extended-volumes:volumes_attached": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}], "personality": null, "power_state": 0, "private_v4": "", "progress": 0, "project_id": "596cc0c1411e48479dfd54364a055f3c", "properties": {"OS-DCF:diskConfig": "MANUAL", "OS-EXT-AZ:availability_zone": "nova", "OS-EXT-SRV-ATTR:host": null, "OS-EXT-SRV-ATTR:hostname": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": null, "OS-EXT-SRV-ATTR:instance_name": null, "OS-EXT-SRV-ATTR:kernel_id": null, "OS-EXT-SRV-ATTR:launch_index": null, "OS-EXT-SRV-ATTR:ramdisk_id": null, "OS-EXT-SRV-ATTR:reservation_id": null, "OS-EXT-SRV-ATTR:root_device_name": null, "OS-EXT-SRV-ATTR:user_data": null, "OS-EXT-STS:power_state": 0, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "error", "OS-SCH-HNT:scheduler_hints": null, "OS-SRV-USG:launched_at": null, "OS-SRV-USG:terminated_at": null, "host_status": null, "locked": false, "os-extended-volumes:volumes_attached": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}], "trusted_image_certificates": null}, "public_v4": "", "public_v6": "", "ramdisk_id": null, "region": "Noida", "reservation_id": null, "root_device_name": null, "scheduler_hints": null, "security_groups": [], "server_groups": null, "status": "ERROR", "tags": [], "task_state": null, "tenant_id": "596cc0c1411e48479dfd54364a055f3c", "terminated_at": null, "trusted_image_certificates": null, "updated": "2019-11-26T05:17:12Z", "user_data": null, "user_id": "1c98d6f5a1cb44efbf0d060ad7911639", "vm_state": "error", "volumes": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}]}}, "item": "1", "msg": "Error in creating the server (no further information available)"}
changed: [localhost] => (item=2)
----Original Message----
From: Help-Desk jira-help-desk@jira.fiware.org
Sent: 26 November 2019 09:25
Cc: Mrinal Das <mrinal.das@india.nec.com>
Subject: [FIWARE-JIRA] (HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 4:54 AM
------------------
Dear Fiware help desk-Team,
We have few queries please find the below:-
1. Instance can't be disabled , only services can be disabled in fiware cloud ?
2. How can your team analyse the problem , please share the logs with us ?
3. What is the root cause of instance creation failure ?
We have occured the issue multiple times , requesting you to share the analysis with us .
Regards,
Mrinal Das
Noida Node Helpdesk - Yesterday 12:33 PM
------------------
The 2 instances were disabled. We have enabled both the instances and both are in active state now.
José Ignacio Carretero Guarde - Yesterday 11:20 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:20 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Your ticket has been assigned to Noida's Team so they can do work on your ticket.
Thank you and best regards,
José Ignacio.
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Today 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
FW External User - Yesterday 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Yesterday 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
FW External User - Today 9:24 AM
------------------
Dear Fiware help desk-Team,
We have few queries please find the below:-
1. Instance can't be disabled , only services can be disabled in fiware cloud ?
2. How can your team analyse the problem , please share the logs with us ?
3. What is the root cause of instance creation failure ?
We have occured the issue multiple times , requesting you to share the analysis with us .
Regards,
Mrinal Das
Noida Node Helpdesk - Yesterday 5:03 PM
------------------
The 2 instances were disabled. We have enabled both the instances and both are in active state now.
José Ignacio Carretero Guarde - Yesterday 3:50 PM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:20 AM
- To: mrinal.das@india.nec.com
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Your ticket has been assigned to Noida's Team so they can do work on your ticket.
Thank you and best regards,
José Ignacio.
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Today 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
FW External User - Yesterday 3:47 PM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Yesterday 3:39 PM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Noida Node Helpdesk - Today 12:22 PM
------------------
Could you perform instantiation of instances with having gap of some time (e.g. of 5-10 seconds) between two instances, instead of launching instances in parallel.
FW External User - Today 11:28 AM
------------------
Adding Screenshots for further details.
From: Mrinal Das
Sent: 26 November 2019 11:08
To: 'jira-help-desk@jira.fiware.org' <jira-help-desk@jira.fiware.org>
Cc: Ajay Yadav <ajay.yadav@india.nec.com>; Anand Sahu <anand.sahu@india.nec.com>; Ravinder Kumar <ravinder.kumar@india.nec.com>
Subject: RE: [FIWARE-JIRA] (HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud
Dear fiware-helpdesk team,
As discussed with Aneel san we have perform the iteration again with higher timeout value of 6 minutes and wait = yes. But creation of one instance out of 2 is again in ERROR state .
So , we are sharing the process of sandbox code with fiware-helpdesk team for better understanding of our scenario.
Synopsis of os_server module in ansible: os_server is ansible module for Create/Delete Compute Instances from OpenStack
Script code:
os_server:
state: present # Should the resource be present or absent
name: "stuff.openstack.vm_name_prefix{{ item }}" #name of instance
key_name: "{{ stuff.openstack.key_name}}" #openstack key name
image: "{{ stuff.openstack.image}}" #openstack image name
wait: yes
timeout: 360
flavor: "{{ stuff.openstack.flavor}}" #openstack flavour
network: "{{ stuff.openstack.private_network}}"
security_groups: "{{ stuff.openstack.security_groups}}" #openstack security groups
boot_from_volume: yes # Should the instance boot from a persistent volume created based on the image given
meta:
hostname: "kube0{{ item }}"
register: openstackvmcreate
with_sequence:
count={{ stuff.openstack.count }}
please find the link for more details : https://docs.ansible.com/ansible/latest/modules/os_server_module.html
Please find the output of nova list
[root@infra-node tasks]# nova list
------------------------------------------------------------------------------------------------------+
------------------------------------------------------------------------------------------------------+
------------------------------------------------------------------------------------------------------+
Please find the cloud configuration settings :
openstack: # openstack group
vm_name_prefix: mrinal # prefix of VM name here (1,2,3... will be added to this based on count)
key_name: sandboxKey # security key-name same as in openstack
flavor: m1.medium # flavor name for instance as in openstack (Minimum ' m1.small ' is required)
private_network: node-int-net-01 # private network name as in openstack
external_network: public-ext-net-01 # external network name as in openstack
image: centos7.5 #supported Images versiona Centos7/ Ubuntu16 (name as your openstack image name)
security_groups: all # name of security group as in openstack
key_path: /tmp/sandbox.pem # path to security key file
count: 2 # number of VMs required
Our Script logs :
TASK [vm-deploy : Deploy an instance assuming image, network(public/private), flavor and key are already present in cloud.] ************
failed: [localhost] (item=1) => {"changed": false, "extra_data": {"server": {"OS-DCF:diskConfig": "MANUAL", "OS-EXT-AZ:availability_zone": "nova", "OS-EXT-SRV-ATTR:host": null, "OS-EXT-SRV-ATTR:hostname": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": null, "OS-EXT-SRV-ATTR:instance_name": null, "OS-EXT-SRV-ATTR:kernel_id": null, "OS-EXT-SRV-ATTR:launch_index": null, "OS-EXT-SRV-ATTR:ramdisk_id": null, "OS-EXT-SRV-ATTR:reservation_id": null, "OS-EXT-SRV-ATTR:root_device_name": null, "OS-EXT-SRV-ATTR:user_data": null, "OS-EXT-STS:power_state": 0, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "error", "OS-SCH-HNT:scheduler_hints": null, "OS-SRV-USG:launched_at": null, "OS-SRV-USG:terminated_at": null, "accessIPv4": "", "accessIPv6": "", "addresses": {}, "adminPass": null, "az": "nova", "block_device_mapping": null, "cloud": "envvars", "config_drive": "", "created": "2019-11-26T05:14:12Z", "created_at": "2019-11-26T05:14:12Z", "description": "mrinal1", "disk_config": "MANUAL", "flavor": {"disk": 40, "ephemeral": 0, "extra_specs": {}, "original_name": "m1.medium", "ram": 4096, "swap": 0, "vcpus": 2}, "has_config_drive": false, "host": null, "hostId": "", "host_id": "", "host_status": null, "hostname": null, "hypervisor_hostname": null, "id": "eb2144eb-7472-4976-a894-a8e291db4f30", "image":
{"id": null}, "instance_name": null, "interface_ip": "", "kernel_id": null, "key_name": "sandboxKey", "launch_index": null, "launched_at": null, "location": {"cloud": "envvars", "project":
{"domain_id": null, "domain_name": "Default", "id": "596cc0c1411e48479dfd54364a055f3c", "name": "mrinal.das@india.nec.com cloud<mailto:mrinal.das@india.nec.com%20cloud>"}, "region_name": "Noida", "zone": "nova"}, "locked": false, "metadata":
{"hostname": "kube01"}, "name": "mrinal1", "networks": {}, "os-extended-volumes:volumes_attached": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}], "personality": null, "power_state": 0, "private_v4": "", "progress": 0, "project_id": "596cc0c1411e48479dfd54364a055f3c", "properties": {"OS-DCF:diskConfig": "MANUAL", "OS-EXT-AZ:availability_zone": "nova", "OS-EXT-SRV-ATTR:host": null, "OS-EXT-SRV-ATTR:hostname": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": null, "OS-EXT-SRV-ATTR:instance_name": null, "OS-EXT-SRV-ATTR:kernel_id": null, "OS-EXT-SRV-ATTR:launch_index": null, "OS-EXT-SRV-ATTR:ramdisk_id": null, "OS-EXT-SRV-ATTR:reservation_id": null, "OS-EXT-SRV-ATTR:root_device_name": null, "OS-EXT-SRV-ATTR:user_data": null, "OS-EXT-STS:power_state": 0, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "error", "OS-SCH-HNT:scheduler_hints": null, "OS-SRV-USG:launched_at": null, "OS-SRV-USG:terminated_at": null, "host_status": null, "locked": false, "os-extended-volumes:volumes_attached": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}], "trusted_image_certificates": null}, "public_v4": "", "public_v6": "", "ramdisk_id": null, "region": "Noida", "reservation_id": null, "root_device_name": null, "scheduler_hints": null, "security_groups": [], "server_groups": null, "status": "ERROR", "tags": [], "task_state": null, "tenant_id": "596cc0c1411e48479dfd54364a055f3c", "terminated_at": null, "trusted_image_certificates": null, "updated": "2019-11-26T05:17:12Z", "user_data": null, "user_id": "1c98d6f5a1cb44efbf0d060ad7911639", "vm_state": "error", "volumes": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}]}}, "item": "1", "msg": "Error in creating the server (no further information available)"}
changed: [localhost] => (item=2)
----Original Message----
From: Help-Desk jira-help-desk@jira.fiware.org
Sent: 26 November 2019 09:25
Cc: Mrinal Das <mrinal.das@india.nec.com<mrinal.das@india.nec.com>>
Subject: [FIWARE-JIRA] (HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 4:54 AM
------------------
Dear Fiware help desk-Team,
We have few queries please find the below:-
1. Instance can't be disabled , only services can be disabled in fiware cloud ?
2. How can your team analyse the problem , please share the logs with us ?
3. What is the root cause of instance creation failure ?
We have occured the issue multiple times , requesting you to share the analysis with us .
Regards,
Mrinal Das
Noida Node Helpdesk - Yesterday 12:33 PM
------------------
The 2 instances were disabled. We have enabled both the instances and both are in active state now.
José Ignacio Carretero Guarde - Yesterday 11:20 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:20 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Your ticket has been assigned to Noida's Team so they can do work on your ticket.
Thank you and best regards,
José Ignacio.
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Today 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
FW External User - Yesterday 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Yesterday 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
FW External User - Today 11:09 AM
------------------
Dear fiware-helpdesk team,
As discussed with Aneel san we have perform the iteration again with higher timeout value of 6 minutes and wait = yes. But creation of one instance out of 2 is again in ERROR state .
So , we are sharing the process of sandbox code with fiware-helpdesk team for better understanding of our scenario.
Synopsis of os_server module in ansible: os_server is ansible module for Create/Delete Compute Instances from OpenStack
Script code:
os_server:
state: present # Should the resource be present or absent
name: "stuff.openstack.vm_name_prefix{{ item }}" #name of instance
key_name: "{{ stuff.openstack.key_name}}" #openstack key name
image: "{{ stuff.openstack.image}}" #openstack image name
wait: yes
timeout: 360
flavor: "{{ stuff.openstack.flavor}}" #openstack flavour
network: "{{ stuff.openstack.private_network}}"
security_groups: "{{ stuff.openstack.security_groups}}" #openstack security groups
boot_from_volume: yes # Should the instance boot from a persistent volume created based on the image given
meta:
hostname: "kube0{{ item }}"
register: openstackvmcreate
with_sequence:
count={{ stuff.openstack.count }}
please find the link for more details : https://docs.ansible.com/ansible/latest/modules/os_server_module.html
Please find the output of nova list
[root@infra-node tasks]# nova list
------------------------------------------------------------------------------------------------------+
------------------------------------------------------------------------------------------------------+
------------------------------------------------------------------------------------------------------+
Please find the cloud configuration settings :
openstack: # openstack group
vm_name_prefix: mrinal # prefix of VM name here (1,2,3... will be added to this based on count)
key_name: sandboxKey # security key-name same as in openstack
flavor: m1.medium # flavor name for instance as in openstack (Minimum ' m1.small ' is required)
private_network: node-int-net-01 # private network name as in openstack
external_network: public-ext-net-01 # external network name as in openstack
image: centos7.5 #supported Images versiona Centos7/ Ubuntu16 (name as your openstack image name)
security_groups: all # name of security group as in openstack
key_path: /tmp/sandbox.pem # path to security key file
count: 2 # number of VMs required
Our Script logs :
TASK [vm-deploy : Deploy an instance assuming image, network(public/private), flavor and key are already present in cloud.] ************
failed: [localhost] (item=1) => {"changed": false, "extra_data": {"server": {"OS-DCF:diskConfig": "MANUAL", "OS-EXT-AZ:availability_zone": "nova", "OS-EXT-SRV-ATTR:host": null, "OS-EXT-SRV-ATTR:hostname": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": null, "OS-EXT-SRV-ATTR:instance_name": null, "OS-EXT-SRV-ATTR:kernel_id": null, "OS-EXT-SRV-ATTR:launch_index": null, "OS-EXT-SRV-ATTR:ramdisk_id": null, "OS-EXT-SRV-ATTR:reservation_id": null, "OS-EXT-SRV-ATTR:root_device_name": null, "OS-EXT-SRV-ATTR:user_data": null, "OS-EXT-STS:power_state": 0, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "error", "OS-SCH-HNT:scheduler_hints": null, "OS-SRV-USG:launched_at": null, "OS-SRV-USG:terminated_at": null, "accessIPv4": "", "accessIPv6": "", "addresses": {}, "adminPass": null, "az": "nova", "block_device_mapping": null, "cloud": "envvars", "config_drive": "", "created": "2019-11-26T05:14:12Z", "created_at": "2019-11-26T05:14:12Z", "description": "mrinal1", "disk_config": "MANUAL", "flavor": {"disk": 40, "ephemeral": 0, "extra_specs": {}, "original_name": "m1.medium", "ram": 4096, "swap": 0, "vcpus": 2}, "has_config_drive": false, "host": null, "hostId": "", "host_id": "", "host_status": null, "hostname": null, "hypervisor_hostname": null, "id": "eb2144eb-7472-4976-a894-a8e291db4f30", "image":
{"id": null}, "instance_name": null, "interface_ip": "", "kernel_id": null, "key_name": "sandboxKey", "launch_index": null, "launched_at": null, "location": {"cloud": "envvars", "project":
{"domain_id": null, "domain_name": "Default", "id": "596cc0c1411e48479dfd54364a055f3c", "name": "mrinal.das@india.nec.com cloud"}, "region_name": "Noida", "zone": "nova"}, "locked": false, "metadata":
{"hostname": "kube01"}, "name": "mrinal1", "networks": {}, "os-extended-volumes:volumes_attached": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}], "personality": null, "power_state": 0, "private_v4": "", "progress": 0, "project_id": "596cc0c1411e48479dfd54364a055f3c", "properties": {"OS-DCF:diskConfig": "MANUAL", "OS-EXT-AZ:availability_zone": "nova", "OS-EXT-SRV-ATTR:host": null, "OS-EXT-SRV-ATTR:hostname": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": null, "OS-EXT-SRV-ATTR:instance_name": null, "OS-EXT-SRV-ATTR:kernel_id": null, "OS-EXT-SRV-ATTR:launch_index": null, "OS-EXT-SRV-ATTR:ramdisk_id": null, "OS-EXT-SRV-ATTR:reservation_id": null, "OS-EXT-SRV-ATTR:root_device_name": null, "OS-EXT-SRV-ATTR:user_data": null, "OS-EXT-STS:power_state": 0, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "error", "OS-SCH-HNT:scheduler_hints": null, "OS-SRV-USG:launched_at": null, "OS-SRV-USG:terminated_at": null, "host_status": null, "locked": false, "os-extended-volumes:volumes_attached": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}], "trusted_image_certificates": null}, "public_v4": "", "public_v6": "", "ramdisk_id": null, "region": "Noida", "reservation_id": null, "root_device_name": null, "scheduler_hints": null, "security_groups": [], "server_groups": null, "status": "ERROR", "tags": [], "task_state": null, "tenant_id": "596cc0c1411e48479dfd54364a055f3c", "terminated_at": null, "trusted_image_certificates": null, "updated": "2019-11-26T05:17:12Z", "user_data": null, "user_id": "1c98d6f5a1cb44efbf0d060ad7911639", "vm_state": "error", "volumes": [
{"delete_on_termination": false, "id": "b6f95a8f-4fa5-4c55-803a-881f6c6567a9"}]}}, "item": "1", "msg": "Error in creating the server (no further information available)"}
changed: [localhost] => (item=2)
----Original Message----
From: Help-Desk jira-help-desk@jira.fiware.org
Sent: 26 November 2019 09:25
Cc: Mrinal Das <mrinal.das@india.nec.com>
Subject: [FIWARE-JIRA] (HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 4:54 AM
------------------
Dear Fiware help desk-Team,
We have few queries please find the below:-
1. Instance can't be disabled , only services can be disabled in fiware cloud ?
2. How can your team analyse the problem , please share the logs with us ?
3. What is the root cause of instance creation failure ?
We have occured the issue multiple times , requesting you to share the analysis with us .
Regards,
Mrinal Das
Noida Node Helpdesk - Yesterday 12:33 PM
------------------
The 2 instances were disabled. We have enabled both the instances and both are in active state now.
José Ignacio Carretero Guarde - Yesterday 11:20 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:20 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Your ticket has been assigned to Noida's Team so they can do work on your ticket.
Thank you and best regards,
José Ignacio.
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Today 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
FW External User - Yesterday 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Yesterday 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com<mrinal.das@india.nec.com>
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com<mailto:mrinal.das@india.nec.com>>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
FW External User - Today 9:24 AM
------------------
Dear Fiware help desk-Team,
We have few queries please find the below:-
1. Instance can't be disabled , only services can be disabled in fiware cloud ?
2. How can your team analyse the problem , please share the logs with us ?
3. What is the root cause of instance creation failure ?
We have occured the issue multiple times , requesting you to share the analysis with us .
Regards,
Mrinal Das
Noida Node Helpdesk - Yesterday 5:03 PM
------------------
The 2 instances were disabled. We have enabled both the instances and both are in active state now.
José Ignacio Carretero Guarde - Yesterday 3:50 PM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:20 AM
- To: mrinal.das@india.nec.com
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Your ticket has been assigned to Noida's Team so they can do work on your ticket.
Thank you and best regards,
José Ignacio.
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
FW External User - Today 11:17 AM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Today 11:09 AM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
FW External User - Yesterday 3:47 PM
------------------
Dear José Ignacio,
I am basic user of fiware cloud .
So, requesting you to please analyse the logs .
Regards,
Mrinal Das
José Ignacio Carretero Guarde - Yesterday 3:39 PM
------------------
The issue has been emailed:
- Time sent: 25/Nov/19 11:09 AM
- To: mrinal.das@india.nec.com
- with subject: *(
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *
Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
------------------------
Issue id: HELP-16366
Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
A user in normal openstack knows the keystone endpoint which he/she mentions in Rc files to get authenticated but in case of Fiware Lab, only admin knows the auth_url and normal user isn't provided with that information. There are different keystone endpoints for different regions. A normal user can know the tenant name, project name, username, password. How could a normal Noida user know the endpoint he needs to authenticate to? Suppose if you have an account on Lannion4 Node do you think you can authenticate with the same auth_url (Fiware cloud portal) there as well ?
You cannot directly use keystone auth url configurations without permission from Fi-Lab. Try to understand you have breached the security rules of Fi-Lab of which you already understand.
Logs analysis is not a major concern for us. Our major concern is how a normal user(you) accessed Fi-Lab with unauthorized usage of keystone configurations(auth_url)?
We are analysing the logs and will let you know once our investigation is done.
This ticket is related to some external scripts being used by the user to lauch instances. We provide infra support but do not provide support at the development level. Hence we are closing this ticket.
The issue has been emailed:
HELP-16366) [Fiware-lab-help] Instance creation failed on fiware cloud *Dear Mrinal,
I guess you created 2 VMs using Volumes to do so. The volumes were created but the VMs didn't started. Maybe, if you start new instances from the volumes created your VMs will start.
This might be due to a non high enough timeout for the volumes to be ready before the instance (nova.conf - block_device_allocate_retries and block_device_allocate_retries_interval).
Best regards,
José Ignacio
From FIWARE JIRA - Main Help Desk ----
-------------------------------------------------------------------------------
Comments:
------------------------
Issue id:
HELP-16366Description:
Dear Fiware Lab Team,
Thanks for your continuous support!!!
Please check the issue on urgent basis and Let us know.
Description of Issue:
We have launched two instances mrinal1,2 on fiware Lab. But instances failed to come in "Active" State. Details are below:
Instance name: mrinal1
Instance ID : 43405c53-e721-4e27-95cd-4790d04856a2
Status: Error
Message: Build of instance 43405c53-e721-4e27-95cd-4790d04856a2 aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-babc2fa5-3d19-40fb-be2d-cdbea9b0c19b)
Instance name: mrinal2
Instance ID : 517ea6b6-f694-40b4-9b31-b576127a6faf
Status: Error
Message: Build of instance 517ea6b6-f694-40b4-9b31-b576127a6faf aborted: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-f4a61d33-b828-45a2-9d1b-6a70c240e0c3)
For further Details PFA.
Regards
Mrinal Das
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
To unsubscribe from Fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Mrinal Das <mrinal.das@india.nec.com>]
FIWARE Chapter:
FIWARE GEri:
Status: Open
---------------------
This email was generated by FIWARE JIRA following an email received into the Main Help Desk.