How do you proceed when you received error 'name_taken' when trying to create a Shared Slack Channel?
There may be different reasons why such an error is encountered. As an example, an old Slack channel was previously created with the same name.
Run a search in Slack to see if the name already exists
Create a Jira and assign to Ofir Cohen to assist with the issue
Connect the Jira ticket with the correct engineering team “team_nordia”
Related
Hi I'm currently trying to deploy Watson Studio Lite but it will not allow me to do this without a resource group. And when I'm trying to create a resource group I do not have permission to do so.
Could someone please advise? IM taking the IBM data science certification online with Coursea and their instructions are either dated or not specific to my issue.
when creating a new IBM Cloud account, a default resource group should be created automatically. Unfortunately you will not be able to create another one without upgrading to a paid account. There are two options:
You can chat with support in the support center.
You can create a new account with a different email address.
I have followed Googles descriptions to the letter, but when I try to download a report from the bucket using the service account I get an error saying .... does not have storage.objects.get access to the Google Cloud Storage object..
From what I can tell the pubsite_prod_rev_xxx bucket is managed by Google Play and adding the service account should (at least in theory) grant access to it.
Has anyone been able to get this working?
I guess permissions are only updated when a new report is generated because it works now. So if you have this problem you might just have to wait a day.
For future reference, in one of my cases it took more than a day for permissions to be applied. I found out later that no files were created on bucket that day, so although I haven't found any source to Kimble's answer, that may indeed be the reason.
I want to develop .net core desktop client application to connect bot service direct line. for that I am following this document. But I couldn't make it work. Here is way to confirm that it has been properly configured. the web page should show output like below in case everything went fine.
{"v":"123","k":true,"ib":true,"ob":true,"initialized":true}
but in my case I am getting output like below:
{"v":"1.0.0.0.55fa54091a1e3b168628d4000ee2b06a88bbc2ac","k":true,"ib":false,"ob":false,"initialized":true}
where "ib" and "ob" values are false for some reason. I found this and this issue reported on github but there is no conclusion.
any suggestion is greatly appreciated. Thanks.
Troubleshooting guid has been added to the document. verified steps below and getting proper results now:
Double check the code for using named pipes has been added to the
bot.
Confirm the bot is able to start up and run at all. Useful
tools are Test in WebChat, connecting an additional channel, remote
debugging, or logging.
Restart the entire Azure App Service the bot
is hosted within, to ensure a clean start up of all processes.
I followed Microsoft Docs on how to setup the bot project: https://learn.microsoft.com/en-us/azure/bot-service/bot-service-channel-directline-extension-net-bot?view=azure-bot-service-4.0
I did a simple echo bot project and followed the sample code in Startup.cs Configure method.
Last thing I did is to resolve an issue HTTP 500.34 when I access the /.bot as described.
You need to add: <AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel> in .csproj after <TargetFramework>netcoreapp3.1</TargetFramework>
In description of Google Cloud Build app on GitHub here https://github.com/marketplace/google-cloud-build every build seems to be identifiable by name:
Cloud Build Triggers With Names
In my current set up, however, every build is displayed by id, which is not very useful:
Cloud Build Triggers with IDs
Is there something I am not doing to make it work as expected?
When I think about Cloud Builds, I understand that every individual build has a unique identifier. For me, this is what I would want to see in a report of a build being triggered. Given a Cloud Build ID, I can then use that for visibility into the underlying process that unique instance of the build caused. I can see all the steps and the outcome of each of them. I couldn't imagine wanting anything else than a build identifier being reported to me as a result of a Cloud Build being performed.
References:
Viewing build results
I posted the original issue in the issuetracker in January 2020,
This is not since fixed and identified real names since August 17th. You do have to reclick on the new names if you have made any previous hash based ones required steps in your build.
For any triggers created prior to August 2020, data sharing needs to be enabled for this to work, As documented here:
https://cloud.google.com/cloud-build/docs/automating-builds/create-github-app-triggers#data_sharing
You need to go in the Settings -> Data Sharing section of cloud build and enable it
In some cases you might get a Failed to enable trigger data sharing error when trying to do this, if so you might want to try
1 - Disable any required checks you have in github related to cloud build
2 - Try doing it using chrome without any ad blocker, for me it wasn't working using Brave browser but worked with chrome
This will allow github to show the trigger name instead of an id in the pull request checks
I'm trying to setup continuous deployment via the Aure Portal.
When doing this via the VSTS account (let's call it "VSTS Account A") which is owned by the same account owner as Azure, everything works fine.
In this case I'm trying to configure continuous deploymenet from source code held in another VSTS account (let's go with Account B).
The Azure account owner is not the Account B owner but is an admin (member of Organization Administrators) for Account B. The owner is also listed explicitly as a member of at least one project within Account B.
The problem is that when it commes to configuring "Deployment source" within the app service section, Account B is not listed as an option to choose from.
I've followed various links (e.g. part 4 of this page) about linking the VSTS account with an Azure account but still no joy. There are a couple of problems here:
The Azure classic portal has a New button within the Visual Studio Team Services section but when I choose Link To Existing, I get the following message:
Make sure you’re the account owner. If you are, maybe your account is
linked to another Azure subscription or connected to another Azure
Active Directory
Account B is not linked to another Azure Subscription or Azure AD.
The new portal doesn't even have an option to attempt to link a different account, plus the menu link says "Team Services Account Preview" so whether the Preview status has something to do with it, I don't know.
I'd have thought this would be a relatively common use case, has anyone had any joy setting up something similar?
I was finally able to choose the relevant account by making the VSTS principal a co-admin in the Azure account which contains the web app, signing in as that user and changing the directory to use from the the user dropdown menu (top-right). Note, the user account in question is already an administrator for a different Azure account, just to complicate matters further. I only had the option to change the directory once the user was a member of multiple directories.
So I finally got it configured and committing code to the specified branch was triggering a deploy. However, it transpires that setting up continuous deployment from within Azure gives you limited scope and I got constant errors which were not straightforward to fix.
I ended up getting it working properly by following these instructions:
Build: https://www.visualstudio.com/en-us/docs/build/apps/aspnet/ci/build-aspnet-4
Deploy: https://www.visualstudio.com/en-us/docs/build/apps/cd/deploy-webdeploy-webapps
Configuring it all from within VSO gives you a lot more clarity about what's actually happening.
When doing the initial setup, I had to go through an authentication step with the Azure account I was trying to deploy to and that process launches a pop-up window which was getting blocked so I missed it at first.
The initial build and deploy were fine but I was getting a build error when being triggered from a code commmit. This is because the Build Definition --> Variables --> BuildConfiguration value was set back to Release even though I set it to the correct value for my project when doing the initial configuration. Once I updated that, the next commit triggered the build which in turn created the artifact which in turn triggered the deploy which went through fine.
Googler from the future here, I had the same problem and came across a really good article called "DevOps: Connecting VSTS to Azure by Ken Muse" enter link description here
This worked like a charm for me from the first try!