I have set up a ASE3 environment to which I am deploying my app service through azure-devops yaml-pipeline. I have an agent-pool on a windows-scaleset that i have created in the same vNet as the ASE3 but on a different subnet.
When the pipeline is excuted it throws the following error in the deploy-task:
##[error]Failed to deploy web package to App Service.
##[error]Error: Error: Failed to deploy web package to App Service. Error: connect ETIMEDOUT xx.xx.xx.4:443
##[warning]Error: Failed to update deployment history. Error: Error: connect ETIMEDOUT xx.xx.xx.4:443
Any help on this please?
We solved this issue by checking the routing table. It seemed that the subnet where build-agent is hosted had next-hop to outside the vNet which made ASEs ip-address unknown to the firewall. by changing that could the agent upload the zip-packege.
Related
I am using openstack container to enable integration testing against swift
The container used is : https://hub.docker.com/r/jeantil/openstack-swift-keystone-docker/
And the steps followed are : https://github.com/jeantil/openstack-swift-keystone-docker
The configuration is working fine on local and open internet(concourse pipeline job)
But when I am using the same in concourse pipeline job on INTRANET, I am getting the below error:
Failed to discover available identity versions when contacting http://127.0.0.1:35357/v3. Attempting to parse version from URL.
Unauthorized (HTTP 401)
I am getting this error while creating a new service or even loading user lists:
Example:
openstack endpoint create --region RegionOne object-store internal http://127.0.0.1:8080/v1/KEY_%\(tenant_id\)s
openstack endpoint create --region RegionOne object-store admin http://127.0.0.1:8080/v1
openstack user list
Is it due to some proxy related configuration, because everything is working fine if I am running this concourse job on internet
I tried multiple approaches and at the end I was able to solve the issue.
Include ENV NO_PROXY=localhost in the dockerfile so that the proxy configurations are removed for this config
When I try to run TerraformInstaller to install terraform in azure pipelines, I get the following error message.
##[error]Error: Failed to download Terraform from url https://releases.hashicorp.com/terraform/1.2.4/terraform_1.2.4_linux_amd64.zip. Error Error: self signed certificate in certificate chain
When I browse the link in server where self-hosted agent is installed, I am able to get to the link fine and download the zip file but only getting this error when I am running the pipeline in Azure DevOps. Firewall port 443 is obviously open and I think this error has to do with cert not being placed in the correct location? Do I need to configure self-hosted agent with cert?
I'm trying to deploy an app on IBM Cloud (Bluemix) from a Github repository (https://github.com/IBM/watson-vehicle-damage-analyzer).
When I deploy the app I choose London as location. The project try to deploy but it stops with this error:
Server error, status code: 502, error code: 10001, message: Service broker error: No matching deployments for the given plan_id.
Can somebody explain me what this error means? I have a paid account on IBM Cloud.
Here is the full log of my error:
Preparing to start the job...
Preparing the build artifacts...
cf login -a "https://api.eu-gb.bluemix.net" -u apikey -p "****" -o "xxxxxxxx#xxxxxxxx.com" -s "dev"
API endpoint: https://api.eu-gb.bluemix.net
Authenticating...
OK
Targeted org xxxxxxxxx#xxxxxxx.com
Targeted space dev
API endpoint: https://api.eu-gb.bluemix.net (API version: 2.106.0)
User: gabriel.cuesta#mkdautomotive.com
Org: gabriel.cuesta#mkdautomotive.com
Space: dev
Creating service instance wvda-visual-recognition in org gabriel.cuesta#mkdautomotive.com / space dev as gabriel.cuesta#mkdautomotive.com...
FAILED
Server error, status code: 502, error code: 10001, message: Service broker error: No matching deployments for the given plan_id.
Finished: FAILED
Thanks,
I see that in the manifest.yml file, it's creating a Watson VR service lite plan but as per the pricing on the website here, Watson VR with the lite plan is available only in us-south (Dallas) region.
You can check the same here as well - https://console.bluemix.net/catalog/services/visual-recognition
I'm facing issues when I deploy my service fabric app to cluster. Deployment completed with below error.
Error event: SourceId='System.Hosting', Property='Activation:1.0'.
There was an error during activation.Failed to configure certificate
permissions. Error FABRIC_E_CERTIFICATE_NOT_FOUND.
This certificate is part of config package. However when I login to VM, I don't see the package deployed with config folder. I checked that package which is built locally, it looks correct with Config folder and certificate. But when this package is deployed to cluster then Config pkg is missing on VM and hence service activation fails with Certificate not found error.
All the details can be found in the issue I have logged on GitHub.
Snippet from ApplicationManifest which refers to certificate:
<ContainerHostPolicies CodePackageRef="Code">
<CertificateRef Name="SecretsCert" DataPackageRef="Config" DataPackageVersion="Version" RelativePath="PFX PATH INSIDE CONFIG" IsPasswordEncrypted="true" Password="NOTMYPASSWORD"/>
<RepositoryCredentials AccountName="Container Registry Name" Password="[Registry Key]" PasswordEncrypted="true" />
</ContainerHostPolicies>
We've been successfully using TeamCity and Octopus on a single machine, and now we have added a new build agent due to growing number of simultaneous builds. I have set up a new Octopus Tentacle and verified that Tentacle is reachable from the Octopus server in Listener role. However,any build that uses Octopack fails when executed on the new TeamCity agent. Here is an extract from the build log:
Running command: octo.exe create-release --server
servername:8443 --apikey SECRET --project NRK Bridge (Legacy)
--enableservicemessages --version 0.0.0.662 --deployto Dev --waitfordeployment --package=NRK.Bridge.Web:0.0.0.662 --packageversion=0.0.0.662
[12:06:02]Creating Octopus Deploy release
[12:06:02]Octopus Deploy Command Line Tool, version 2.0.8.22
[12:06:03]Handshaking with Octopus server: servername:8443
[12:06:06]The following certificate errors were
encountered when establishing the HTTPS connection to the server:
RemoteCertificateChainErrors
[12:06:06]Certificate subject name: CN=servername
[12:06:06]Certificate thumbprint: 79C26(...)
[12:06:07]The following certificate errors were encountered when
establishing the HTTPS connection to the server:
RemoteCertificateChainErrors
[12:06:07]Certificate subject name: CN=servername
[12:06:07]Certificate thumbprint: 79C26(...)
[12:06:08]The following certificate errors were encountered when
establishing the HTTPS connection to the server:
RemoteCertificateChainErrors
What I noticed is that the certificate thumbprint in the build log is different from thumbprints shown in Octopus server machine page. I tried to generate a new API key and re-register a Tentacle. Am I overlooking something here?
Did you copy the Api key into Team City? The api key is different to thumb prints. Api Key can be found in Octopus Admin section, under users tab.