#2678 rolekit rolectl cmd RC=256 on ppc64
Closed: migrated 3 years ago by dmoluguw. Opened 6 years ago by mharmsen.

rolekit rolectl cmd RC=256 on ppc64 (BE) no error for ppc64le (LE)

Problem while running the fedora openQA server_role_deploy_domain_controller
test on a PowerPC host with F26-Alpha

=== extract of openQA issued command:
echo '{"admin_password":"monkeys123","dns_forwarders":{"ipv4":["9.101.4.100"],"
ipv6":["9.101.4.100"]}}' | rolectl deploy domaincontroller --name=domain.local
--settings-stdin
Deployment can take a long time. To monitor the progress, run
journalctl -ef -u rolekit
Error: COMMAND_FAILED: 256
=== extract  /var/log/rolekit
2017-03-31 03:09:12 ERROR: b'ipa.ipapython.install.cli.install_tool(Server):
DEBUG    The ipa-server-install command failed, exception: RuntimeError: CA
configuration failed.'
2017-03-31 03:09:12 ERROR: b'ipa.ipapython.install.cli.install_tool(Server):
ERROR    CA configuration failed.'
2017-03-31 03:09:12 ERROR: b'ipa.ipapython.install.cli.install_tool(Server):
ERROR    The ipa-server-install command failed. See
/var/log/ipaserver-install.log for more information'
2017-03-31 03:09:12 ERROR: RolekitError: COMMAND_FAILED: 256
===

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1437793
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue assigned to cheimes
- Issue priority set to: major

6 years ago

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.4)

6 years ago

Ade and Fraser want to know... what the heck is this ticket about?

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2798

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata