-
Notifications
You must be signed in to change notification settings - Fork 202
f8 not setting imagestreams resourceVersion properly. #1696
Comments
Maybe this is related: |
I am experiencing the same behavior, and this represents a blocking issue for me. @weinzierl-florian, did you manage to find a workaround? |
oh, is it happening for |
@rohanKanojia It seems to be happening just for ImageStreams, but I haven't tested all types of resources. I can add that the problem is also present in version 4.1.0 of fabric8-maven-plugin, so this is not a "new" issue. It seems to work with version 4.0.0, so I can downgrade for now. |
hmm, when I append resourceVersion while doing PUT on |
@erikgb: Maybe downgrading is the only option until this is finally solved. @rohanKanojia: |
@weinzierl-florian : I've created a PR to explicitly add resourceVersion in metadata. I don't see any harm in doing this. |
Hello @rohanKanojia, Unfortunately I am still not able to successfully apply the generated imagestreams.yamls with “mvn fabric8:apply”. I used the latest 4.3.0 version of the plugin. Could you please double check if that is working. Thank you very much in advance! The error says that it can not create ImageStream and has failure when executing PUT. Regards, |
what response code are you getting? 422? |
Could you please share logs with |
@nikolaaleks : You're right. I'm also able to reproduce this 😞 |
Hi @rohanKanojia, After I have generated the resources with “mvn fabric8:resource” when I try to call “mvn fabric8:apply” I get the error code 422 and image stream is generated in OpenShift. If I call fabric8:apply second time the error has code 409. If i call it third time there is no error at all, which is strange. It depends and how much imagestreams.yamls I have generated. I will look what the output is when I call it in Debug mode and let you know. Regards, |
hmm, weird. Let me fix this. |
@nikolaaleks : I've created a PR which seems to be working for me. Would appreciate if you could test it and provide feedback. It would only take 5-8 minutes. |
Hi @rohanKanojia, I have successfully tested the fix that you have proposed. I was able to generate the imagestreams in OpenShift by using "mvn fabric8:apply". When could I expect to get the newer version of the plugin? Thank you in advance. Regards, |
@nikolaaleks : Thanks a lot for trying it out 👍 . I'm planning to cut 4.3.1 this week. |
@nikolaaleks : FMP 4.3.1 has been released. |
Hi @rohanKanojia, Can you tell me when the FMP 4.3.1 will be available also in maven central repository - https://mvnrepository.com/artifact/io.fabric8/fabric8-maven-plugin ? Is that something that you control? Thank you in advance! Regards, |
@nikolaaleks : It is already there: https://search.maven.org/artifact/io.fabric8/fabric8-maven-plugin/4.3.1/maven-plugin You should start using the official Maven search, and not the "commercial" one. 😉 |
f8 not setting imagestreams resourceVersion properly.
Description
I wrote the following yml config for an imageStream:
if I run fabric8: resource-Goal it succeeds properly
But running fabric8:apply-Goal afterwards fails with:
I tried Setting
resourceVersion: 1
in the metadata section but got:BUT If I went to the Web UI choose
Import YAML/JSON
under theAdd to Project
-Button and copied the exact same Config above (without the resourceVersion setting) it worked without any problemsInfo
mvn -v
) :Red Hat OpenShift
Version
Create a configfile for an ImageStream and try to execute fabric8:resource and afterwards fabric8:apply
The text was updated successfully, but these errors were encountered: