Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-4087

Improve error handling and reporting for EC2 ebs snapshot / volume procedures (scripts)

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      The following has been observed:

      The EA does not start up if shell scripts fail to run successfully. So far this has happened in

      /opt/bamboo-elastic-agent/bin/restoreSnapshot.sh and /opt/bamboo-elastic-agent/bin/setAwsEnv.sh

      can be failing on getting the availability zone using curl. This is stopping the agent from starting successfully.
      The response from amazon is

      <?xml version="1.0" encoding="iso-8859-1"?> 
      <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
      <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>404 - Not Found</title> 
      </head> 
      <body> <h1>404 - Not Found</h1> </body> </html>

      and the agent is not started up. The instance remains idle - no warning or error messages are sent to the server.
      then restoreSnapshot.sh hangs

      1     0  1122  1114  23   0   2648   484 wait   S    ?          0:00 /bin/sh /opt/bamboo-elastic-agent/bin/restoreSnapshot.sh
      0     0  1123  1122  24   0   2640  1136 wait   S    ?          0:00 bash /usr/local/ec2/ec2-api-tools/bin/ec2-create-volume --snapshot snap-d64885bf --availability-zone
      

            [BAM-4087] Improve error handling and reporting for EC2 ebs snapshot / volume procedures (scripts)

            Ulrich Kuhnhardt [Atlassian] added a comment - - edited yeah - paul is right https://support.atlassian.com/browse/BSP-1910?focusedCommentId=556447&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_556447 http://jira.atlassian.com/browse/BAM-4037

            Hi,

            The EC2 team is currently working to resolve an issue that is resulting in "404 - Not Found" when performing the metadata requests for availability-zone in the 'us-east-1d' zone only. We'll provide an update when this is corrected.

            However as a work around, you may wish to restrict your instance launches to the other three availability zones.

            Best regards,

            Ramkumar
            Amazon Web Services
            =======================================

            Ulrich Kuhnhardt [Atlassian] added a comment - Hi, The EC2 team is currently working to resolve an issue that is resulting in "404 - Not Found" when performing the metadata requests for availability-zone in the 'us-east-1d' zone only. We'll provide an update when this is corrected. However as a work around, you may wish to restrict your instance launches to the other three availability zones. Best regards, Ramkumar Amazon Web Services =======================================

            As requested by Ulirch in https://support.atlassian.com/browse/BSP-1910, I've attached the test.pcap file from running the command: curl http://169.254.169.254/latest/meta-data/placement/availability-zone.

            Dylan Hansen added a comment - As requested by Ulirch in https://support.atlassian.com/browse/BSP-1910 , I've attached the test.pcap file from running the command: curl http://169.254.169.254/latest/meta-data/placement/availability-zone .

              kbrazulewicz Krystian Brazulewicz
              ukuhnhardt Ulrich Kuhnhardt [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2h
                  2h