I have a JazzHub project associated to Bluemix UK region (according to project settings: JazzHub project overview page > Settings (gear icon) > Options > Make this a Bluemix Project: Region). After I upgraded it to toolchain (in the US), I get the following problems:

When selecting the US org, we keep seeing a message saying the organization doesn't have a space in the 'US South' region, asking to create a space.Though we don't want to run anything in the US.

Some of my colleagues can't access it, though they were listed as member in the original JazzHub project. If they try to open the toolchain with the URL (from the UK app overview page, in the VIEW TOOLCHAIN button), they see access denied message.

1 reply

This can occur if you came from a non-US Bluemix organization, and didn't explicitly expand your organization to the US-South region BEFORE upgrading.

You can confirm this in two ways:

When you open the toolchain URL, please check the Bluemix banner at the top. It is likely showing you your org name with NO space ("---").

In the toolchain > manage page, you should see listed first the org name that is granted access to this toolchain. This should be another org than the one you intended.

In fact, what happened is that at the time of this toolchain manual upgrade, your non-US org didn't exist in the US, and thus the upgrade selected another org for you gracefully (by looking up an another one you happen to have access to). This step can easily be missed as we didn't provide a strong warning there (fix is underway).

So if you properly toggle to that Bluemix org in the US, you'll be able to find the toolchain listed. If you add your colleagues to this org, then they will be granted access from thereon. This toolchain can continue deploying to your non-US org. The only problem is that these two orgs are distinct orgs, user management will not perform across them both automatically.

If you want your toolchain to be in the a US org matching your non-US org, then please follow these steps:

In Bluemix banner, toggle to US-South region, which will prompt for creating a space in the US

Accept creating a space in the US to get your org expanded into the US region. Now you are properly footed in the US region to continue.

Delete the toolchain that was created prior through the upgrade process. NOTE: the Git repo is not automatically deleted. You might want to delete it manually, or rather just rename it for now (in case you made changes to it already, you can switch the future toolchain to using it later on).

Go back to JazzHub project. It should reset itself for another upgrade attempt (if it doesn't automatically does so, please contact us at hub@jazz.net providing the URL of the project needing to be reset).

Reinitiate the JazzHub project manual upgrade process, and this time be sure to check it selected the proper org in the US (matching the name of your org in non-US region).

If you kept/renamed the Git repo from the previous toolchain upgrade attempt (see step 4 above), then you can reconfigure the Git card to point to this Git repo URL instead. It will automatically be reflected in the pipeline (you can view it in the BUILD stage configuration, under Input tab).