Bug 1298321
Summary: | unable to tag containers or pods | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Felix Dewaleyne <fdewaley> |
Component: | UI - OPS | Assignee: | Ari Zellner <azellner> |
Status: | CLOSED NOTABUG | QA Contact: | Avi Tal <atal> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.5.0 | CC: | atal, azellner, fdewaley, fsimonce, hkataria, jhardy, mpovolny, obarenbo, rananda, srevivo, sshveta |
Target Milestone: | GA | Flags: | rananda:
automate_bug-
|
Target Release: | 5.6.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | container | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-02 09:24:30 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Felix Dewaleyne
2016-01-13 18:47:09 UTC
Ari I have the feeling we have seen/addressed something like this recently. Can you double-check if it's already fixed or if it's something new/different. For containers there could be some new implications introduced by the fix for bug 1289694 Could not replicate on latest upstream or latest downstream(5.5.z) for both pods and containers Mooli, since you can reproduce the issue and Ari is going to be out for few days, can you reply the question above? On 5.5.0.13 does it reproduces for pods? For containers? For both? Container UI code changed quite a bit but Pods UI remained the same IIRC so why is it not reproducing on latest cfme-5.5.z? I could not reproduce the above all the way back to 5.5.0.0. In all of those I could assign tags to pods. As for containers, since 5.5.1.0 the 'policy' selection box is disabled, but that does not seem to be the described problem. Finally I retested on 5.5.0.13 with fresh db but still I was able to assign tags. [1] 5.5.1.0 and 5.5.0.13 seem to tags of the same commit the commits I tested: 5.5.z: 5b93864 5.5.1.0, 5.5.0.13: e9c3eea 5.5.0.0: 58436ca Without logs or a reproducer we can't continue. Felix are you still experiencing the issue? I'm still waiting for logs. I haven't been able to reproduce it on my environment yet (lacking an openshift) I've got data from the customer that would confirm that editing a single item works. However I am also remembering that in the recorded session that's attached to the case, I did try to select multiple tenants to attach a tag to them all in one go... it'd take me a while to be able to reproduce that due to having to deploy openshift in lab. if you're able to before, that is fine, otherwise I'll update the case again in a while. Sorry for missing that point in the reproducer steps. Felix, I was automatically moving the ticket to myself but seems that you are still investigating it. I this ticket requires specific setup to reproduce and you have all what it takes to do it then let me know and i'll move it back to you. Felix, it seems that there are no additional information and it's not reproducible. I'll close this for the time being, feel free to reopen in case you have more information. Thanks. I believe this may have been a temporary issue following a cookie expiring - the interface glitched and detected the usage of "back" when going quickly through tabs just before, and this has not been reproducible on the customer's system either. If I see it again I'll reopen this. |