davidburtton's questions

I'm trying to create a new container in RH OpenShift, but I keep getting the following error:

error: build error: Failed to push image: error copying layers and metadata from "containers-storage:[[email protected]...: i/o timeout

I've recently configured my Internal Image Registry so I'm wondering if that could be the problem?

I'm completely lost for what is wrong here!!

Thanks in advance

I've recently completed an installation of a Single Node Cluster using OpenShift 4 but I'm running into issues when trying to spin up some of the example container / projects they have available. I just keep getting the following error:

Error starting build: an image stream cannot be used as build output because the integrated container image registry is not configured

It doesn't seem to matter which of the template containers I choose, I always get the same error. Obviously I could be wrong here, but I'm guessing this has something to do with the local registry not being enabled or configured correctly yet? Assuming that's the case, how do I go about configuring the image registry on a Single Node Cluster?

Does anyone have any ideas?

Thanks in advance

I've got a brand new OpenShift Single Node 4.9 installation up and running but am running into issues when trying to get my first container up and running

The install completed without a hitch, but now that I'm trying to get my first container up, I run into an error about the registry not being available? This happens during the build process of the container. Unfortunately, the logs don't show up so I can't share any of those.

No container image registry has been configured with the server

I've tried a few different things to get a registry up and running, but ultimately I'm really not sure where to go from here

Any guidance would be much appreciated!!

Thanks in advance

I've just finished up installing my first Single Node OpenShift cluster but I'm running into some problems with trying to log into the node itself. Of course, I have access to the VM that the cluster is running on but I don't seem to have a way of finding the default credentials that were created during the installation.

Is there something obvious that I'm missing here?

Thanks in advance!

I'm trying to get an OpenShift installation going, but I'm running into issues pretty much right away when trying to add the 'rhel-7-fast-datapath-rpms' repo to RHEL.

Of course, the systems are fully and correctly registered, subscribed, etc. And I've tried all troubleshooting step I can find but nothing's worked so far. I've even asked Red Hat Support for a manual account refresh, per some of the forum posts, but they aren't able to help either.

Of course, I've tried de-registering & reregistering, unsubscribing and re-subscribing, removing and re-adding the repos, etc. But nothing seems to work.

Anyone have any ideas?

I have a scenario where I need a non-domain joined Windows 10 to reboot after it gets joined to a domain and there's a logon of a domain user - any domain user, not a specific one. I'd also need this reboot to happen only once after the initial logon on that user.

I've tried to create a scheduled task that runs when any domain user logs in and reboots the device but I can't seem to find a way of setting this domain user part up without the device already being domain joined? Is this even possible?

I'd also like for this to only happen once, so after the reboot (triggered by the logon on a domain user), I don't want the machine to reboot every time someone logs in. To try cover this off, I looked at Task Scheduler's 'Delete Task After' option but that doesn't look like it'd work either since the task will always be scheduled to run (when any domain user logs in).

Does anyone have any experience taking care of something like this? At this point, I'm pretty sure I'm trying to force a square peg into a round hole using Task Scheduler and that using something like PowerShell might be the better option.

Any ideas how I'd go about this?

Thanks in advance

We're in the process of upgrading ESXi from an older version that only supported BIOS boot mode and I've got some questions around Windows Images (wim files) that we've captured from those VM's that are running on the older version of ESXi and what happens when I upgrade and my VM's start running under UEFI mode.

As we're still in the planning stage, mainly I'm looking for some general advice and guidance on how best to make use of these images in WDS once the migration is complete. I suppose the first question I have is whether or not these images will even be usable once the upgrade is complete - will images captured on VM's running in BIOS mode still be usable and deployable to VM's running in EFI mode?

And if not, what's the process to get them running again? Is there a way to convert those images work with UEFI mode or would they have to be rebuilt from scratch?

Thanks in advance!

I'm trying to find a way to use the native Ansible and Tower failure variables and notifications respectively to send an email with the result of a job's execution output.

So I have a playbook that does something like this:

  rescue:
    - debug:
        msg: "Failure:\n\n{{ansible_failed_result | to_nice_json}}"

Which gives me a nice output in Tower

However I'd also like to be able to pass that same output from Tower to an email notification so that I can see in an email the output of a job without having to log into Tower. This means I know from my email right away if it's a connection timeout or something more serious.

I've tried using the customize notifications in Tower and have tried the 'job.job_explanation' field, however that always returns empty.

I tried running the job with increased verbosity, but that didn't work either.

Any ideas of how to do this? At this point I'm not sure I'm even on the right track using the job_explanation field so any help would be much appreciated!

Thanks

I've got a Windows ISO file that I can currently boot from and install with the EFI boot mode, however I run into issues when trying to boot a VM using the same ISO in ESXi 6.5 which only supports BIOS boot mode.

So I'm wondering how, if it's even possible, do I convert / make compatible my ISO file to work with both EFI and BIOS? After some research, it looks like it might be possible by creating a second BIOS ISO but I have no idea how to go about this

Thanks in advance everyone!

I'm trying to use Ansible to backup a folder once a day and then store the backups on an NFS for archiving but I'm not really sure how to get started with this.

I'd want to mount this NFS temporarily since it's only needed for the duration of the archiving job.

The NFS is protected by Active Directory Authentication.

Any ideas how I would go about this?

My company is getting started with MaaS to replace our old MDM service but we've hit a roadblock pretty quickly...we have several hundred desktops and laptops that need to be enrolled.

Since everyone's working from home and super security conscious these days, there's a lot of pressure to get all of these devices enrolled as quickly as possible. I've looked at Bulk Enrollment but there doesn't seem to be a whole lot of guidance on how to distribute the Bulk Enrollment exe en masse to large numbers of devices

I spoke with IBM Support but they weren't as helpful as hoped: the suggestion was either to use GPO's to distro the enrollment app or to do it manually...

I'm hoping you guys might have some ideas or been in similar situations and point me in the right direction? Any help is much appreciated!