Bug 1527392
| Summary: | subscription-manager-cockpit : Text fields in the "Register" dialog doesnt clear the data at all | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Rehana <redakkan> | ||||
| Component: | subscription-manager | Assignee: | Jiri Hnidek <jhnidek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Red Hat subscription-manager QE Team <rhsm-qe> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 7.5 | CC: | jhnidek, jsefler, khowell, redakkan, salmy, skallesh | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | subscription-manager-1.20.10-1 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-04-10 09:52:44 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: | |||||||
| Attachments: |
|
||||||
|
Description
Rehana
2017-12-19 11:02:08 UTC
Created attachment 1388763 [details]
proxy details still remain upon unregister
Moving bug to back to new as the text fields of register dialogue are cleared but proxy details still remain upon unregistering
[root@bkr-hv03-guest18 ~]# rpm -qa | grep cockpit
cockpit-160-2.el7.x86_64
cockpit-bridge-160-2.el7.x86_64
subscription-manager-cockpit-1.20.10-1.el7.noarch
cockpit-system-160-2.el7.noarch
cockpit-ws-160-2.el7.x86_64
> Moving bug to back to new as the text fields of register dialogue are cleared but proxy details still remain upon unregistering.
These fields are being pulled from rhsm.conf, similar to serverurl. Since the expectation is that upon successful registration, these details are saved to rhsm.conf and also the cockpit UI should respect settings from rhsm.conf, I think it's reasonable that they are present after unregistering. Thoughts?
Hi Kevin, I agree that the text field of register option are now getting cleared. However for the proxy ,When user removes the proxy entries from rhsm.conf( by manually or CLI) the Proxy details are *NOT* getting removed from the cockpit UI. But if the user restarts rhsm.service then the proxy entry is getting removed I just wanted to confirm if user makes any changes in the rhsm.conf file , the rhsm.service needs to be restarted to see the changes on the cockpit ? > I just wanted to confirm if user makes any changes in the rhsm.conf file , the rhsm.service needs to be restarted to see the changes on the cockpit ? Correct. We are tracking this in bug 1504588. (In reply to Kevin Howell from comment #5) > > I just wanted to confirm if user makes any changes in the rhsm.conf file , the rhsm.service needs to be restarted to see the changes on the cockpit ? > > Correct. We are tracking this in bug 1504588. Hi Kevin, Can we switch this bug to on_qa then ? I can verify the text field clearing part as the other observation is tracked in bug 1504588 thanks. Rehana Verifying on : ============ subscription-manager-rhsm-1.20.10-1.el7.x86_64 subscription-manager-initial-setup-addon-1.20.10-1.el7.x86_64 subscription-manager-gui-1.20.10-1.el7.x86_64 subscription-manager-rhsm-certificates-1.20.10-1.el7.x86_64 subscription-manager-cockpit-1.20.10-1.el7.noarch cockpit-160-2.el7.x86_64 subscription-manager-1.20.10-1.el7.x86_64 Steps followed: 1.Try to register the system using cockpit 2.enter the details needed 3.register 4.now unregister and try to register again Observed that now the Text fields in the Register Dialog are cleared. Note: The observation regarding reflecting any change of rhsm config parameters in cockpit will be tracked in the bug 1504588 as per comment 6 Based on the above observations marking the bug as Verified!! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0681 |