On Thu, May 7, 2020 at 3:03 PM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:
> Ben,
>
> That explains it the build wait failure - you can see from the output
> I included at the end of my email, that I'm at v4.3.12 . Does this explain
> my observations with the project delete not
Ben,
That explains it the build wait failure - you can see from the output I
included at the end of my email, that I'm at v4.3.12 . Does this explain my
observations with the project delete not waiting correctly either?
Regards,
Marvin
On Thu, May 7, 2020 at 2:53 PM Ben Parees wrote:
>
what version is your cluster? conditions were only recently added to the
build.status section to OCP 4.4. oc wait doesn't work no resources that
don't have a status.conditions section.
On Thu, May 7, 2020 at 2:47 PM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:
> Ben,
>
> It
Ben,
It looks like I have a general problem with "oc wait" or waits, in
general, not working reliably on my cluster. Here is my code now:
# Step 7: Wait for the build to start. For some reason, the wait command
doesn't work, saying that the build doesn't exist even
# though the new-app
On Wed, May 6, 2020 at 12:50 PM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:
> Ben,
>
>I appreciate the pointer, but this doesn't seem to do the right thing.
> Here is the relevant portion of my code:
>
> oc new-app --name=teams git@ -e MONGODB_USER= -e
>
On Wed, May 6, 2020 at 11:34 AM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:
> Hi,
>
> I've been trying to write a script that runs various commands
> following a new-app. These commands will operate on the dc created by
> new-app, but fail if the resources haven't reached the
