https://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-02-28T22:06:20ZPulpRPM Support - Issue #430: The pulp-profile-update yum client plugin does not clearly report errors to usershttps://pulp.plan.io/issues/430?journal_id=8152015-02-28T22:06:20Zrbarlow
<ul></ul><p>I am using yum-3.4.3-146.fc21.noarch, if that matters.</p>
<p>+ This comment was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1097906#c1" class="external">Bugzilla #1097906 comment 1</a> +</p> RPM Support - Issue #430: The pulp-profile-update yum client plugin does not clearly report errors to usershttps://pulp.plan.io/issues/430?journal_id=8162015-02-28T22:06:21Zrbarlow
<ul></ul><p>It turns out that our plugin is printing this error through the yum conduit:</p>
<p>Peer certificate commonName does not match host, expected localhost.localdomain, got guava.rdu.redhat.com</p>
<p>It would be nice if this was more clearly an error in reporting the profile.</p>
<p>+ This comment was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1097906#c2" class="external">Bugzilla #1097906 comment 2</a> +</p> RPM Support - Issue #430: The pulp-profile-update yum client plugin does not clearly report errors to usershttps://pulp.plan.io/issues/430?journal_id=8172015-02-28T22:06:22Zrbarlow
<ul></ul><p>Turns out that this was user error. I hadn't edited the server line in the /etc/pulp/.../consumer.conf file, but I had in the /root/.pulp/consumer.conf file. The yum plugin only reads the one from /etc/.../. However, I do think we have an issue here in reporting problems to users. Note the printout in the middle here about the peer certificate commonName not matching:</p>
<p>rbarlow@guava ~/d/p/pulp_rpm> (pulp_rpm) sudo yum install grinder_test_package-4.0<br>
Loaded plugins: langpacks, pulp-profile-update<br>
Resolving Dependencies<br>
--> Running transaction check<br>
---> Package grinder_test_package.noarch 0:3.0-1.fc14 will be updated<br>
---> Package grinder_test_package.noarch 0:4.0-1.fc14 will be an update<br>
--> Finished Dependency Resolution</p>
<p>Dependencies Resolved</p>
<p>====================================================================================================================<br>
Package Arch Version Repository Size<br>
====================================================================================================================<br>
Updating:<br>
grinder_test_package noarch 4.0-1.fc14 test-errata-install 1.6 k</p>
<p>Transaction Summary<br>
====================================================================================================================<br>
Upgrade 1 Package</p>
<p>Total download size: 1.6 k<br>
Is this ok [y/d/N]: y<br>
Downloading packages:<br>
grinder_test_package-4.0-1.fc14.noarch.rpm | 1.6 kB 00:00:00<br>
Running transaction check<br>
Running transaction test<br>
Transaction test succeeded<br>
Running transaction<br>
Updating : grinder_test_package-4.0-1.fc14.noarch 1/2<br>
Cleanup : grinder_test_package-3.0-1.fc14.noarch 2/2<br>
Peer certificate commonName does not match host, expected localhost.localdomain, got guava.rdu.redhat.com<br>
Peer certificate commonName does not match host, expected localhost.localdomain, got guava.rdu.redhat.com<br>
Verifying : grinder_test_package-4.0-1.fc14.noarch 1/2<br>
Verifying : grinder_test_package-3.0-1.fc14.noarch 2/2</p>
<p>Updated:<br>
grinder_test_package.noarch 0:4.0-1.fc14</p>
<p>Complete!</p>
<p>I think it would be best if we could make that error message more obviously tell the user that the plugin failed to report the profile to Pulp. I didn't even notice it was an error at all when I first ran it. It would have been better if it said something like "Error in reporting profile to Pulp: <error_message_here>".</p>
<p>I'm lowering the severity since it turns out that nothing is really broken.</p>
<p>+ This comment was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1097906#c3" class="external">Bugzilla #1097906 comment 3</a> +</p> RPM Support - Issue #430: The pulp-profile-update yum client plugin does not clearly report errors to usershttps://pulp.plan.io/issues/430?journal_id=25872015-03-20T19:14:16Zbmbouterbmbouter@redhat.com
<ul><li><strong>Severity</strong> changed from <i>Low</i> to <i>1. Low</i></li></ul> RPM Support - Issue #430: The pulp-profile-update yum client plugin does not clearly report errors to usershttps://pulp.plan.io/issues/430?journal_id=372962019-04-12T20:15:10Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - WONTFIX</i></li></ul><p>Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" class="external">developer mailing list</a>.</p> RPM Support - Issue #430: The pulp-profile-update yum client plugin does not clearly report errors to usershttps://pulp.plan.io/issues/430?journal_id=404132019-04-15T21:12:41Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>