Hide Forgot
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
~]# hammer -u admin -p changeme host list ---|-----------------------------------------------------|------------------|-------------------------|------------|-------------------|--------------|---------------------- ID | NAME | OPERATING SYSTEM | HOST GROUP | IP | MAC | CONTENT VIEW | LIFECYCLE ENVIRONMENT ---|-----------------------------------------------------|------------------|-------------------------|------------|-------------------|--------------|---------------------- 3 | ana-davitt.domain.redhat.com | RedHat 7.4 | RHEL 7 Server 64-bit HG | 11.x.x.4 | 00:1a:4a:3e:a6:4a | RHEL 7 CV | DEV 4 | patsy-younglas.domain.redhat.com | RedHat 6.8 | RHEL 6 Server 64-bit HG | 11.x.x.6 | 00:1a:4a:3e:a6:4b | RHEL 6 CV | DEV 1 | sat6.domain.redhat.com | RedHat 7.4 | | 11.x.x.1 | 52:54:00:32:9e:c6 | | ---|-----------------------------------------------------|------------------|-------------------------|------------|-------------------|--------------|---------------------- [root@sat6 ~]# hammer -u admin -p changeme host info --id 3 Id: 3 UUID: 88c11d70-c6bf-498b-a1a5-1b5ccce4edbd Name: ana-davitt.domain.redhat.com Organization: Default Organization Location: Default Location Host Group: RHEL 7 Server 64-bit HG Compute Resource: rhevm1 Environment: production Puppet CA Id: 1 Puppet Master Id: 1 Cert name: ana-davitt.domain.redhat.com Managed: yes Installed at: Last report: 2017/08/24 21:05:00 Network: IP: 11.x.x.4 MAC: mac_Address Subnet: katello_latest Domain: domain.redhat.com Network interfaces: 1) Id: 3 Identifier: eth0 Type: interface (primary, provision) MAC address: 00:1a:4a:3e:a6:4a IP address: 11.x.x.4 FQDN: Operating system: Architecture: x86_64 Operating System: RedHat 7.4 Build: yes Partition Table: Kickstart default Custom partition table: Parameters: Additional info: Owner Id: 3 Owner Type: User Enabled: yes Comment: Content Information: Content View: RHEL 7 CV Lifecycle Environment: DEV Applicable Packages: 0 Upgradable Packages: 0 Applicable Errata: Enhancement: Bug Fix: Security: Subscription Information: UUID: 6e36b9da-a01f-4a9e-95ce-cee65866d592 Last Checkin: 2017-08-24 20:48:21 UTC Service Level: Release Version: Autoheal: true Registered At: 2017-08-24 20:01:10 UTC Registered by Activation Keys: 1) ak-rhel-7 Host Collections: default_download_policy | on_demand | Default download policy for repositories (either 'immediate', 'on_demand', or... I was able to do Host provisioning with download-policy set to ondemand. VERIFIED with sat6.3.0 12.0 snap
This is strange, I am facing this issue again with Sat630-snap13.0 This had worked fine with Sat630-snap12.0 on my setup. As seen from comment9, it did work earlier, with "on_demand". The above output in comment 9 was from the "hammer settings list | grep -i default_download_policy" Will attach foreman-debug shortly.
Requesting needsinfo from upstream developer jortel because the 'FailedQA' flag is set.
Requesting needsinfo from upstream developer rbarlow because the 'FailedQA' flag is set.
I will try and test this again once with a fresh setup. I just realized that the manifest might have expired and hence the cdn is Forbidding things to fetch the boot files "vmliniz/initrd" after a grace period has passed. Will move it to VERIFIED state if things appear ok, after immediately being able provision hosts.
So, my best guess here is, 1) If I create a new manifest import it in a sat6 2) Then not upload/import the manifest anywhere else in another satellite6 Then this should not be an issue, "if tried immediately it works , but after a while it will not." As the manifest is not expired and so CDN may not forbid it anymore. The problem is creating multiple manifest each time to verify bugs.
VERIFIED again with Sat6.3.0 - snap13.0 and this seems to works fine.
Randy, Seems you set the FailedQA flag on this BZ twice without any further information as the reasoning. Can you shed some light on what the issue is?
(In reply to Eric Helms from comment #20) > Randy, > > Seems you set the FailedQA flag on this BZ twice without any further > information as the reasoning. Can you shed some light on what the issue is? On further thought, I see this flag was set before yet BZ seems to make it appear that you are setting it (or attempting to unset it?). Since this seemed random and out of the blue I figured I'd double check.
weird, all I did was load the page and remove myself from CC. I tried to change it back but I don't seem to have permissions to edit the verified field. I wonder if this is a Bugzilla issue? Since I edited this bug (by removing myself from CC) and don't have permission to edit the Verified field, maybe Bugzilla erroneously cleared it? No idea, but I definitely *can't* edit it intentionally.
Ugh, didn't mean to clear jortel from needinfo either…
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