uyuni/docs installation-and-upgrade-manager-4.3-MU-4.3.13 — Czech @ openSUSE Weblate: Troubleshooting

Translation

Source change

English type: Title ==

Czech

Needs editing

Skip

	English	Czech	Actions
	{payg} instance may not be accessible from the {productname} server at all times.
	If the instance exists, but is stopped, the last known credentials will be used to try to connect to the instance.
	How long the credentials remain valid depends on the cloud provider.
	If the instance no longer exists, but is still registered with SUMA, its credentials are no longer valid and the authentication will fail.
	The error message is shown in the column Status.
	The error message only indicates that the instance is not available. Further diagnostics about the status of the instance needs to be done on the cloud provider.
	Any of the following actions or changes in the {payg} instance will lead to credentials failing:
	removing zypper credentials files
	removing the imported certificates
	removing cloud-specific entries from [path]``/etc/hosts``
	Registering {payg} system as a client
	You can register a {payg} instance from where you harvest the credentials as a {salt} client. The instance needs to have a valid cloud connection registered, otherwise it will not have access to channels. If the user removes the cloud packages, the credentials harvesting may stop working.
	First set up the {payg} instance to collect authentication data, so it can synchronize the channels.
	The rest of the process is the same as for any non-public-cloud client and consists of synchronizing channels, automatic bootstrap script creation, activation key creation and starting the registration.
	For more about registering clients, see xref:client-configuration:registration-overview.adoc[].	Další informaceo skriptech pro bootstrap viz xref:client-configuration:registration-bootstrap.adoc[].
	Troubleshooting	Řešení problémů
	Checking the credentials	Pověření účtu (Account Credentials)
	If the script fails to collect the credentials, it should provide a proper error message in the logs and in the {webui}.
	If the credentials are not working, [literal]``reposync`` should show the proper error.
	Using [literal]``registercloudguest``
	Refreshing or changing the [literal]``registercloudguest`` connection to the public cloud update infrastructure should not interfere with the credentials usage.
	Running [literal]```registercloudguest --clean`` will cause problems if no new cloud connection is registered with the cloud guest command.
	Containerized proxy deployment using internal registry
	It is possible to deploy containerized images in an environment without an internet connection. In such case, the images can be copied from {suse} registry to an internal registry, or saved to a [literal]``tar`` file.
	Image copying from {suse} registry to internal registry
	This example illustrates deployment of {salt} proxies only.
	Procedure: Deploying {salt} Proxy from an internal image registry	Postup: Výměna Salt proxy a zachování registrace klientů
	On a machine with access to [literal]``registry.suse.com`` install [literal]``skopeo``:
	zypper in skopeo	zypper ref
	This can be {productname} Server.	Konfigurace serveru {productname}
	Copy images between registries:

Loading…

None

String added in the repository

English

Czech 15 characters edited Current translation Needs editing

3 weeks ago

None

Source string changed

English 1 character edited Needs editing

3 weeks ago

Browse all string changes

Things to check

Trailing space

Source and translation do not both end with a space

Fix string

Reset

Glossary

English	Czech
No related strings found in the glossary.

String information

Source string description

type: Title ==

Flags

no-wrap

Source string location

modules/installation-and-upgrade/pages/connect-payg.adoc:78

String age

3 weeks ago

Last updated

3 weeks ago

Source string age

3 weeks ago

Translation file

l10n-weblate/installation-and-upgrade/cs.po, string 146