Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-3368

FIWARE.Request.Tech.Cloud.PaaSManager.EnvironmentNoValid

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Blocker
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-TECH-HELP
        • Labels:
          None
        • HD-Chapter:
          Cloud
        • HD-Enabler:
          Pegasus

          Description

          There is already a ticket open https://jira.fiware.org/browse/BEAR-10 but I'm not able to reassign it to you. See attachment.

          I'm wondering why there is no project in Jira for PaaS or Blueprints?

          The Blueprint catalog is now available.
          If I try to launch a Blueprint, from a clone of the catalog, I get the following error:
          Success: Blueprint Instance CB status.
          Description: Create environment CB
          Status: ERROR
          Error: The Environment CB is not in the System
          It seems to be a general issue, because I tried another template which was also failing with the same error.

          1. CB-VNC.JPG
            53 kB
          2. CloneofTemplate.JPG
            38 kB
          3. DeploymentError.JPG
            86 kB
          4. Jira_reassignment_issue.JPG
            113 kB
          5. Status_Installing.JPG
            98 kB

            Activity

            Ascending order - Click to sort in descending order
            14 older comments
            Hide
            Permalink
            henar Henar Muñoz added a comment -

            in addition I will need a floating ip to be able to access and check it.

            Show
            henar Henar Muñoz added a comment - in addition I will need a floating ip to be able to access and check it.
            Hide
            Permalink
            BerlinSupportTeam Berlin Node Helpdesk added a comment -

            Unfortunately we're not allowed to give third parties SSH access our servers. Please let us know the log files you're interested in and we'll provide the required information asap. We could also have together a live debugging session via GotoMeeting or Skype.

            Please provide your tenant ID and I'll assign a floating IP.

            Show
            BerlinSupportTeam Berlin Node Helpdesk added a comment - Unfortunately we're not allowed to give third parties SSH access our servers. Please let us know the log files you're interested in and we'll provide the required information asap. We could also have together a live debugging session via GotoMeeting or Skype. Please provide your tenant ID and I'll assign a floating IP.
            Hide
            Permalink
            henar Henar Muñoz added a comment -

            Hi

            My skype is henarmunoz. My ID is 00000000000000000000000000000081
            Regards,
            Henar

            Show
            henar Henar Muñoz added a comment - Hi My skype is henarmunoz. My ID is 00000000000000000000000000000081 Regards, Henar
            Hide
            Permalink
            BerlinSupportTeam Berlin Node Helpdesk added a comment -

            Hi Henar, I gave you an additional public IP (193.175.132.57), please delete it if it is not needed anymore.

            Show
            BerlinSupportTeam Berlin Node Helpdesk added a comment - Hi Henar, I gave you an additional public IP (193.175.132.57), please delete it if it is not needed anymore.
            Hide
            Permalink
            BerlinSupportTeam Berlin Node Helpdesk added a comment -

            Hi Henar, yesterday I was able to solve the issue. I had to reduce the MTU size of eth0 on the VM that was launched through Blueprint. We had already other connectivity issues wrt MTU size and the reason seem that we are using GRE tunneling. Now I've configured the dhcp-option-force=26,1456 for the dnsmasq. This will set the MTU size of the interfaces from new VMs to this value and this seems to solve the connectivity issues.

            Thanks again for your support.

            Show
            BerlinSupportTeam Berlin Node Helpdesk added a comment - Hi Henar, yesterday I was able to solve the issue. I had to reduce the MTU size of eth0 on the VM that was launched through Blueprint. We had already other connectivity issues wrt MTU size and the reason seem that we are using GRE tunneling. Now I've configured the dhcp-option-force=26,1456 for the dnsmasq. This will set the MTU size of the interfaces from new VMs to this value and this seems to solve the connectivity issues. Thanks again for your support.

              People

              • Assignee:
                henar Henar Muñoz
                Reporter:
                BerlinSupportTeam Berlin Node Helpdesk
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: