Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionLukáš Hellebrandt
2017-09-19 12:24:01 UTC
Description of problem:
In Sat<6.3, when creating a sync plan, there were sensible date and time pre-filled in the form. It is not in Sat6.3.
Version-Release number of selected component (if applicable):
Sat6.3
How reproducible:
Deterministic
Steps to Reproduce:
1. Content -> Sync plans
2. Create sync plan
Actual results:
Empty date and time, I must fill them in order to continue
Expected results:
The same behavior as in Sat<6.3
Hi Walden,
This regression looks like it may have been introduced during the removal of tupane.
Would you mind taking a quick look to see if it is an easy fix?
I did confirm that in 6.2 the date/time do have defaults on the 'new' form; however, that is no longer the case on 6.3 or upstream.
Verified in snap 19.
Please note that there is no time prepopulated. According to the upstream commit:
"This adds back in the default start date on the sync plan creation day.
The bz mentioned the time as well but the time wasn't ever pre-filled
and is not required to create the plan."
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/RHSA-2018:0336
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/RHSA-2018:0336