blocks|key|378260|text|文档的措辞可能有点糟糕。它的意思是，如果您尝试创建一个特定类型的对象，其中具有该名称的对象已经存在，则您创建新对象的尝试将被忽略。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|378261|如果尝试从相同的原始资源定义创建应用程序的多个实例，则会出现这种情况。无法使用一组原始资源定义中的oc+create+-f覆盖命令行中的名称，因此第二个部署是不同的。|offset|length|style|CODE|378262|如果要从相同的资源定义创建多个实例，则需要做的是将定义转换为模板并对名称进行参数化，以便为不同的实例传递不同的名称。这样就不会有冲突了。|378263|另外，当您创建一组资源时，通常最好在所有资源类型中使用一个名称，而不是对每个资源类型使用不同的名称，例如，只对所有资源使用'my-app-+name‘，而不是单独使用'my-buildconfig’、'my-imagestream‘。|378264|更重要的是，您需要确保在它们上添加一个具有相同键/值的标签，这样就可以轻松地与它们一起工作，包括一次性删除它们。|378265|您要部署的应用程序类型是什么？我可以向您指出示例模板，您可以使用它作为指南。|378266|更新1|378267|如果您希望能够运行oc+create+-f，并且在资源已经存在的情况下让它不抱怨，但是如果它们不存在，则使用oc+apply+-f。|378268|entityMap^0|0|1D|C|0|0|0|0|0|0|9|C|1I|B|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|14|8|@$D|15|E|16|F|G]|$D|17|E|18|F|G]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|U|$]]

The documentation is perhaps a bit badly worded. What it is saying is that if you try and create an object of a specific type where an object of that type with that name already exists, your attempt to create the new one will be ignored.

The situation you have will occur if you tried to create multiple instances of an application from the same raw resource definitions. There is no way using <code>oc create -f</code> from a set of raw resource definitions to override names from the command line so a second deployment is distinct.

What you would need to do if you want to create multiple instances from the same resource definitions, is to convert the definitions into a template and parameterise on the name so that you can pass in a different name for different instances. That way there will not be a clash.

Also, when you do create a set of resources, it is usually better to use the one name across all the resource types and not use a different name for each, eg., use just 'my-app-name' for all of them, and not separately, 'my-buildconfig', 'my-imagestream'.

More importantly, you need to ensure you add a label with same key/value on them all so it is easy then to work with them together, including deleting them all in one go.

What is the type of application you are trying to deploy? I can possibly point you at example templates you can use as a guide.

<hr>

UPDATE 1

If you want to be able run <code>oc create -f</code> and have it not complain if the resources already exist, but create them if they don't, use <code>oc apply -f</code> instead.

blocks|key|378273|text|使用oc+replace怎么样？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|378274|oc+replace+--filename+file.yml+--force|code-block|syntax|javascript|378275|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.openshift.com/container-platform/3.11/cli_reference/basic_cli_operations.html#replace^0|2|A|2|A|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

How about using <a href="https://docs.openshift.com/container-platform/3.11/cli_reference/basic_cli_operations.html#replace" rel="nofollow noreferrer"><code>oc replace</code></a>:

<pre><code>oc replace --filename file.yml --force
</code></pre>

blocks|key|2013697|text|运行oc+delete+<resource>+<name>。示例:然后运行oc+delete+configmap+my-configs命令。-f和"oc替换“对我不起作用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2013698|entityMap^0|2|R|11|U|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Run <code>oc delete &lt;resource&gt; &lt;name&gt;</code>. Example: <code>oc delete configmap my-configs</code> Then run your command. -f and &quot;oc replace&quot; didn't work for me.

Attempting to create a set of resources based on a file via <code>oc create</code> fails if they already exist.

According to the <a href="https://docs.openshift.com/enterprise/3.2/cli_reference/basic_cli_operations.html#create" rel="noreferrer">docs here</a> <code>oc create</code> should:

<blockquote>
 Parse a configuration file and create one or more OpenShift Enterprise
 objects ... Any existing resources are ignored.
</blockquote>

(emphasis mine).

I can't see any config options for this command or globally that would alter this behaviour and it seems to me to be counter to the docs.

The command I ran is <code>oc create -f some.file</code>

The output is:

<pre><code>Error from server: services 'my-app' already exists
Error from server: buildconfigs 'my-app' already exists
Error from server: imagestreams 'my-app' already exists
Error from server: deploymentconfigs 'my-app' already exists
Error from server: routes 'my-app' already exists
Error from server: secrets 'my-app' already exists
</code></pre>

It also exits with a non-zero exit code, so it's not just a warning. Am I missing something obvious here or misunderstanding what the documentation is saying?

I just want to be able to apply this file and ensure the state of the OpenShift project afterwards.

OpenShift oc create fails with "already exists"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

试图通过oc create创建一组基于文件的资源，如果这些资源已经存在，则失败。根据 oc create应该：解析配置文件并创建一个或多个OpenShift企业对象.任何现有资源都将被忽略。(强调我的)。我看不到这个命令的任何配置选项或全局配置选项会改变这种行为，在我看来，这似乎与docs背道而驰。我运行的命令是oc ...

问OpenShift oc创建失败与“已存在”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OpenShift oc创建失败与“已存在”EN