We are using Jenkins for our continuous integration and in one job Jenkins checks in files into out Clear Case Integration Stream. Recently during one job the ClearCase checkin failed with the following message:
cleartool: Error: Operation "create_version" unavailable for manager "_xxx_file"
(Operation pathname was:
"D:\Programs\IBM\RationalSDLC\ClearCase\lib\mgrs\_xxx_file\create_version")
cleartool: Error: Unable to store new version. cleartool: Error:
Unable to check in "Path/To/File/xxx
I was able to trace back the error, but the file in ClearCase is messed up since then. Every time someone tries to update his view connected to the integration stream he gets the following error message:
Unable to load "xxx": unknown error in VOB.
I can't see the file in the Rational Explorer or in Windows Explorer, but when I click "Compare with Previous Versions" on the containing folder I can see the file in both windows (belonging to current and previous version).
That behavior really confuses me.
I am pretty new to Clear Case and I would love to have a simple way to retrieve the previous version (something similar to git revert).
I would love to have a simple way to retrieve the previous version (something similar to git revert).
If you really think the new and problematic version was to be reverted, you could remove it completely with cleartool rmver (as I used it here). This is quite dangerous though.
But here, that version was likely never created, since the error message starts with "Operation "create_version" unavailable"
You can see this error message in this technote (about ClearCase MultiSite)
This issue occurred after the following sequence of events:
VOBs were being moved from an old server to a new server along with upgrading ClearCase from an older version to 7.x.
A new type manager had been created on the old server along with an element type called keyed_text_file_delta.
The error occurred because the new type manager and element type keyed_text_file_delta did not exist on the new server.
So double-check if the type manager "_xxx_file" still exists in your VOB, using cleartool lstype.
Related
I've got an vscode extension successfully published and updated in market for several versions.
Today after publishing a new version from command line as usual, I got a mail that said it failed due to a validation error. The attached log only said "the extension contains an entry which is unsafe for extraction".
But the only changes in this version were just some adds and deletes in an existing file. I've tried to publish again and the result was the same. So I'm very confused what going wrong here, and the more important question is: How could I get the extension updated again?
Problem while receiving an update from Eclipse to svn. The error message is '0x00000: Open Project' operation completed with error: 0x000000: Unable connection to 'blah-' project. Please check that SVN meta-information exists and it is supporting the form ...
Except that the operating system has been updated from Windows 7 to Windows 10, nothing has changed, but it is annoying and cumbersome to see such errors every time we update. Of course, there are solutions such as cleaning up or re-connecting, but I want to prevent this problem from occurring fundamentally.
Can you tell me what to look at?
Thank you for reading it.
I have been trying to deploy a war file as an OpenShift project. The server used is jboss-webserver30-tomcat8. I have followed the below steps -
Put ROOT.war file under 'deployments' directory in local system.
Upload the changes in github.
Create a new JAVA project in OpenShift 3 and provide the github repository details.
No automatic build or deployment starts. On manually clicking on Start Build button, the below error is displayed:
An error occurred while starting the build. Reason: Error resolving
ImageStreamTag jboss-webserver30-tomcat8-openshift:1.2 in namespace
openshift: unable to find latest tagged image
Please suggest how can I resolve the error.
This is an issue with how the jboss-webserver30-tomcat8-openshift imagestream is defined in the cluster. We are working to correct this, it is not currently importing the correct set of tags and as a result the 1.2 tag was stopped being a valid tag, when it should be.
However the short term solution is change your buildconfig to reference one of the tags that has a valid image reference associated (e.g. 1.3) instead of the 1.2 tag it is currently referencing. Your build should then be able to run.
A (temporarily) unavailable builder image may be related to this platform upgrade that correlates with the time of posting your question.
Generally, the best place to check for any incident reports or scheduled maintenance is the Status Page (Starter | Pro clusters; it's linked in the web console too, in the upper right corner of the interface).
If this does not seem to be related (e.g. you're not on the starter-us-west-2 cluster where the platform upgrade is taking place) or persists after the maintenance is over, I would encourage you to check the open issues, and log a new bug report, if it's not in the list.
Thank you.
I have been using the TFS plugin for eclipse with my companies TFS server for several months. Last week, my laptop crashed while eclipse was open and a connection to the TFS was present. Now, every time I launch eclipse, I get an error stating a connection could not be made to the server, throwing a NullPointerException.
To try to fix this, I cleaned eclipse from my system and removed the installed plugin and then reinstalled eclipse and the TFS plugin. Now, I am no longer getting this connection error on launch. I added the original TFS to the list of servers in eclipse and it can see all of the projects (see http://i.imgur.com/SbgyuRx.png).
However, trying to use any of the projects leads to a screen with an error message saying Error querying workspaces: null. The error log shows the plugin in question as com.microsot.tfs.client.common, with the stack trace saying An exception stack trace is not available.
I am using the same exact plugin installation that I originally used. I have no idea why I'm getting these errors.
The error logs may be helpful. You can view them by going to Help > Team Explorer Everywhere Support, then clicking on the Logs tab.
Ultimately, though, this is probably some corrupt configuration files. TEE performs some various background tasks and I suspect one of those was interrupted in the middle of some file I/O when your computer crashed. Deleting the cache directory may be helpful:
~/.microsoft/Team Foundation
When you restart Eclipse, you should get a dialog box that indicates that your TFS server information cannot be located, but when you reconnect to that TFS server, your projects should return to being TFS managed.
Our software group is using Team Explorer Everywhere Eclipse plugin on Eclipse Helios Our OS is Debian Lenny. Some of the team members are experiencing some weird behavior when they have conflicting changes and when they get the latest.
For instance, right now when we get the latest:
Bunch of conflicts return
"Unable to perform the get operation because you have a conflicting property +x" error.
Then another bunch returns
"Unable to perform the get operation because you have a conflicting edit" error.
Then below all these warning messages eclipse displays the following error:
"Resolving multiple conflicts requires a single resolution type".
Instead of displaying the resolve conflict screen, eclipse does nothing, everytime we get the latest we receive these error messages, so we stare at the screen clueless about how to fix this error.
conflicting property +x error makes me think that there is some permission conflict between the source control and workspace, Though I am not quite sure what we are doing wrong.
Can somebody shed some light on what might be the issue here?
This does seem like a bug. I get this all the time, and use two work-arounds:
1) Go to each conflicting file and do "Get Latest". When you do this file by file instead of project wide, any conflicting files will bring up the Resolve window.
2) At the project level, instead of "Get Latest" do "Get Specific Version" and choose "Latest" with the option to Force the download. That option is usually a checkbox with text like "Force get of file versions..." or something like that.